Administered by:
From the original McKinsey document: “one company found that its most talented developers were spending excessive time on noncoding activities such as design sessions or managing interdependencies across teams. “
Heaven forfend that experienced, senior engineers should spend time designing things or helping to smooth collaboration across dependent teams. rather than just banging the keyboard. Only half way through but currently it feels like this report should be renamed code-monkey measurement
@Andylongshaw they obviously missed @whereistanya talk on glue work.
@Andylongshaw Even the idea of “talent” often boggles me. As if outcomes were inherent to the person and not the work process. In the eyes of these people, it’s all destined, there’s nothing you as a manager could (or should do). Your team is doing bad work? It’s not leadership’s fault but just “bad talent.”
@Andylongshaw why can’t you just do what the people who know nothing about your job expect you to do?!?! Why do you have to be such a problem!?!
yeah I was in a company that hired consultants one time. I think one of the 5 that they hired had a clue. Loved that guy. He listened to everybody for a week before opening his pie hole. The rest? Like you describe above.
@Andylongshaw Cross team management is a completely different skillset than writing code. Sure, some people can have both, and it might be valuable to have some of those people around, but requiring everyone with either to do both is detrimental.
@Andylongshaw Who can prove that that McKinsey document (or any other from now on) hasn’t been written by ChatGPT?
@Andylongshaw what the fuck
@Andylongshaw @rodlux I can’t figure out why anyone would ever hire McKinsey. At a friend’s company they took an overworked staff and gave them an extra 10 hours of meta work per week for six months, and then made recommendations that damaged the company
@Andylongshaw once again management consultants proving they have no concept of what they manage. Most of the time should be spent planning and spotting problems in advance, which is what you might imagine happens in design sessions.
@Andylongshaw it's *almost* like software engineering isn't, in fact, "just typing". Whoda thunk.
@Andylongshaw absolutely batshit stuff from McKinsey 