Striving for Excellence: Why Being a 1x Engineer is Better
Written on
Chapter 1: The Myth of the 10x Engineer
You've likely come across the term "10x engineer." This concept refers to engineers who are said to produce code at a pace significantly faster than their peers. However, quantifying what it means to be 10x or 100x is ambiguous; whether it's measured by lines of code, the speed of problem-solving, or features delivered, the notion of a 10x engineer is more theoretical than practical.
Should you aspire to be a 10x engineer? Is it a worthwhile ambition?
The premise is fundamentally flawed and potentially harmful for several reasons.
Being labeled a "10x engineer" can lead to detrimental outcomes within engineering teams. Here are some of the pitfalls:
- Spending excessive hours coding, often beyond regular work hours.
- Viewing colleagues as "slow" or "B players."
- Believing that you are the only one who comprehends a particular feature.
- Becoming defensive during code review processes.
- Ignoring team discussions and opting to implement personal ideas without collaboration.
- Feeling irritated when pairing with other developers.
- Writing convoluted code under the assumption of superiority.
Section 1.1: Embracing the 1x Engineer Mindset
Adopting a bit of humility in your engineering career makes you a more effective team contributor. Even if you produce more code than others, it’s essential to do so with a humble approach:
- Once the workday concludes, make sure to disconnect and recharge.
- Cultivate interests outside of programming.
- Foster positive relationships with your team.
- Participate actively in team discussions, such as RFCs, sprint planning, and architectural dialogues.
- Write thorough unit tests that ensure your code is dependable.
- Engage in constructive feedback during code reviews, recognizing the contributions of others.
- Take the time to connect with colleagues over coffee or lunch.
- Research solutions before seeking help.
- Update documentation when you discover new information.
Subsection 1.1.1: Fostering Curiosity and Creativity
Setting out to write clear and understandable code collaboratively is an admirable goal. Cultivating curiosity about software, coding, and the underlying principles is a valuable trait. It's crucial to invest time in improving your skills and becoming a better engineer.
However, striving to be a "10x engineer" is misplaced.
The "10x" archetype can be detrimental, promoting negative behaviors rooted in an inflated sense of self-worth. Instead, it’s far more beneficial to focus on being a "good engineer" and leave the unrealistic expectations behind.
Chapter 2: Inspirations and Resources
The motivation behind this reflection on the "1x engineer" concept stems from the website 1x.engineer, which provides a delightful, community-driven compilation of traits that define a "1x engineer."
If this discussion resonated with you, you might enjoy exploring that platform for additional insights.
The first video, "The 10X, 1X, 0X and -X Engineer," delves into the implications of these archetypes and their impact on engineering culture.
The second video, "How to -10x Engineer Correctly," offers practical advice for engineers looking to cultivate a healthier work approach without succumbing to toxic competitiveness.
More Resources
- DeveloperPurpose.com — A platform dedicated to building a meaningful and purposeful software career.
- Why Working for FAANG Might Be a Misguided Ambition — Insights on the pitfalls of aiming for big tech companies.
- Software Development Groceries — A metaphorical exploration of effective coding practices through the lens of a grocery store.