Writing code is only sometimes about programming a feature or functionality. But it means different things at different times, and an engineer's productivity is directly related to that.
They could be working on creating a prototype one day involving a form or page with mimic data and write 1000s of lines of code within a few hours.
The next day working at bugs could mean different things and involve pre-estimated code corrections around only a dozen lines of code -- but could solve dozens of issues within a day.
On the other day, working on a new feature could involve several hours of mulling it over in the head while appearing to be doing nothing or doing something unrelated. And that is because of the programming part of it, especially the problem-solving aspect of it.
And someday, they can spend the whole day writing and deleting a few lines, debugging, and working on a significant aspect of the same program. Then revert the entire thing in the evening and start their other life to work over the problem to try it in code the next day.
#Code #Programming #Coding #SoftwareEngineering #ProblemSolving #DeveloperLife #Career
This is Mur 
@drupler
by the way, how do you plan and distribute work in software projects for a team?
@mur2501 For me, it is not difficult being a technical person.
There always is a lot of information available from the ongoing activity and brief from daily standup to understand by the end of 2 or 3 weeks to evaluate.
This is for educating non-tech people so that they expect genuine work and not some superman shit daily.