[capttruckerdave]

I love typing - it just makes a little ping in my little lizard brain. But if one of my jr teammates are typing out every single character of their code I will slap their ass and teach them about autocomplete and github copilot. So much faster to have jr type their code (as in define the types) and leave the typing (as in the writing) to the editor.

That still doesn't stop us from having typing (as in writing) races at the office which is a fun thing.

[junon]

I'm a principal and do not use either of those things at all. You sound miserable to work with if I'd get a slap for that.

[geraldwhen]

If rephrase that as “use moments of inefficiency to teach juniors how to use their tools better”

Showing someone how to use column edit, or macros, or automated method refactor, will change their productivity dramatically. It’s the role of leaders to teach and empower.

[junon]

Yes, that I agree with.

[cromulent]

Agreed.

The article makes a good point about how little of software development consists of typing. This matches with my experience also, over several decades. There are so many things to optimize before "code input speed".

20 years ago, one of our guys hurt his arm and had his arm in a sling. The customer asked for a 50% discount on his rate - it was clear they saw software development as "fancy typing" rather than a process of turning business requirements into functional software.

[badcppdev]

Do you recommend that the junior staff you supervise use autocomplete and other code generation tools? Do you use an IDE with linting, etc?

[junon]

I don't recommend them anything unless they're struggling with something. I would certainly never suggest copilot.

The way I see it, they're juniors because they need guidance and to gain understanding. You cant do that with a computer writing code for you.