Are consistent coding conventions important? To many stand alone developers, the words "coding standards" may sound like fingernails on a chalkboard.

I remember an integration project that I worked on and it was crazy, chaotic, and it simply failed. I was working for a big consulting company, and we were integrating their bandaid solution hack code into a new CRM system. Boy, we didn't realize what we were getting ourselves into. The client was upset about the delays after delays, but we had to deliver the bad news that their code was so messy that we'd have to basically re-write all their lines. Obviously, they were not happy with this.....needless to say, they couldn't find another company to successfully integrate with their code.

Many engineers don't like to adapt to a company's coding standard or convention, but you know what, it's tedious...but it's important. When you have one developer, maybe not that important, but when you add 3 or 4......they better all be on the same page. It's important for a startup company to establish this type of development culture right away; otherwise, you'll end up having to play the sheriff in the wild, wild west.