This well-written article is about much more than just ivory tower architects. Skip the author's bullet points; click on the link and read his article in its entirety. This well-written article highlights many important organizational concepts and trade-offs, such as: - Job Roles vs Job Titles (with product managers, project managers, and product owners included in the example) - Generalists vs Specialists - Organizational Silos and Friction as a result of of overstaffing, or as a result of enthusiasm in the wrong direction You'll also find links to many other insightful articles from the same author (Alex Ewerlof).
Sr Staff Eng | Follow for new perspectives on Reliability Engineering, Growth, and Technical Leadership
How to spot an ivory tower architect? ❌ Have beautiful charts and diagrams but those boxes and arrows don’t map to the reality of how the system actually works ❌ Pretend to represent the average engineer in the leadership table where in reality a tiny fraction of their time (if at all) is spent living the life of the average developer. ❌ Resort to rituals like tech committees which are objectively too expensive for what they deliver. ❌ Demand that all decisions go through them as opposed to teams working together to evolve a system design. Shout out to Neo Kim and Alex Xu who have made system design accessible to the masses. Architecture is NOT a fulltime job. It is every engineer's responsibility. ❌ Engage in high visibility low-impact work like tech radars without lending a hand to do the actual migration or refactoring. ❌ Issuing “maturity models” and “self-assessment” manifestos while conveniently keeping silent about the the responsibility of the company to invest in talent, upskilling, and organizational architecture. ❌ Design systems that look great on paper but are too flaky when implemented. That’s because they miss hands-on experience with the very artifact they’re designing for. ❌ Seeing their engineering peers who are below them in the career ladder as disposable rows of an spreadsheet because “architect is only concerned with tech not the flesh”. Read more about the most important pitfall for Staff+ Engineers, practical tips how NOT to become an ivory tower architect and how to prevent hiring/promoting this type of engineer. #career #staffEngineer #systemDesign https://lnkd.in/dQbw8BxJ