How to communicate with a developer

Do you work in a big company like this --they're not efficient, and there's a lot of meetings? Will you do a task to develop an API, but you don't know what it does? Do you just follow the document and technically put it to the correct implementation?

How to do this is the most important information a developer needs to know in a team life. But, in part, this is the only thing developers need to know about the project.

But we can't see it that way.

If you don't know what you're doing, even the most efficient Ruby on Rails guy, the most skilled spring developer, or PHP programmer, can't do anything worthwhile.

How many of you have written the API but can't say where it will be and how to use it? How many people have been angry asking, "How do you use them?" I've developed all 17 Web service requirements in the specs, but now you've only used 4 of them. Damn it. ”

I think a developer who wants to do a good job, besides knowing how to do it, must know what he is doing.

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

I am convinced that a developer needs to know and understand why. Only when you know this can you develop the most valuable product.

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

Knowing the "Why", we can really understand the objectives of the project, the objectives of the product and the company's goals. It inspires us because we see the big blue scene.

Understanding "Why" makes decisions more accurate.

We have to stick with what and why. So we know how best to do it.

The trick worked for me. And how did you get on the path to success?