Yep, that's why I put it in quotes. As a software engineer of 10+ years (professionally, on a personal level, 20+ years now), I can understand code even if I am unfamiliar with the language and the frameworks in question. I know what needs doing (not just random "do this feature, make no mistakes" bs prompting), I know roughly how it can be done, and I let the LLM fill in the gaps.

Plus I also work with a fleet of agents and a collection of skills to ensure its not crap being written. Multiple agents work with specific roles (say, embedded development expert, PlatformIO expert, and so on), there's a continuous verify-repair-improve loop, strict code quality guidelines and non-LLM checks in place. Of course it's not perfect, but it gets things 99% of the way, and at the end I just need to review and confirm things.

For example one of the things I maintain is a private fork of CrossPoint reader, into which I've integrated BookOrbit, not just as a plugin that awkwardly allows retrieval of your books, but as an actual on-device library that downloads the right EPUBs and syncs not just reading progress but statistics (words per minute, page size and turns, reading time, etc.) as well. The library itself functions similar to a Kindle - all books are listed and with a tap you can download them. LLMs take care of rebasing my changes, with proper reporting on what's going on and why and how, how the rebase went, what upstream has fixed so I can drop the local version and so on. LLMs take care of API changes to be updated for, optimisations, the list goes on - but before any change is executed, I go in and get an understanding of what really changes.