[virgilp]

Look. Aren't you spending time thinking? Do you imagine you think faster than everybody aged 23?

Could you do an MSc at a top-level US university (in your primary domain of expertise) in a week? Because plenty of people (juniors by definition, almost all of them) can do it in 2 years, so if you're "100x" in the sense that you say you are, you should be able to do all that work in 1 week. At least that much should be plainly obvious to you, that you can't possibly be "100x" in the sense that you claim to be. Or well, if you are... you're rather unique, I definitely haven't seen anybody that can even come close to you, and I know some top-notch engineers. So you're definitely the exception, not the rule.

[g051051]

> Aren't you spending time thinking? Do you imagine you think faster than everybody aged 23?

No, but I probably think better...i.e. how to approach a problem, sift out the relevant details, formulate a plan, execute it, understand the trade-offs, etc. As a result, I can deliver more correct code faster than a junior dev.

> you can't possibly be "100x" in the sense that you claim to be.

I never claimed to be 100x. I was just mentioning the reason why I'm cheaper than a junior dev (that I'm not paid in line with my "effectiveness multiplier"). You were the one that mentioned a 100x engineer thing in a link, so I included the number.

[virgilp]

> I never claimed to be 100x.

You actually did - look 2 posts up, "i.e. I'm a 10x (100x) dev". But I suspect you didn't actually read that link, just the URL - not fair to chide me for mentioning the number if you didn't read what that meant.

> how to approach a problem, sift out the relevant details, formulate a plan, understand the trade-offs

That's exactly my claim, that you add more value with this sort of activity than the "execute it" part; doing that plus teaching others to do it, you add exponentially more value to the company, than just coding stuff in a corner .

You cling on the fact that a junior dev can't possibly code faster than you - even though it's a completely irrelevant detail. And yes they can, if you remove qualifications like "correct code" or "maintainable" or whatever (I never claimed junior devs will do the right thing all by themselves, that'd make them seniors, right? But - I participated in coding competitions in high-school, got a silver medal at IOI - I know very well that my younger self could code circles around my older self when it comes to raw speed. And I've seen other people like that later; experience can't fight youth when it comes to speed and enthusiasm... it just can't. It's more likely that you just never worked with a good junior dev before, than it is that you can always code everything faster).

[g051051]

Actually, the context that you're ignoring is important:

> I'm so much more effective that it's always cheaper to have me do it, assuming I don't have a higher priority task (in which case it's a non-issue, since I'm working on that one). I.E. I'm a 10x (or 100x) developer, but I don't get paid 10x (or 100x).

The numbers were merely to indicate that my multiplier is sufficient that I'm cheaper than a dev.

> I suspect you didn't actually read that link, just the URL - not fair to chide me for mentioning the number if you didn't read what that meant.

No need to suspect, I confirm I didn't read it. I saw the number in the URL and just dismissed it as puffery.

> That's exactly my claim, that you add more value with this sort of activity than the "execute it" part; doing that plus teaching others to do it, you add exponentially more value to the company, than just coding stuff in a corner .

That was in no way you're claim, at least, not the claim I disputed. Your claim(s) were:

> You don't hire senior devs to code - good junior devs can code not only "just as fast", but probably faster too!

> "Mentoring" is basically the job you hire a senior dev to do

No way. Maybe mentoring is a part of the job, but it's by no means the main job in many organizations.

> if you remove qualifications like "correct code" or "maintainable" or whatever

??? This is a pretty ludicrous statement. Why would you ever count incorrect code? And yes, I probably can code incorrectly faster than a junior dev, too. After decades of experience, I'm a faster typist than most junior devs.

> I know very well that my younger self could code circles around my older self when it comes to raw speed. And I've seen other people like that later; experience can't fight youth when it comes to speed and enthusiasm... it just can't.

Rose colored glasses, to say the least. You seem to be switching back and forth on whether raw LOC throughput is meaningful...first you were "flabbergasted" that it might be a measure of productivity, now you're bragging about raw speed, and even suggesting that creating "correct code" or "maintainable" code is irrelevant, which is insane.

> It's more likely that you just never worked with a good junior dev before, than it is that you can always code everything faster).

I've worked with (and mentored) some really great junior devs, who grew into great senior devs. But they didn't walk into the building as my equals in coding.

[xigency]

Education is a good point. New algorithms are often found in academia that aren't exactly on Hacker News all of the time. It doesn't matter which field either - micro architecture, high performance computing, UX, databases, PL, computational linguistics, you name it. Or hell, math has been around for a long time and you might not know planar graph algorithms off-hand unless you were really smart or had taken the course two months ago.

This whole debate is nutty. I personally would welcome as much strategic and intellectual diversity as possible onto teams I'm running. I wouldn't put all my eggs in one basket, either.

[g051051]

> I personally would welcome as much strategic and intellectual diversity as possible onto teams I'm running.

Me too. I just think the blanket assertion that a junior dev is the coding equal to a senior dev is what's nutty.