I would never use the term “10x engineer” in earnest, but I have a decent idea of what it is. It’s definitely not quantifiable, it just is what it is. When you’ve been around enough developers you know the ones that stand out, that are just exceptionally competent. They will quickly have a better grasp of the system under development than anybody else, including those who have been around a lot longer. If there is a bug that other developers are struggling with, you know who to call to figure it out and unblock them. They’re the ones that aren’t going to come up with cockamamie theories about why something is not working and make a fix with nothing to back it up and hope it works, they’re going to quickly zero in on how to reproduce it and isolate the source of the problem and surgically resolve it. They’re the ones that you always want in your architecture discussion even when they loathe the title of architect. Instead of wasting time on repetitive tasks, they build tools, even if it means doing it on their own time. They’re always looking for ways to improve the system and improve their own skills and know where to draw the line between bringing value and wasting time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I would never use the term “10x engineer” in earnest, but I have a decent idea of what it is. It’s definitely not quantifiable, it just is what it is. When you’ve been around enough developers you know the ones that stand out, that are just exceptionally competent. They will quickly have a better grasp of the system under development than anybody else, including those who have been around a lot longer. If there is a bug that other developers are struggling with, you know who to call to figure it out and unblock them. They’re the ones that aren’t going to come up with cockamamie theories about why something is not working and make a fix with nothing to back it up and hope it works, they’re going to quickly zero in on how to reproduce it and isolate the source of the problem and surgically resolve it. They’re the ones that you always want in your architecture discussion even when they loathe the title of architect. Instead of wasting time on repetitive tasks, they build tools, even if it means doing it on their own time. They’re always looking for ways to improve the system and improve their own skills and know where to draw the line between bringing value and wasting time.