It’s been a while since we’ve been thinking about moving to Mercurial from Subversion at our company. We were convinced about the benefits of DVCS and chose Mercurial over Git. However, due to pressure at work and some procrastination, the move was delayed a couple times. Finally, today we had the move and the team is already up to speed with it.

Although it’s quite simple to install it in a central server, the different articles on the web had me confused with too many options or with a different distro than Ubuntu. So, here is a dead simple list of things to do for installing Mercurial centrally for your dev team.

1. Log onto your server using SSH

2. Install mercurial from repository:

3. We need to have a directory to store our Mercurial configuration and repository files, so let’s create one and change it’s owner to the apache user so that apache can access them:

4. We’ll be creating a configuration that will allow us to host multiple repositories in this server. And we’ll be using CGI to serve the files through Apache:

5. We need to show the location of the config file to the CGI script, so open the file hgweb.cgi with nano or vim to update the line with “config = …” with the following and save it.

6. Now let’s create the file /var/hg/hgweb.config and write the location of the repositories:

Enter the following content and save the file:

7. As a final step, we’ll need to update the Apache configuration so that it executes the CGI when requested with a /hg prefix:

At the end of the defaul virtual host configuration and just before the </VirtualHost> tag, add the following and save it:

8. In order to take effect of the above change, we’ll need to restart apache:

9. Now you should be able to visit the server’s /hg location like http://rbs-server.com/hg from browser. However, you’ll be greeted with a username/password prompt as we’ve enabled that in our apache configuration above. So, lets add some user for our use.

It will ask for the password of the user admin twice and after you enter that, it will be stored in the file hgusers. You can add more users in the similar fashion, just ignore the c parameter as it was used to create the file first time:

10. Now visit the /hg path in your browser and you’ll see the empty list of repositories after you authenticate.

11. By default Mercurial only allows pushing changes through SSL, but in our case it was not necessary. Also, we wanted to give all our developers the push access to the repositories. For that, let’s update the system-wide mercurial configuration file /etc/mercurial/hgrc by adding the following lines at the end of the file and saving it:

12. Now that all is set, let’s setup a test repository so that we can clone it in our development machine:

This repository can now be accessed through http://rbs-server.com/hg/test and can be cloned in a development machine with the following command (mercurial must be installed already):

Hope this will make someone’s life easy. Enjoy the beauty of Mercurial!

Photo source

Here goes the slides:

All the other slides, pictures, and videos are available here.

Enjoy!

You’ve been developing web applications using PHP for a couple months now and are finding it very enjoyable. Although you feel that you’re doing quite good, you’re not sure whether its the end. Besides, the following questions wonder you often:

• Where to go from here
• What new things to learn
• How to become a Kick-ass PHP Ninja

If that’s the scenario, then this post if for YOU.

Background

A few days back, I read a number of blog posts where people have highlighted the shortcomings they see in newbie developers. Some of them have gone further to narrow down the focus on PHP developers only (as PHP’s nature sometimes allow developers to avoid standards). They did a great job by listing the shortcomings, but their posts missed clear way forwards (these can be inferred though). A number of readers also commented on the posts with their insight as well. So I was thinking how about compiling all these in an easy to follow list? Hence this post.

Btw, due to the volume, I’ve mostly touched the points here and provided few useful resource links for further study. I do have plan to elaborate a few of them in coming posts, with each point becoming a single post. Let me know which ones you’ll prefer most, by entering the poll at the bottom of the post.

Part A : Technical Way Forward

In the first part, let’s shed some light on how you can move forward with your technical abilities.

1. Start using version control

Version control is like a big UNDO button for your coding. You can go back to your previous code revisions and can compare/rollback to specific code areas anytime you see necessary. It will keep track of all your changes and will empower you to track your development changes across your work/team. Also, in a distributed development team, version control helps prevent overwriting of code by team members and keeps all the members code up to date.

Subversion (SVN) is one of the most popular open source version control system. If you’re on windows platform, you can try TortoiseSVN, a client for SVN.

2. Write code in OOP way

If you haven’t already, it’s high time you started writing code in Object Oriented Programming (OOP) way. You may ask why? Well, OOP forces you to write code that is maintainable in nature. If properly followed, OOP code become a lot efficient than procedural code. Also, it allows you to re-use code across your project and/or multiple projects.

