Few cars are manual steering, manual brakes, manual transmission.
Few grappling bodies go all Greek-naked.
Few chess bodies forbid researching previous games or your opponent.
The list is indeed endless, and every single person thinks they are using just the right amount of assistance; anything less is pointlessly difficult, anything more is cheating that takes the sport out.
Me, I've been a hobbyist programmer since youth (6502 assembly, represent). I'm having a blast "writing" software without touching a line of code. Sure, I'm old, and maybe I'm like those guys blasting Veyrons through highways, relying on traction control and all the computers to let me drive beyond my abilities. And... ok? I'm having fun, even if I'm not doing it right, by random anonymous peoples' views.
And that’s totally fine, enjoy your hobby however you enjoy it best. Most people programming by hand for fun don’t care that you program with an LLM for fun. The problems come when those two worlds collide, like in the linked GitHub issue, in chess engine leaderboards. In the long run for both groups to have their fun and friendly competition you’ll need two separate leaderboards. This is also very common in other hobbies. In racing there are car classes so that your Veyron and someone’s old Miata don’t go head to head. In combat sports there’s weight classes. Most sports separate amateurs and pros. Usually there is respect across the group boundaries and appreciation for the other groups deeply specialized skill. There’s even the concept of cross training to get better in your flavor of a sport. This will be figured out with programming as well.
But I think you’re on to something important: framing programming as a competition of intrinsic skill where rules are necessary to equalize. That’s certainly true in some cases, and more power to those who enjoy it.
I guess I’m just more of a product guy these days, where the equalizer is the market and the consumers rather than the implementation methodology.
Not that it’s about me, but I was doing programming competitions 25 years ago, half of which were on paper with no keyboard allowed.
Not everyone has to agree. Just everyone in a particular group at a particular time. Grappling competitions exist and so do MMA competitions, and both of them will expect you to follow their own rules.
I don't think there is insignificant group who would say that using LLM to write a book does not make you an author. Or make a song musician. Or draw a picture a painter or artist.
This just somewhat baffles me... Or maybe the LLM for programming people all believe that you are as much artist if you use AI in those fields and the product generates as such is as if not more valuable than one by more traditional means.
My retort is usually a variation of one I've already posted in this thread: they do that to the same extent that taxis enable everyone to drive, which is something most people will intuitively understand as nonsense, even if they've given clear instructions to the driver and even though they've arrived at the intended destination. If you aren't driving, you aren't driving. If anything, the taxi service enables more people not to drive.
A programmer that has climbed up the ladder in their field, on the other hand, often stopped coding themselves. Instead, they manage others who code, or provide vision/direction on the project.
I think it really depends on what people on the senior level of your field do. If they mostly move to managerial roles, then it's much more likely they'd embrace LLM.
Ironically I observe this in academia too. Professors (who often stopped doing hands-on research, but only provide guidance to postdocs and grad students in their research) tend to embrace LLM more than the fields you mentioned.
Only difference is I’m prompting LLMs rather than engineering teams. But honestly it’s not all that different, except that in the hobby flavor I can write specs that would take tens or hundreds of engineers to implement.
Maybe it all comes down to semantics: does “programming” mean typing in code, designing app architecture, or producing software? When I was young I was probably 75 / 5 / 20 between those. Now I’m 5 / 20 / 75. Maybe it merits a different word?
Not to diminish your enjoyment, you’re completely entitled to it, I just think this is a bit of a false equivalence
Sometimes I'm having fun getting to the output I want and otherwise wouldn't have had time to. Sometimes I'm having fun exploring the code.
I don't care if someone don't see the value in one or the other of those, and to me they stand on equal footing as things I find both fun and valuable for different reasons.
Tell me you are not in European or African continent without telling me.