You can code only 4 hours per day. Here’s why. (newsletter.techworld-with-milan.com)
from codeinabox@programming.dev to programming@programming.dev on 14 Feb 01:02
https://programming.dev/post/45735716

#programming

threaded - newest

BCsven@lemmy.ca on 14 Feb 02:39 next collapse

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

PlutoniumAcid@lemmy.world on 14 Feb 06:58 collapse

*flow

I hope you code better than you spell, friend.

NotANick@lemmy.world on 14 Feb 07:42 next collapse

I don’t think the simplest of typos on a QWERTY keyboard justifies a correction and snark, does it?

Alexstarfire@lemmy.world on 14 Feb 10:33 next collapse

New to the internet?

BCsven@lemmy.ca on 14 Feb 16:36 collapse

Its fine , I got a chuckle out of it. That’s inevitable for me on mobile without my glasses on.

BCsven@lemmy.ca on 14 Feb 17:00 collapse

Now you’ve interrupted I will lose 40 minutes. Lol.

Also it’s not whats I’d call true code like what a C programmer would do, it’s a enterprise 3d CAD modeller that has a variety of built in programming automation tools/language, visual rules. So its solving geometry issues, component interaction, and interpart constraints via formulae and code so that the varied consumer parameters (they may alter) don’t destroy the model dependencies, and they still get a product assembly output.

TehPers@beehaw.org on 14 Feb 04:37 next collapse

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.

IanTwenty@piefed.social on 14 Feb 08:38 collapse

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.

nullPointer@programming.dev on 14 Feb 06:33 next collapse

it would take 4 hours of concentration to just pronounce “Csíkszentmihályi”

kambusha@sh.itjust.works on 14 Feb 06:45 next collapse

Bless you

whatsgoingdom@rollenspiel.forum on 14 Feb 10:42 collapse

Easy, his name is pronounced like: chicks sent me high.

MonkderVierte@lemmy.zip on 14 Feb 10:45 next collapse

Hyperfocus wants a word.

But, saving this anyway.

nullroot@lemmy.world on 14 Feb 19:36 collapse

I feel like with neurodivergent types it balances out to around that anyways. Yes, I may spend 3 days hyper focused on a task 10 hours a day, but the rest of the week or month it’s might just be 10 minutes a day I can focus lol.

pinball_wizard@lemmy.zip on 14 Feb 11:01 next collapse

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.

FishFace@piefed.social on 14 Feb 11:08 next collapse

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.

Cryxtalix@programming.dev on 14 Feb 11:17 next collapse

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.

entwine@programming.dev on 14 Feb 17:01 collapse

Idk, I definitely have days where I’m highly productive for more than 4 hours, but I also have days where I work even longer and accomplish nothing. I don’t think a number like that is particularly useful for anything, and only good for micromanagers who need to feel like they can hyper-optimize every single thing.

Interruptions definitely fuck me up though, without fail. Maybe it’s the type of work I tend to do, which generally requires me to keep a lot of context in mind. An analogy I’ve heard that I think works well: It’s like fixing a car, but you have to disassemble the entire dashboard and steering column just to reach the part you need to work on. As you’re doing that, someone asks you pick them up so now you have to reassemble everything to be able to drive the car to pick them up, and then disassemble it all again just to get back to work.