Last Updated on March 14, 2022
Well, that’s pretty much clear. The act of writing code means that you are in action or you are trying to create something. But that doesn’t necessarily mean that you are moving toward your goal. Basically, if your goal is to finish a project, the number of lines of code does not mean anything at all. It cannot give any indication about the progress of the project.
Personally, when I find myself writing a lot of code to complete a feature or a user story, an alarm rings in my head: “Are you doing the right thing? Why do you need to write so much code for this?”.
It’s true that sometimes you do need to write many lines of code in order to achieve your goal. However, in the majority of cases, there is always an easier and simple way of doing the same thing…
This is one of the reasons why it’s crucial to have a good design and understand the architecture before writing any single line of code. Even a simple proof-of-concept needs to be designed correctly to make sure that you are not just wandering around lines of code.
Developers are like construction workers. They need the blueprint in their head while implementing the solution and they need to know where they are going before starting the work.