Comments on: What do to right from the beginning http://scottmartin.net/2007/12/14/what-do-to-right-from-the-beginning/ Tue, 06 Jan 2009 22:42:20 +0000 http://wordpress.org/?v=2.5.1 By: PIBlog » Blog Archive » Doing it Right from the Beginning http://scottmartin.net/2007/12/14/what-do-to-right-from-the-beginning/#comment-10 PIBlog » Blog Archive » Doing it Right from the Beginning Mon, 17 Dec 2007 22:26:58 +0000 http://scottmartin.net/2007/12/14/what-do-to-right-from-the-beginning/#comment-10 [...] My coworker Scott Martin recently posted a list of things to do from the beginning of a project.. [...] [...] My coworker Scott Martin recently posted a list of things to do from the beginning of a project.. [...]

]]> By: Jeremy Teale http://scottmartin.net/2007/12/14/what-do-to-right-from-the-beginning/#comment-8 Jeremy Teale Mon, 17 Dec 2007 13:53:54 +0000 http://scottmartin.net/2007/12/14/what-do-to-right-from-the-beginning/#comment-8 A couple things to add of a bit less technical orientation: 1. Version control policy Commit messages are important and useful. Major development should always be branched. Symlinking everything instead of using external repositories gets really silly, really fast. Above all, maintain a clean repository, cruft accumulates quickly. 2. Documentation PHPDoc only goes so far. Wikis have better flexibility and can be more easily contributed to by laymen. Whatever is used, it should be standardized, accessible, and utilized religiously. 3. Project management Spreadsheets and barrages of e-mails are time consuming and confusing. Invest in a proper setup for task lists, bug reports, milestones, and some form of work flow collaboration. A couple things to add of a bit less technical orientation:

1. Version control policy
Commit messages are important and useful.
Major development should always be branched.
Symlinking everything instead of using external repositories gets really silly, really fast.
Above all, maintain a clean repository, cruft accumulates quickly.

2. Documentation
PHPDoc only goes so far. Wikis have better flexibility and can be more easily contributed to by laymen. Whatever is used, it should be standardized, accessible, and utilized religiously.

3. Project management
Spreadsheets and barrages of e-mails are time consuming and confusing. Invest in a proper setup for task lists, bug reports, milestones, and some form of work flow collaboration.

]]>