If you’re not convinced, have a look at these excellent resources for further study.

3. Adhere to a coding standard

Coding standards allow you to write code in a way which is easily understood by other people. When you adhere to a coding standard used by may others, you actually convey a message that you’re serious in writing code that people will be able to “get” and maintain. Keeping abbreviation type variable names, applying multiple indention types, writing meaningless function names etc will work for you in short term, maybe in personal projects. But when you move to a larger group with a number of developers, you ought to follow a standard so that everybody working with you can get along with your parts.

The following standards are most widely used among PHP developers around the globe:

• PEAR Coding Standards
• Zend Framework Coding Standards
• eZ Publish PHP Coding Standards (depreciated)
• eZ Components Implementation guidelines

Although you can define a standard for your team/company, it’s always better to have close relation with what the industry follows. In my company, Right Brain Solution Ltd, we follow a slightly modified version of Zend Framework Coding Standards. You can get that one here.

4. Document your code

Documentation is a virtue of great developers – don’t get me wrong, I’m talking about code documentation, not writing user manuals Well documented code prevents other team members from reading each line of your code and understand them by heart. Rather, it tells them exactly what they need to know – purpose of the code, what it requires as input, what it will deliver as output, etc. If you take a look at the above mentioned coding standards, you’ll discover that most of them even specified standard for documentation as well, which is phpDocumentor. It’s the most used standard for PHP code documentation and is widely recognized.

5. Use a good framework

Frameworks give you good structure and helps you build web applications in a fast way, with confidence. Most of today’s popular PHP frameworks (Zend Framework, CodeIgniter, CakePHP, Symfony, Kohana etc) follow the Model-View-Controller (MVC) pattern, which itself is a strong advocate of good practice.

Besides structure, frameworks force you to write code in a structured way. Some of them will also require writing the code in OOP – whose benefit we already discussed above. And frameworks usually come with a number of helpful libraries and helpers, to make your life easy as a web developer.

Josh sharp discusses this in details here and later posts a follow-up here. Both are good reads.

6. Re-use code/libraries

One of the most common advice programmers get is: “Don’t re-invent the wheel”. Well, what’s the point here? It actually means that you should not spend much time on solving a problem that has already been solved, in efficient way, by others. Rather solving it out yourself, you can “google” it and see how others have done it. It will not only save your valuable time, but also will ensure stable code (assuming that people usually post things on web after doing a number of testing and user of the codes usually help iron-out any issues, etc).

However, keep an eye on your target use/objective. If there is not enough good solutions that solves your problem, go ahead and solve yourself. Make it good and give it back to the community so that others facing that problem won’t need to spent the time you’ve spent. The whole open source model runs on this give-give way, so be a part of it.

7. Test your code the right way

In order to make confidence out of your code, you’ll need to test your code the right way. Although you might be used to testing your application using debug messages and browser refreshes, in a real world scenario these won’t work. You’ll need to write unit tests which can do automated testing of your code. The power lies in that you can run these tests almost anytime and can check if anything is broken after each new change.

PHPUnit and SimpleTest are the two most widely used Unit testing suite for PHP. You should also have a look on Test Driven Development (TDD), which is the way of greatly enhancing your chance of deploying application with least bugs.

Part B : Personal Way Forward

Now, even if you’ve improved yourself on the above mentioned points, you’ll still need to work on your personal matters to move forward. Here goes those points.

8. Be Agile

You need to be an agile developer if you want to move forward in your career. What does it mean to be agile? Agility is more of an attitude than a skill set. The common characteristics of agile developers are:

• They’re open minded and therefore willing to learn new techniques
• They’re responsible and therefore willing to seek the help of the right person(s) for the task at hand
• They’re willing to work closely with others, pair programming or working in small teams as appropriate
• They’re willing to work iteratively and incrementally

Further resources: Agile Software Development, The Agile Manifesto.

9. Keep yourself updated

No matter what, keep yourself updated on whats going on in your field (in this case PHP). Subscribe to the RSS of great PHP blogs and skim over them on a regular basis. Dig into the topics that interest you most and see the author’s point. Also, keep a habit of trying new technologies every now & then. It gives you an edge over others and when any discussion goes about it, you can help others understand as well as make your points.

Btw, if you don’t have a clue where to find good blogs, have a look at here, here and here.

