Hi Glenn,

In this article, I want to expose one truth that we often forget, but that acknowledging that we can improve the productivity.

The idea is that just writing new code, typing, is the tiniest task that the developer does. But it is not the most important. The developer needs to read the surrounding code, including that one written by other colleagues, plan how to introduce the new code, and when it is done, if it fails, then debug (which often is the most expensive one).

But that unbalance is necessary. It is like a writer, before writing, he needs to collect information, organize it, and prepare. If he is writing for a publication, he has to catch the tone. And of course, he has to review the text, and rethink that could be misunderstood. Writing is just a small part of the writer task.

And the budget takes that into consideration. Even without know it. Because if the code is harder to read, or harder to modify, programmers rise estimates.

So, acknowledging that writing is a small part of the task, we can aim to reduce the rest, the big ones. And one of the methods, is, for example, investing time in having clean code. I do recommend watching the video about Fractal Architecture to see how it could work.

Thanks for asking, and I hoped it helped.