[ramraj07]

There’s always a hoarde of people second guessing the 10x engineer. Of course it looks impossible to regular folks. I have seen a few people like this. They’re real. Sometimes it’s even worth the dysfunction they cause to see this in action.

[kpandit]

Not commenting about the ppl who are subject of this thread but talking in general. I have been lucky enough to have seen some of these 10x engineers but what is much more common is a 1x engineer feeling and treated like a 10x engineer because they are surrounded by 0.1x engineers.

[Xcelerate]

Haha, that reminds me a lot of this quote from an Atlantic article on Freeman Dyson:

I asked him whether as a boy he had speculated much about his gift. Had he asked himself why he had this special power? Why he was so bright?

Dyson is almost infallibly a modest and self-effacing man, but tonight his eyes were blank with fatigue, and his answer was uncharacteristic.

“That’s not how the question phrases itself,” he said. “The question is: why is everyone else so stupid?”

[wavewrangler]

That’s still 10x. If you think that’s worth mentioning, you should see the 10x engineers swoon over the 100x unicorn.

[vasco]

Same, I've seen it in practice and the numbers didn't lie, week on week on week. But you know, some people are very uncomfortable with someone else being called smart. Worse yet what if they're called smarter than what they actually are? Like an injustice in the universe, but comes from defensiveness I think.

I don't know this guy in particular so I have no clue though.

[NhanH]

I am not second guessing the 10x engineer, that topic is not the one under discussion.

The topic at hand is “how did a high level engineer got to focus on programming”. And I am saying that the reason has to do more with his influence and role within the organization, rather than other reason.

[pydry]

>There’s always a hoarde of people second guessing the 10x engineer.

Because most 10x engineers recognized by management as such are characterized chiefly by building out shoddy software extremely quickly that only they can understand.

In a similar dynamic, Doctors that are scored highly by patients often have pretty bad medical outcomes.

[blurbleblurble]

I've seen the bugs of multiple 10x engineers multiply together for 10^n x bugs

[datameta]

In my experience I have encountered two 10x engineers:

1) Moves fast, flexes their authority to sweep small stuff under the rug until it is out of scope and can be "fixed real quick" later. Often leverages many subject matter experts through effective and persistent communication and learns quick enough to get PRs through the door (that sometimes need "quick" fixes later). Enjoys selecting items that benefit their career the most, at the expense of others on their team. Mentors only enough to onboard and increase his team's yield, not to aid their careers. Fueled by the recognition and validation of peers through PR/project completion.

2) Gets shit done, is the SMI themself. Solo code cannon, but PRs go in clean, beautiful to look at. May not get along well with some but not necessarily abrasive to work with especially being part of their direct team. Can be a great altruistic mentor if they spare 5% of their time. Enjoys what they do, and the technologies they work with. Fueled by personal satisfaction in their achievements, and in uplifting their team.

[pixl97]

Typically when you see the type 2 engineer, they are also an architect. It is very rare that they don't seem to have knowledge of nearly the entire system and all its interactions.

[chucke1992]

Sorry, but what is SMI?

[datameta]

I just engaged in the kind of acronym abuse I don't enjoy receiving! It stands for Subject Matter Expert.