10. Start community involvement

Remember I told above to give your work back to the community ? How to do that ? Start a blog of your own and start writing posts there every now & then. Yes, I know you’d say “Who’s going to read my blog anyway?”, but if you share your experience, someday, somebody will find it useful. And if you can share things that others haven’t done, you’ll slowly see visitors coming on your blog increasing way.

Besides blog, try to participate in tech forums and communities. Help people out in the areas you excel and at the time of your need, other people will be happy to help you out as well. These communities are also great place to learn about many unusual matters, see how situation changes from person to person, place to place, etc. You’ll also be able to make great friends who might come handy later in your life.

Another great way of community involvement is to contributing to open source projects. Share some of your valuable time for an open source project and it may come handy for a huge number of people. Your work might solve the problem of somebody like you. If needed, initiate an open source project yourself and invite others to work on your vision.

11. Use a good IDE

With due respect to Dreamweaver, step forward and use an IDE made for PHP. You’ll notice the difference in a few days when you’ll see that your productivity has increased in great ways. These IDEs provide great number of useful features including but not limited to: syntax highlighting, auto completion, code suggestions, code snippets, contextual help, code templates, debugging, profiling, etc.

The following IDEs mostly have the similar feature set and can boost your productivity in great ways:

• NuSphere PhpED
• phpDesigner 2008
• Zend Studio for Eclipse

Personally I use NuSphere PhpED 5.2 and I love it in every way. They’ve provided me with a complementary license and I am grateful to them for that. If you’re planning to buy it, let me know and I might find you a discount.

12. Be communicative

In your team/company, try to be as communicative as possible. It reduces a lot of confusions, makes you close to other devs so that you understand them, portrays you as a good person in front of management and overall, helps you enjoy your work. When you’re working together with others, make them feel that you’re there and ready to give whatever it takes. Create a personal brand of yourself.

What’s next?

Phew! It’s quite a good amount of writing in a while I’ve tried to cover most of the items I found to be important. However, there might be some points I’ve overlooked so feel free to post them in the comments. If this helps any one of the developers I intend it for, then I’ll take that the effort is successful.

Thanks everybody, Happy Eid Mubarak to you!

When you interview them and ask about complex topics, they’ll reply: “Oh my last company didn’t allow me work with that, but I’ll be able to grab that in a day“. You trust them and think that if they get the chance, they’ll sure be able to excel. After all, they’ve got that Company X’s experience and Guru Y’s reference.

At first everybody gets amazed with these developers employment history, the projects they’ve done, the technical jargons they can utter, the ideology/framework/pattern they talk about, etc etc. Everybody wants them in their team. The team who gets them finally are happier than ever, after all life will get easier to have such an expert in team.

Soon projects get rolling and everybody in his/her team is eagerly waiting to see the magics from these “senior” developers. To their disappointment, more ideas/criticism/review (e.g. “Pattern X is better than pattern Y. Why you’re choosing X?”, “Why are you doing Z in this way? Who taught you this?”, “Have you ever heard of DEF?”, “I have done research on DB normalization and you teach me schema?“) takes place but they don’t see actual code from these developers.

They come to office in an awkward timing, leaves early, works with personal things at office – but nobody can question their activity as people might not believe them. With much regret, the remaining team members continue to complete the work which the “senior” developer was suppose to do. Instead of a team synergy, an unintended pressure is created in the team.

Eventually the project misses deadline by miles, team members become unhappy as they had to do extra work each day to cover the team’s ass, company gets screwed as client is unhappy and decides not to do repeat business. Company digs down the cause of the failure, finds the responsible person, and fires them away.

Surprisingly, when a friend of the “senior” developer asks them in a social party: “What happened with the Company X you were working on?”, they’ll reply: “Oh that crap! You know, it’s a pain to work with junior developers. They don’t understand things. All they know is coding, no knowledge, no understanding of architecture. And the management is so poor, you won’t believe……“.

Don’t include someone like them in your team and think twice or thrice if you don’t have many options. Try to find out how good programmer they are in the interview. How senior they might be, ask them to write code in the interview. Try out proven questions that others have shared from their experience. Overall, make sure you’re taking the right person. The best hiring option is to hire “no one”.

Have you been in such situation? Share your experience here!

Feb 2009: An updated version of the code for CodeIgniter 1.7.x can be found here.

