There is a familiar phrase that I hear all too often when a client comes to me with an existing application.  It goes something like this:

“Our team spent quite a bit of money on our application and we don’t want to ship it.  We are not proud of the product.”

It blows my mind that many developers and development teams are still in business given the poor quality of products that I see getting churned out all of the time.

When I encounter these types of situations, I immediately know that the team (or individual) behind them is much more interested in a ‘quick buck’ instead of the longevity of their company.  Poor quality in software is directly related to cutting corners.

A few examples of cut corners:

  1. Using inexperience developers without proper guidance.  I am all for hiring ‘staff’ level developers, however, they must be properly mentored and trained so that there is no compromise on quality.  If you must compromise on something, compromise it on time.
  2. Outsourcing the project without proper guidance.  Although I don’t prefer outsourcing given the communication challenges, I am not opposed to it.  There are plenty of talented individuals all over the world.  However, given the varying degree of abilities and communication issues, one must not rely 100% on an outsourced team to ship a product.
  3. Not following coding standards/guidelines.  This could be things such as: not commenting code, not testing, not leveraging a QA team, or simply writing “smoke an mirror” code.

I can usually identify immediately which of the above applies after spending a few minutes with the code.  In fact, I have built much of my business around saving these types of projects.

So I urge you, although it might cut into my market share, *please *build something you are proud of.  This is not only the right thing to do, it is also **critical **to your future success as an independant software developer.

Tweet