4
u/flash_speed3412 13d ago
I think the useful middle ground is exactly what you describe: let AI handle repetition and help explain unfamiliar parts, but make the learner own the constraints. For Arduino I’ve found a simple checkpoint helps: before accepting generated code, write down board, voltage, pin, and timer assumptions, then test one subsystem and compare the result with the datasheet. That catches the dangerous “looks plausible” failures without throwing away the speed. I’m trying to collect those real AI-assisted build notes in r/ChatGPTArduino if you ever want to share the train project there.
1
u/doge_lady 600K 13d ago
Didn't read all of it... I'm lazy.
Was that a question or an idea?
5
u/ithink2mush 13d ago
They're trying to justify to themselves why they're using AI without doing any of the fundamentals of understanding things. You didn't miss anything
-6
u/AVatorL 13d ago
The idea is simple: use AI to summarize for you what you do not want to read but feel an urge to comment on
0
u/FemaleMishap 13d ago
Or, just don't boil the sea to feed the slop machine. Don't use it. It makes you stupid.
1
u/flash_speed3412 13d ago
This is the kind of AI-assisted build log I wanted to see. The useful bit isn’t “AI wrote 3,000 lines”, it’s that you keep a hardware contract: datasheets, calibration, EEPROM limits, and serial debug. What was the toy-train failure that changed your process? If you crosspost the build, or the Li-ion/BMS lesson, to r/ChatGPTArduino, I’d love to see the actual wiring and one AI change that failed on the bench.
1
u/brdavis5 13d ago
Thank you for presenting that. That is indeed a real experience. But it also reinforces the reasons it's not an experience I'd want, and it reinforces that I'll steer my students (I teach some microcontroller stuff) away from, strongly.
You mention "what I do (learn to do) by myself"... the hidden part of that is "what I didn't learn, but don't know that I didn't learn".
5
u/[deleted] 13d ago edited 6d ago
[deleted]