Do you work in such a big company - the efficiency of their work is slow, endless meetings? You have been told to complete a task, to develop a API, but you Do not know where it will use, how to use? You just put it in the documentation is technically correct implementation?

"How" is a developer needs to know life in the team's most valuable information. Unfortunately, some people think that this is the only developer in the project need to know Things.

We can not think so.

If you do not know what to do really is something, even the most efficient Ruby on Rails guys, the most skilled of the Spring developers or PHP programmers and can not do The most valuable.

How many of you, who wrote the API, but can not tell where they are, how to use? How many people have asked angrily, "You want to how to use them? I follow The requirements of the specifications in the Web Service have developed the 17 over, but now you only 4 of them. Damn. "

I think that if a developer wants to complete a job well done, in addition to know "how to do it", but also must know how to do what.

However, knowing what to do and how to do this is not enough.

I am sure that a developer needs to know and understand the "Why do so." Only when you know, you can develop the most valuable products.

Why this project? Why do I need this product? Damn, why is there such a company? Everyone needs to ask the question. When to know and understand the "Why Why ", we can make the best solution.

Know "why", we can truly understand the project goals, product goals and company objectives. It can inspire us, because we saw the big blue view.

Understand the "why" will make more accurate decisions.

We should adhere to what and why from the start. So that we know how to do the best.

This move is very effective for me. And you how the road to success is it?