> One single-handedly wrote 85% of <extremely popular and complex app you've used> and another wrote most of the internal libraries at <company you've heard of

> One single-handedly wrote 85% of <extremely popular and complex app you've used> and another wrote most of the internal libraries at <company you've heard of>. There is a trap here, though. There is another group of engineers, who jump on any greenfield project before everyone else manages to discuss the plan and then they write some code very quickly, showing you a "finished" solution. Those people often appear 10x to management as well. However, after deploying their code to production, it turns out it has many issues and is a source of never ending frustration for the people who maintain it. Unfortunately at that time the "super hero" has moved to a new greenfield project, and is not willing to fix their bugs or help because they are "busy" or "in a flow". I don't think those people are really 10x. They are often an annoyance to the rest of the team and if the management doesnt break this pattern early, you end up with a team where one person codes 90% of stuff, gets most of the credit, but 10 other people get frustrated maintaining it, and overall the team pace is not 10x higher, but may be even slower than a similarly sized group of average devs. So if you are in a management position, don't just look at how much code a person writes in a short time or what percentage of the product they created, but also look at the quality of their work and how good they are at sharing their knowledge with the rest of the team. Having said that, I have met some true 10xers who created high quality stuff fast and were very helpful to their teammates, but they are quite rare and often don't get all the praise they deserve, particularly in environments valuing the "ship fast and break things" strategy.