Experienced Solution Architect | Designing Impactful Solutions | AI Explorer | Business Transformation Leader
The entire plot of the Iliad is like one big code review gone bad. You just spent the better part of the week painstakingly building out that killer new feature. In fact, it's some of your best engineering, the unit tests are a work of art, and the function names would make Uncle Bob proud. But not so fast! The next thing you know your work is completely ripped apart by someone more senior. This is what sparked the rage of Achilles! Agamemnon used his opportunity to save the Greek army as a means to assert his dominance over Achilles, rather than leading as he should. Agamemnon took what was treasured by Achilles in front of everyone setting in motion the epic on anger and pride. At one time or another we've all been tempted like Agamemnon when giving a review. So remember, code reviews aren't a means to satisfy our own pride and insecurities about our position. Have you ever been in a code review that felt more like a battle than a collaboration? Let's turn these moments into opportunities to learn and grow with each other rather than using each other. How do you ensure your code reviews are constructive and empowering? "Achilles’ wrath, to Greece the direful spring Of woes unnumber’d, heavenly goddess, sing! That wrath which hurl’d to Pluto’s gloomy reign The souls of mighty chiefs untimely slain;" - The Iliad, Book 1
SVP of Delivery
4moLGTM (approved)