Are you working in one of those big companies which have slow processes and endless meetings? Are you told to work on a task to create an API but you don’t really know how it is going to be used? Are you just following the specifications to make it technically correct?
The knowledge of “How to do things” is the most valuable piece of information developers brings to teams. Sadly, some people think that it is the only thing a developer needs to know to pick him for a project.
We don’t think so.
Even the fastest Ruby on Rails dude, the most skilled Spring developer or PHP hacker will never bring the best value if he does not know what he is actually working on.
How many of you have created an API but have not been told correctly how it would be really used? How many have gasped “They use it like that? I developed all the 17 rest services as described in the spec and now they use only 4 of them. Damn.”
We think that before a developer can do a good work, not only he needs to know “How to do it”, but he also needs to know What he is actually working on.
However knowing What and How is not enough.
We believe that a developers needs to know and understand also the “Why“. When he knows that, he will be able to produce the most valuable and working product.
Why does the project exists? Why does the product exists? Damn, why does the company exists? Everyone should be asking these questions. By knowing and understanding the “Why”, we will be able to produce the optimum solution.
Knowing the “Why” will make us fully understand the goal of projects, products and the company. It motivates us because we see the big picture.
Understanding the “Why” will make decision making so much better.
We always start from What and Why. Then we know How to do it the best.
That works for us. What is your road to success?