Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (42)

On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 The future is bright Mar 30, 2025 2024 Reflections Dec 31, 2024 The day I became an architect Sep 11, 2024 Are developer jobs truly in decline? Jun 29, 2024 Form follows fiasco Mar 31, 2024 Thanksgiving reflections Nov 23, 2023 Working from home works as well as any distributed team Nov 25, 2022 Book review: Clojure for the Brave and True Oct 2, 2022 The Toxic Clique Sep 28, 2022 All developers should know UNIX Jun 30, 2022 Good developers can pick up new programming languages Jun 3, 2022 Java is no longer relevant May 29, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Best practices for building a microservice architecture Apr 25, 2022 Kitchen table conversations Nov 7, 2021 What programming language to use for a brand new project? Feb 18, 2020 On elephant graveyards Feb 15, 2020 Microsoft acquires Citus Data Jan 26, 2019 Teleportation can corrupt your data Sep 29, 2018 What does a Chief Software Architect do? Jun 23, 2018 Leaving Facebook and Twitter: here are the alternatives Mar 25, 2018 When politics and technology intersect Mar 24, 2018 The technology publishing industry needs to transform in order to survive Jun 30, 2017 Why it makes perfect sense for Dropbox to leave AWS May 7, 2016 LinkedIn needs a reset Feb 13, 2016 In memory of Ed Yourdon Jan 23, 2016 IT departments must transform in the face of the cloud revolution Nov 9, 2015 We Live in a Mobile Device Notification Hell Aug 22, 2015 What Every College Computer Science Freshman Should Know Aug 14, 2015 On Maintaining Personal Brand as a Software Engineer Aug 2, 2015 Book Review: "Shop Class As Soulcraft" By Matthew B. Crawford Jul 5, 2015 The Clarkson School Class of 2015 Commencement speech May 5, 2015 On Managing Stress, Multitasking and Other New Year's Resolutions Jan 1, 2015 Software Engineering and Domain Area Expertise Nov 7, 2014 Infrastructure in the cloud vs on-premise Aug 25, 2014 On anti-loops Mar 13, 2014 On working from home and remote teams Nov 17, 2013 Thanking MIT Scratch Sep 14, 2013 Thoughts on Wall Street Technology Aug 11, 2012 Scripting News: After X years programming Jun 5, 2012 Eminence Grise: A trusted advisor May 13, 2009

On elephant graveyards

February 15, 2020

Some years ago I heard someone sarcastically say “This is where elephants come to die” in response to me asking them what is such an intelligent person as them still doing in that company.

Since then I have been referring to “elephant graveyards” when describing companies and teams that don’t have room for intelligent people to rise up the ranks and grow as engineers.

An elephant graveyard, when applied to a corporate setting, is a team, company, or some other set of conditions in which otherwise bright engineers are forced into positions or assignments where there is no hope for future career growth. In this post, I hope to define the conditions that must be present for an elephant graveyard to form, how to detect them, and how to navigate them.

Defining career growth


An engineer's career growth has three dimensions: skills, recognition, and compensation.

Skill growth is a function engineer learning new skills and becoming an expert through practicing newly acquired abilities on real-world projects.

Recognition is a function of showing initiative, applying new skills, and being recognized by supportive leadership.

Compensation is a function of recognition and skill growth.

Conditions required for an elephant graveyard to form


An elephant graveyard forms when the three dimensions of career growth become stagnant.

Skill growth stagnates when the project reaches a certain level of maturity and is either no longer growing or is in a terminal decline. Projects reach maturity when they reach a critical mass in production and are no longer rapidly evolving. When the active development phase is over, the projects are often scaled back. When projects don't rapidly evolve, there is no room for the acquisition of new skills.

Another reason for skill growth stagnation is presence of The Smartest Person In the Room. The Smartest Person in the Room is either the developer themselves (which means they've outgrown the project and are now a toxic influence on it), or someone else (who created the conditions in which only his ideas are good).

The emergence of The Smartest Person in the Room is toxic to the team and good leaders should discourage it. Since only their ideas count, the rest of the engineers can't grow and earn recognition.

Recognition stagnates when either skills stagnate or the engineer loses the support of the leadership, including due to management incompetence. When leadership is unsupportive no new skills will earn recognition.

When both skill growth and recognition stagnate, the compensation stagnates as well. Well-run companies reward engineers. Poorly run companies don't have the money to reward them. Companies that create artificial limitations due to parochial title hierarchies run the risk of not rewarding technologists and losing them.

What to do if you find yourself in an elephant graveyard


First of all, try and detect an elephant graveyard before you join the company. Ask questions about team dynamics and the project maturity cycle. Don't join a company or a team where elephants come to die.

If you find yourself in an elephant graveyard, however, it's not all over. Evaluate your overall situation. Is work-life balance important to you at this phase of your life? Are you being fairly compensated at this moment in time? Are there opportunities within your company on other projects? Is there an opportunity to shake things up on your existing project?

As long as there is room to grow, there is no reason to be restless. You are not an elephant and you are not in a graveyard. Not yet, at least.