2025-05-26 12:44 UTC
Replies (4)
-
@realn2s@infosec.exchange 2025-05-26 13:11
@CorinnaBaldauf@nrw.social I kind of remember an article stating more or less "if you have a hero programmer, fire them". Not meaning literally to fire them but really keeping them from doing all the work themself. Meaning if something came up what they would normally do, they had to pair with someone and get them to fix it with their help (not touching the keyboard) Sadly, I could find it yet. From my personal experience I can confirm that "losing" hero can actually have positive effects. I lead the development of a project and on two occasions a senior developer decided to leave. I was very shocked the first time. I was doubting that the development could continue at the same pace. After they left 3 people took over, the development pace actually increased. It turned out that everything ran informally through them and it held a lot of things back (sometimes things weren't started at all, as the hero was known to opposed them) The second time I was slightly less worried. The effect was similar.
-
@Reinald@nrw.social 2025-05-26 13:41
@CorinnaBaldauf@nrw.social neben dem, was Claudius sagt: auf die Führungskultur einwirken, dass Einzelgänge keine Belobigung mehr bekommen. Da gibt es eine Wechselwirkung zwischen den goldenen Rittern und der Führung, die da an der Planung vorbei Sonderaufgaben zuordnet. Manchmal sind da auch noch teamfremde Nebenprojekte im Spiel, die hilft dann auch organisatorische Entflechtung. Meist sind mehrere Faktoren beteiligt...
-
@scrumschau@mastodon.social 2025-05-26 14:04
@CorinnaBaldauf@nrw.social It will not solve your question but could be useful to catch the topic: https://mastodon.social/@SenseException@phpc.social/110209511694547139
-
@scrumschau@mastodon.social 2025-05-27 11:15
@CorinnaBaldauf@nrw.social soetwas in die Richtung? https://dev.to/codeshipper/the-hero-developer-must-die-my-journey-from-midnight-savior-to-team-builder-50k2