[sombremesa]

In my first team at a certain FAANG company, we would never schedule for more than 4 hours a day of coding per dev. Realistically that’s about the time you have thanks to meetings, code reviews, planning, other administrative activities, and working on automating parts of your job.

[rramadass]

>we would never schedule for more than 4 hours a day of coding per dev

Exactly right; And that is on a good day!

I like to read about how the "Great Scientists/Engineers/etc." approached their work and have come to the conclusion that they all avoided "busyness" like the plague. Instead they spent a lot of time thinking about What to do and How to do it before embarking on the job itself. Dijkstra famously did everything using Pen and Paper. I am trying to cultivate similar discipline given that the amount of distractions available on a Computer is orders of magnitude more now.

[bogle]

I particularly like, "automating parts of your job". I wish more organisations made that effort. Especially in large financial enterprises I frequently see the same manual jobs being performed every week because they won't take the time to script it. They'll write up the manual steps, sometimes, but they won't script it, and often it's not even written up.