Comment Re:Thinking vs drudge work (Score 1) 72
anecdotical:
I'm a Ham and I wanted to CAT control multiple radios and a couple serial port devices. I currently do this with multiple USB serial ports which is a pain because if you ever move them you'll get a different enumeration and have to reconfigure everything.
I asked an LLM to create a project for a multiport card with hardcoded serial numbers and configurable settings (speed, parity, polarity etc - even inter-byte delays).
It did everything as I requested. The only issue I had is that when I bootstraped the project i selected a different microcontroller target. But the result is now a serial port that 1) works exactly as intended, 2) has serial numbers which allows me to move it around ports without reconfiguring (Linux by-id path), 3) whatever quirks i can either fix or add as workarounds for badly behaving devices. 4) Is not a chinese clone that will refuse to work on windows because the official drivers detect it as counterfeit.
The experience was honestly just fantastic. I do NOT want to write code for a multiport serial card. It's completely boring drudge. There is nothing fun in it. There is just hundreds of #define and compiler guards for everything. This thing had a working solution in 10 minutes, of something that would probably take me an entire weekend to do myself - a weekend of, you know, not actually using my radios because I was too busy writing code. I was able to do what I really wanted (focus on the high level requirements and then actually use the product) instead of digging deep into a datasheet developing a skill I'll never use in my work (I don't do embedded code for work).