6 ms·

Your reading comprehension suffers under your fragile ego. Nobody said 'senior developers shouldn't be coding'. The topic is about a lack of mentoring for juni

Your reading comprehension suffers under your fragile ego. Nobody said 'senior developers shouldn't be coding'. The topic is about a lack of mentoring for junior devs. You being a certified 100x rockstar developer is totally fine but irrelevant, because you don't scale. What would scale is if you were to start coaching junior devs, because if you don't, all the juniors will keep reinventing 'left-pad' in this week's ES201x iteration, while your retirement keeps getting closer. Instead of adding to the discussion on how to solve the coaching gap, you decided to defend your coding efficiency and how you deliver features faster than a Junior Dev. You missed the point completely. You're part of the problem the article addresses, don't you realize?

deleted 9y ago
[deleted]
g051051 9y ago
> Your reading comprehension suffers under your fragile ego. Nobody said 'senior developers shouldn't be coding'. That is exactly what the post I was responding to said, and I've quoted it several times. Here it is a gain, since you keep glossing over it: > 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 So, yes, the person I responded to said "senior developers shouldn't be coding'". > You being a certified 100x rockstar developer is totally fine but irrelevant, because you don't scale. How so? I'm a mentor as well as a developer. In addition to doing my part to train the next wave of devs, I also code my ass off. What part of that doesn't scale? > You missed the point completely. No. That's what you did though. And are increasingly insulting about it as well. > You're part of the problem the article addresses, don't you realize? Who's talking about the article? I was talking about the bogus "point" in the post I responded to.
- atoko 9y ago
  For what it’s worth I agree with the person you’re replying to. The OP is saying: given two senior applicants with the same coding skill level, the one most suited to the job is the person who can communicate to juniors and delegate effectively. I’m surprised you mentor, given all the hubris you have displyed on this thread.
  - g051051 9y ago
    > The OP is saying: given two senior applicants with the same coding skill level, the one most suited to the job is the person who can communicate to juniors and delegate effectively. If that's what he was saying, I'd be much more in agreement. Instead he said, effectively, that senior devs shouldn't be coding because they can't do it any better than junior devs.
    - virgilp 9y ago
      No. Read it again. What I was saying is two things: A. GOOD junior devs can (and often do) outperform good senior devs at the metric of "quantity of code produced" (I later added that IMO in fact they should, not just can) B. (the central point of my argument, really) If you're working on the premise "we can’t afford to have our senior developers mentor juniors" , you're misusing the senior devs. It's not just cost-ineffective (you're paying a senior do to a junior's work), but you also run into other risks as well (juniors that ask questions force seniors to explain stuff, which in turn forces them to think clearly about it; you may have experienced the phenomenon where you understand something much better after explaining it to somebody else)
      - g051051 9y ago
        And I'm saying that your arguments are wrong. I don't care how good the junior dev is, I can out code them every time. > If you're working on the premise "we can’t afford to have our senior developers mentor juniors" , you're misusing the senior devs. Actually, no argument there. Mentoring is indeed a critical function of senior devs. > It's not just cost-ineffective (you're paying a senior do to a junior's work) And you lost me there. 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).
        virgilp 9y ago
        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.

deleted 9y ago

[deleted]

g051051 9y ago

> Your reading comprehension suffers under your fragile ego. Nobody said 'senior developers shouldn't be coding'. That is exactly what the post I was responding to said, and I've quoted it several times. Here it is a gain, since you keep glossing over it: > 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 So, yes, the person I responded to said "senior developers shouldn't be coding'". > You being a certified 100x rockstar developer is totally fine but irrelevant, because you don't scale. How so? I'm a mentor as well as a developer. In addition to doing my part to train the next wave of devs, I also code my ass off. What part of that doesn't scale? > You missed the point completely. No. That's what you did though. And are increasingly insulting about it as well. > You're part of the problem the article addresses, don't you realize? Who's talking about the article? I was talking about the bogus "point" in the post I responded to.

atoko 9y ago
For what it’s worth I agree with the person you’re replying to. The OP is saying: given two senior applicants with the same coding skill level, the one most suited to the job is the person who can communicate to juniors and delegate effectively. I’m surprised you mentor, given all the hubris you have displyed on this thread.
- g051051 9y ago
  > The OP is saying: given two senior applicants with the same coding skill level, the one most suited to the job is the person who can communicate to juniors and delegate effectively. If that's what he was saying, I'd be much more in agreement. Instead he said, effectively, that senior devs shouldn't be coding because they can't do it any better than junior devs.
  - virgilp 9y ago
    No. Read it again. What I was saying is two things: A. GOOD junior devs can (and often do) outperform good senior devs at the metric of "quantity of code produced" (I later added that IMO in fact they should, not just can) B. (the central point of my argument, really) If you're working on the premise "we can’t afford to have our senior developers mentor juniors" , you're misusing the senior devs. It's not just cost-ineffective (you're paying a senior do to a junior's work), but you also run into other risks as well (juniors that ask questions force seniors to explain stuff, which in turn forces them to think clearly about it; you may have experienced the phenomenon where you understand something much better after explaining it to somebody else)
    - g051051 9y ago
      And I'm saying that your arguments are wrong. I don't care how good the junior dev is, I can out code them every time. > If you're working on the premise "we can’t afford to have our senior developers mentor juniors" , you're misusing the senior devs. Actually, no argument there. Mentoring is indeed a critical function of senior devs. > It's not just cost-ineffective (you're paying a senior do to a junior's work) And you lost me there. 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).
      - virgilp 9y ago
        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.