We, developers, create algorithms, programs, applications. They are often filled for the programmer with the beauty of technical solutions, the grace of architectural approaches, or the elaboration of an algorithmic approach. We enjoy grace and beauty. We often refuse projects where it is impossible to write beautiful code. In our world, we argue to the point of hoarseness about this or that approach that makes the program more perfect. We laugh with programmer memes about code, he june, about seniors, about the numerous coding routine.
Beauty is in our eyes. But the manager is often far from technical details. It is often very difficult to explain the entire programming “kitchen” in the language of Gantt charts. When studying the documentation and reading the library code results in a metric of +10 lines of code. (For half a month.) Well, the truth is, it's somehow not solid - 0.125 lines of code per day. (How many characters per day? And per hour?) Really?
Do we really have to stoop to the level of leaders?
And it's not even about different tasks being solved. The fact that we are programmers, managers and marketers are solving one problem - creating a successful product / service. Everyone in their place are moving towards the implementation of a common task. As leaders or workers, as experts, or as testers, researchers, testers, technical writers, etc.
But still, what about the dialogue?
If you ask yourself: do you need to pass?
Could it be nifty to understand what benefits the user gets from these ten lines of code? If you try to think of the benefits of reducing server load in the 10 lines version of the code. Is it difficult to name the amount of profit? Maybe. But if the server response time decreases by a certain number of milliseconds. For half a month, the view will be different. True?