My experience doesn’t match this in terms of resuming after an interruption. For me at least, most coding doesn’t require that high state of understanding everything in every detail, so an interruption is usually not that big a deal.
It’s helped if the interruption is on my own terms though.
it would take 4 hours of concentration to just pronounce “Csíkszentmihályi”
Bless you
Easy, his name is pronounced like: chicks sent me high.
I’m on west coast time, and main office is eastern, my day becomes way more productive once east coast ends their day. No interruption and the last 3 hours are such a good floe state
*flow
I hope you code better than you spell, friend.
I don’t think the simplest of typos on a QWERTY keyboard justifies a correction and snark, does it?
New to the internet?
Its fine , I got a chuckle out of it. That’s inevitable for me on mobile without my glasses on.
My favorite meeting is my 8am standup that’s scheduled for 30 minutes and averages an hour. It really makes sure I have no energy to do anything else that day. Except it’s every day. And most updates are “no updates” with extra words to make it sound like people are doing stuff.
Wow that’s bad. The original idea of standing up, I understand, was to keep the meeting short through physical discomfort and only speak of blockers to progress or ask for help. It is not meant to report status, which can make people feel like they have to continually justify themselves and their work.
Bullshit. I program for much longer periods.
Does that include research time? I sit around pondering solutions, drawing diagrams, planning. When implementing harder solutions, usually 2 hours of actual deep work. But there are days where I wire up the logic and other grunt work, I can do that for 5 to 6 hours.
Data reveal that the median coding time is 52 minutes/day. Meetings consume 11+ hours per week, pushing peak coding to the afternoons when mornings should be prime.
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.
Hyperfocus wants a word.
But, saving this anyway.
