The Sins Of Development Companies

QArea Team by QArea Team on September 17, 2014

The Sins Of Development Companies
Reading Time: 2 minutes

What sins are mortal to a development company?

Practically the basic 7 list may be applied to software development as well as any other field of human business. Although the sins are slightly different from what we are canonically used to. Still they may bring a company to ruins.

  • Lust. There is a difference here. If you can make other people lust for your products you are a winner. That is some good business you are having. The lust of developers, on the other hand, is the lust for perfection. A commonly shared sin among developers worldwide. There are multiple examples where seemingly limitless resources and the strong desire to create perfection were bringing great companies with splendid ideas to rubbish and clutter due the fact that by the time their brainchild is released it is useless due other, faster people have already released cheaper solutions that are now popular. Please remember, there is no such sing as perfect software in existence.
  • Gluttony. Yes, hardware is constantly improving and is becoming more advanced. Still that fact does not mean that your software has to be eating all the machines CPU and hardware space. Batteries are not eternal. That is way smaller programs are still the key to success and, I believe, they will always be the way you wish to develop. Plus, the less code, the less bugs, the easier it is to maintain.
  • Greed is no good way to determine how the project has to be going on. Profit is important, yes. But still if you are constantly chasing for more you will hunger for more smaller features in the shortest time possible regardless of quality. Your users will not be appreciating such an approach.
  • Sloth. Not laziness, no. Lazy workers are great actually. The really lazy person is the one that is developing single sign-in feature in order not to put in the logins/passwords all the time. Sloth is apathy. If the developer cares not about his work he is the most dangerous guy on the team, trust me.
  • Wrath. You believe that your developers are calm and peaceful folk? Try reading the notes they are leaving in the source code. Those comments are to determine on who is actually the passive aggressive guy that gets angry of criticism and enjoys pointing out mistakes of others. Still they are the OK guys. And the silent one that never asks any questions is the one you should worry about. Perfect developers have their strong opinion on practically every aspect yet they also love to debate and are not afraid of admitting mistakes if they are pointed out. And the one that is never asking is not getting better.
  • Envy. Sure you have competition. And that is ok. Yet don’t envy their success and don’t become a copy-cat. Stick to your idea and before implementing somebody’s successful feature stop for a second and ask whether your piece of software actually needs it.
  • Pride. If your developers are too self-confident that is never good. The ‘just trust me’ approach when the ouds are against that particular decision can indeed lead you to victory. Yet the chances of that are somewhere around 1 out of a 100. Know what you are risking.