Great post on slashdot about setting up a proper environment web developing. I’m posting a good one here for future reference. Enjoy.
Actual article here.
Actual comment here.
This is Unix/OSX-centric, and I’ve been doing this for years and showing others the way:
* My code always has a standard layout (bin, conf, src, lib, and so on). No exceptions, because you never know when that little script will become a big app (this happens to me at least once a year).
* Use good coding practices: unit tests, continuous integration, whatever
* The code is checked into CVS/Subversion/Darcs, whatever. Use branches and so forth intelligently (dev on the trunk, release branches which are bugfix only, whatever). Make it “obvious” where the latest stable code always lives, so that someone besides yourself can deploy it.
