[bungie4]

30+ year programmer here. This is absolutely true. Some days you cause more damage then progress, forcing you to spend still more time correcting it.

My supervisors understand that some days I'm not going touch code, instead I'll spend my time on education by keeping up with new tech, or, writing docs.. anything but talk with other co-workers distracting them

[thirdsun]

> My supervisors understand that some days I'm not going touch code, instead I'll spend my time on education by keeping up with new tech, or, writing docs.. anything but talk with other co-workers distracting them.

Couldn‘t agree more. There are days I spend exclusively reading and thinking. I regard keeping up on technology, thinking about potential approaches and solutions to various problems we’re facing as an essential part of my job. To an outsider that might look like a pretty relaxed work life, but this kind of preparation allows the actual execution, the thing that looks like work, to be the easiest part of a project.

[Viliam1234]

> There are days I spend exclusively reading and thinking.

And you admit to do so openly at your daily agile meetings?

Because for me, the problem is that every day I am expected to produce some code, and reading is something... that is kinda supposed to happen... but at the same time it is also not supposed to actually take time, at least not on the scale of days.

[thirdsun]

Admittedly, I'm in a comfortable position that allows me to be very liberal with how I spend my time at work. I'm a developer at a small company that isn't focused on tech, but manufactures physical porducts - there aren't any agile meetings and to the rest of the staff that kind of work looks like black magic.

[mattmanser]

That's the problem with daily standups, they're micro-management.