My Take on The 10X Engineer Myth

-

Lately the tech landscape is discussing a lot about the 10X engineer myth. It has always been a very interesting point to discuss. What makes a 10X engineer and where to find them? What’s my take on what makes a 10X engineer? Let’s see in details how I see it.


No I don’t see Rambo as the ideal 10X Engineer.

Based on my own experience, a 10X engineer is that team member that is able to perform to his maximum abilities. The engineer enables other team members to be as effective as possible in unlocking the team’s value. Here are some values that describes a 10X engineer.

First, the engineer understands what he knows well and is well aware of the areas he needs to improve. The engineer should be able to understand the problems he’s trying to solve by applying his knowledge or by asking the right questions to gain as thorough understanding of the problem. A good understanding of the problem will leads to a more effective problem solving.

Second, the engineer is able to apply the right amount of solution to the problem. Start with the simplest approach that solves the problem. Let the more complex solution comes later when needed. The first draft should solve it first. This way, the engineer does not over-engineer a solution. Instead, use that extra engineering bandwidth on other things that needs solving.

Third, the engineer has a high sense of ownership to the problem he’s solving. This way, the engineer will pay attention to the big picture as well as the details of the problem. Edge cases are often identified early by the engineer. The engineer will do things that are needed, not simply following instructions.

Fourth, the engineer is able to understand how his teammates think. Let’s face it, engineering is a team sport. When you understand how your teammate thinks, each one of you knows each other’s hindsight and can cover one another. This way, a thorough solution to a product is crafted.

Fifth, the engineer is not selfish and thinks for the good of the product and the team. If you can’t work in a team, you have a harder chance to succeed nowadays. I’m not saying that if you’re a solitary rockstar then you can’t be successful. All I am saying is working good in a team will make a product better. The goal is always how we solve the problem better. That way the user wins. It’s not about whose code is better, it should always be about how we provide the best solution. It’s nothing personal, it’s just business. The best engineers in my team are those that acts as enablers, thinking for the good of the team and the product.

Sixth, the engineer is always curious. A curious engineer will be able to always make his code better and will always strive to expand knowledge and hone the problem solving skills. When you stop being curious is usually when you think that you know better than anyone else and you’ll start going downhill from there. As engineers you will always need that technical knowledge and you always have to try to make it better. After all, engineering is a technical job.

These are the six qualities that I think is very important in achieving that 10X myth. Let me know what you think are the qualities that makes up a 10X engineers.

Regards
-E-

follow @femmerling on twitter
visit my website

Comments

Post a Comment

Popular posts from this blog

Customizing Sanic's Logging output on Gunicorn

-
For those of you who didn't know, Sanic is a Python 3.6+ web server and web framework that’s written to go fast. It allows the usage of the async/await syntax added in Python 3.5, which makes your code non-blocking and speedy. Sanic's API is highly influenced by Flask and the API is really good. I worked on a personal project lately and found out that doing custom logging on Sanic is quite hard. You don't get a lot of information from Sanic's logging library and since it's based on the default Python 3 logging library , the information it provides is limited. My initial thought was since I will use Gunicorn, let's use Gunicorn's --access-logformat to get the information I needed. The functionality provided a lot of information and I can make use of it to get what I need. However, when you use Sanic Gunicorn Worker, which you need to use to make it work on Gunicorn, it will only use Sanic's logging output. I did a lot of googling and it seems like a lo
Read more

5 Takeaways From My Past 5 Years With Coral, Prism, Midtrans and Gojek

-
Image
A little over 5 years ago, I decided to resign from Traveloka and joined hands with my friends to help build Coral. It was an exciting project. I have a big interest in the social commerce space and Coral seemed to be a very good take at it. We built it, launched it, learned from it and in the end decided that the business model will not be sustainable. Our experiment was evidently working. Merchant's conversion rate reached over 20% on our platform but we couldn't monetise it. Then we took the decision to pivot. We took the best part of Coral, the chat-to-buy capability, and breathe life into Prism. The product helped businesses dive head first into the social commerce space with their existing platforms. One thing that a lot of people don't know was that Coral and Prism was part of Midtrans from early on. It was acquired before launch. This enabled us to do the experiment without worrying about funding. Gojek acquired Midtrans during the closing days of 2017 and Prism w
Read more

Lessons From Leading and Developing Product Engineering Teams - Part 1

-
Image
The WFH period gives me extra time to think and reflect back on the lessons I’ve gained throughout my 15+ years career. I spent most of it leading others and I've gathered a lot of practical knowledge. I want to share it to help others learning to take up leadership. So, here are some important lessons about leading people based on my experience. It's a long read, so please bear with me, I'll split it into 3 parts. #1 - It all starts with trust Hire people you can trust. This brings a world of difference to the team dynamics. On every interview, I always ask myself the following questions. Can I trust this person? Will this person help the other team members? When I am confident to hire someone, it means that I trust that person enough to work with the other team members. The mindset I establish would always be Trusted, until proven otherwise. I mean, why would you even hire someone you can't trust? I've seen a lot of people hiring people but are too afraid to trust
Read more