this is a good approach that I have admittedly not thought of.
At that point however, is it really saving you that much time over good snippets and quick macros in your editor?
For me writing the code is the easiest part of my job, I can write fast, and I have my vim configured in such a way where it makes writing code even faster.
>is it really saving you that much time over good snippets and quick macros in your editor?
I had someone say that to me ~a month ago. I had mentioned online that one of the things I had the AI tooling do that morning was to convert a bunch of "print" statements to logging statements. He said that was something he'd just have his editor find/replace do. I asked him what sort of find/replace he'd do that based on the content of the log message appropriately selected between "logging.debug", "info", "warning", and "error", because the LLM did a good job of that. It also didn't fall into the issues of "pprint()" turning into "plogging.debug()" and the like.
At that point however, is it really saving you that much time over good snippets and quick macros in your editor?
For me writing the code is the easiest part of my job, I can write fast, and I have my vim configured in such a way where it makes writing code even faster.