The π’ engineer has good guts but often seems slow compared to the π° engineer.
The π° engineer is quick at decision and gives impression of progress to the product owner often disappointed with the slow pace of change of the π’.
The π’ is busy battle testing the draft he's about to integrate in the product, suddenly he finds out the new bugs were introduced recently by the π°, and decides to postpone his work while focusing on debugging the shit.
In the meantime, the customer complains because of the new bugs introduced in latest release by the π° engineer.
The product owner is worried and decides fixing this bug is a priority.
- The π’ engineer was already investigating the bug and proposes a fix.
- The π° engineer cannot wait for the π’ to fix the bug and already merges new changes in the stable branch so the new release will not only be bug free but also deliver new quality shit.
- The π’ is busy integrating and retesting all the new changes made by the π° as it seems those changes includes critical changes of the core authentication layer and library updates that had nothing to do with the features the π° was working on.
- π° lacks time for testing for side effects, so his changes bring bugs π©, whatever, at least code is delivered, whether it works, that is someone else's problem (π’ of course).
- The π° becomes impatient at the slow π’ and decides to create a hotfix π₯ and deliver his changes to production.
The customer is still unhappy π .
Ignoring the new bugs, the product owner finds it's time for π’ to deliver things too, but is happy the π° is done.
The π’ will be busy with kids at home while also thinking about all new bugs caused by π°.
The π° thinks and claims π’ is not delivering and working enough hours.
The π’ is tortured with this lack of teamwork and with all the shit π© that is being merged in the codebase by the π°.
The π° says it's time to hire more people and he knows other π° who can help and it would be nice if the π’ worked more like π° is doing.
The π’ suggests to focus on quality and teamwork and slow down but the π° and the product owner look at him suspiciously.
The product owner suggests the π’ to consider leaving the team if he's not happy with the way things are. Because in the end, speed and working long hours are important even if results are not perfect.
π€¦ "fuck this shit". A few weeks later, π’ has left.
The π’ is working in a good team nowadays π€², where testing is a thing β , quality is under control π, documentation matters βοΈ, and collaboration is a foundation π€²πͺ.
Related
How the situation should be managed instead by the PO / Lead.
https://workchronicles.substack.com/p/comic-be-like-bob-he-works-long-hours
Don't be like the π°-> See broken window theory.