Yes but the goal of school is to lift heavy things, basically. You're trying to do things that are difficult (for you) but don't produce anything useful for anyone else. That's how you gain the ability to do useful things.
I wouldn't want to write raw bytes like Mel did though. Eventually some things are not worth getting good at.
When I stand still for hours at a time, I end up with aching knees, even though I'd have no problem walking for that same amount of time. Do you experience anything like that?
Forklift operators don't lift things in their training. Even CS students start with pretty high level of abstraction, very few start from x86 asm instructions.
We need to make them implement ALU's on logical gates and wires if we want them to lift heavy things.
Though I also wonder what advanced CS classes should look like. If they agent can code nearly anything, what project would challenge student+agent and teach the student how to accomplish CS fundamentals with modern tools.
As an added bonus, being able to discuss your code with another engineer that wasn't involved in writing it is an important skill that might not otherwise be trained in college.
> We need to make them implement ALU's on logical gates and wires
Things must have certainly changed since I was a CS student :-/ We did an assembler course in second year, and implemented a basic adder in circuitry in a different course.
This was in the mid-90s, when there was definitely little need for assembly programmers outside of EE (I was CS).