Programming

23570 readers

86 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

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

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

361

Do not Interrupt Developers, Study Says (shiftmag.dev)

submitted 3 months ago by SmartmanApps@programming.dev to c/programming@programming.dev

75 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] lmmarsano@lemmynsfw.com 97 points 3 months ago (2 children)

Funny thing: developers say the same.

[–] Lemminary@lemmy.world 13 points 3 months ago

And what, we should listen to them? Imagine that! /s

[–] anomnom@sh.itjust.works 7 points 3 months ago (2 children)

Abolish open office plans for programming.

[–] BlameTheAntifa@lemmy.world 2 points 3 months ago

But have you considered the magic of being together? 🌈⭐️

[–] ronigami@lemmy.world 1 points 3 months ago (1 children)

Meetings are the bigger problem but yes

[–] anomnom@sh.itjust.works 1 points 3 months ago (1 children)

I could at least plan around meetings, random our conversations and wallops were the bane of my years coding.

[–] ronigami@lemmy.world 1 points 3 months ago

I’ve always found scheduled meetings just as disruptive if not more. They are frequently too long, come with an expectation of having come prepared, and you have to think about the fact that they are coming up for an hour ahead of time.