126
You can code only 4 hours per day. Here’s why.
(newsletter.techworld-with-milan.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Feb 2026
126 points (93.2% liked)
Programming
26192 readers
209 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Shit. I knew it was low, but that's awful.
As an engineering manager, I use all of the approaches described in the article, and a few others.
It does make a tremendous difference both in output of correct solutions, and in team member retention. And team member retention saves big money - having to spend 18 months to train new a subject matter expert every three years is expensive.
The 18 months onboarding every three years (per each pod of five developers) was the average re-training cost on my teams before I mastered these (and a few other) techniques for managing creative engineering talent.
Edit: and for those who say "I've heard it takes less than 18 months" - yes, I know. I probably lied to you to protect my own job. Haha. The truth is important, but the full unvarnished truth is not more important to me than my collecting my next paycheck.