3 ms·
I've found the AI tooling very helpful for 1:1 pair programming with junior developers. The AI tends to provide bad code at "100%" but it prevents me from const
by thechao 3y ago
I've found the AI tooling very helpful for 1:1 pair programming with junior developers. The AI tends to provide bad code at "100%" but it prevents me from constantly having to take the keyboard away from the junior — I can just prompt the junior to type a bit, the AI fleshes out the rest, and we talk about how/why the AI isn't quite right, and what should be correct. The junior is typing the whole time. It really helps, a lot. Probably cuts 1:1 time in half, or better (re: it doubles the amount of stuff we can cover).
- deleted 3y ago[deleted]
- kijin 3y agoWhen I'm working with a junior developer I have a rule: never, ever, touch their keyboard or mouse while they are driving. If I absolutely have to help them make some specific input, I'll spell it out, symbols and all, so that the junior can type it themselves. It takes time, but it's so much easier to remember something when you're the one who typed it out. Besides, even before AI, autocomplete was usually good enough that I rarely had to spell out more than a few letters. :)
- thechao 3y agoYeah — that's what I was doing before AI: clearly spelling out each character, character-by-character. The AI does about 75% of that, so we can skip the 0.5-baud C-over-bongos thing.