The story of little printf

[MrRoboSteve]

I also recognize every single character in that story.

I've found that it's a battle to avoid falling into one of those stereotypes. Despite having had the "architect" title for several years, I routinely commit code to our service (most recently yesterday afternoon), participate in code reviews, and take my turn in the on-call rotation. All of those things keep you grounded in what is really going on.

Notes on each role:

Chap 4 -- sr engineer -- stops getting promoted because lack of influence over others
Chap 5 -- poseur -- eventually fired from competent places
Chap 6 -- the real engineer
Chap 7 -- framework fad lover - only thing missing here is him having his own framework
Chap 8 -- devops -- managers love these people because they don't complain
Chap 9 -- architect -- this one seems quite disconnected
Chap 10 -- Ghosts of Christmas