Programming

17416 readers

108 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 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

How do we evaluate people for their technical leadership? (chelseatroy.com)

submitted 3 weeks ago by rimu@piefed.social to c/programming@programming.dev

1 comments fedilink hide all child comments

Our workflows and productivity metrics regularly ask knowledge workers for things that do not make good knowledge work.

Bloggers on reddit lament how much “meta-work” and “not-work” exists in tech. They kvetch about the conversations and the waiting. They consider the principal engineer’s calendar, packed with meetings, quod erat demonstratum that those roles are “easy” and “airware.” They insist that, if they could manage to not get caught, they could keep several such positions simultaneously and never under-deliver on any of them. None of these jobs, they claim, ask them for all that much code.

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

[–] Mac@mander.xyz 11 points 3 weeks ago* (last edited 3 weeks ago)

I'm but a lowly fidgeter but this is very similar to the age-old IT guy paradox:

Shit's borked! What do we even pay you for???
or
Everything is working perfectly! What do we even pay you for???