Thanks for coming back for Day Three!

[Note: Sorry this post is a day late. It was all ready to go late yesterday, but some of the code included below triggered a bug either in WordPress or ScribeFire and the whole post got mangled. I managed to resurrect it today ...

Welcome back.

Ready for Day Two? Did you get your "hello world" app running on your host?

Where We Stand

Yesterday we nailed down our concept, bought a domain name and hosting, set up our toolkit, and deployed a practice app on the host.

Here are five reasons you should wait before moving on to the next phase of your software development process:

1. Get the requirements right. It's so often repeated that it's almost a cliché to say that requirements errors will cost 10x or more to fix during coding or testing ...

Here are some simple things you can do - today - to find and prevent bugs in your code. These take very little effort to implement and do not cost any money. (And typically don't require management approval.)

1. Turn on warnings.
2. Make warnings break the build.
3. Review your code.
4. Get a ...

This is the second half of an article I posted about using a checklist to prevent security errors. There, I said that you have 15 checklist items max, and you shouldn't waste any of those questions on silly things like "Does the code follow the coding standard?".

Jason Cohen ...