I developed this extension of CodeIgniter’s Model last year, but never had the chance to publish it. The main purpose of this extension is to make a dev’s life easy. This extension has been used by several of my devs at RBS and has been proved to increase productivity and reduce the number of painful small queries to write. Their enthusiasm has driven me to post this for the CI fans out there.

Without much babble, let’s get into point. I’ve explained the process of installing it and then showed some example uses. For starter, click here to download it. Now follow these steps to get started:

1. Replace the system/libraries/Model.php file with the attached Model.php (CodeIgniter version 1.6.3)

2. For each of your tables, you will need to create a model file in system/application/models.

3. Lets say we have a "products" table whose schema is as follows:

   1: CREATE TABLE `products` (

   2:       `id` int(11) NOT NULL auto_increment,

   3:       `title` varchar(50) NOT NULL,

   4:       `description` text NOT NULL,

   5:       `color` varchar(20) NOT NULL,

   6:       `price` float NOT NULL,

   7:       `category_id` int(11) NOT NULL,

   8:       `featured` char(1) NOT NULL,

   9:       `enabled` char(1) NOT NULL,

  10:       `visits` int(1) NOT NULL,

  11:       `created` int(11) NOT NULL,

  12:       `modified` int(11) NOT NULL,

  13:       PRIMARY KEY  (`id`)

  14:     ) ENGINE=MyISAM;

4. Now we need to create system/application/models/product.php:

   1: <?php  if (!defined('BASEPATH')) exit('No direct script access allowed');

   2:  

   3:     class Product extends Model {

   4:  

   5:         function Product()

   6:         {

   7:             // Call the Model constructor

   8:             parent::Model();

   9:             

  10:             // Load the associated table

  11:             $this->loadTable('products');

  12:         }

  13:  

  14:     }

5. From any controller, you can load the Model as instructed in the CI manual. Here are some sample usage of the model functions:

   1: function products()

   2:     {

   3:         // Load the model in the default way

   4:         $this->load->model('Product');

   5:         

   6:         // Total # of products

   7:         echo $this->Product->findCount();

   8:         

   9:         // Total # of featured products

  10:         echo $this->Product->findCount("featured = 'Y'"); 

  11:         

  12:         // Retrieve ALL the products

  13:         $allProducts = $this->Product->findAll(); 

  14:         

  15:         // Retrive id, title and price of top 10 products (based on popularity) that are enabled

  16:         $topProducts = $this->Product->findAll("enabled = 'Y'", 'id, title, price', 'visits DESC', '0', '10');

  17:         

  18:         // Retrive id, title and price of the 1st most popular product that is enabled

  19:         $topProducts = $this->Product->find("enabled = 'Y'", 'id, title, price', 'visits DESC', '0', '10'); 

  20:         

  21:         // Retrieve the product with id = 1

  22:         $oneProduct = $this->Product->read(1); 

  23:         

  24:         // Retrive the price of the product whose id = 1

  25:         $productPrice = $this->Product->field('price', 'id = 1'); 

  26:         

  27:         // Single array with the titles of all the enabled products

  28:         $productArr = $this->Product->generateSingleArray("enabled = 'Y'", 'title'); 

  29:         

  30:         // Insert a new product in the db

  31:         $newProductId = $this->Product->insert(array('title' => 'New Product', 'price' => '10.99')); 

  32:         

  33:         // Update the price of the newly added product

  34:         $updProduct = $this->Product->save(array('price' => '20.00'), $newProductId); 

  35:         

  36:         // Delete the product

  37:         $this->Product->remove($new_product_id);

  38:     }

7. There are a number of other helpful functions in this file. If you have a careful look, you’ll discover that some of them are really handy.

UPDATE: I forgot to give due credit to the wonderful developers of CakePHP – I’ve taken inspiration from their Model implementation while building this one for CodeIgniter.

Download

Model.php Extended Model for CodeIgniter Downloaded: times

MORE UPDATE: Download the version for CodeIgniter 1.7.x here.

I would like to let you all know that we’ve just launched the new website of Right Brain Solution Ltd.. I would like to personally thank all our friends, families, associates, and well-wishers – for all their support and patience.

Please have a look at the site and let us know your views, comments, ideas, criticism – anything that you would like to share with us.

Thank you all!