The amount of time an LLM saves is negated by fussing over which service provider and model to use, what to put in your agents.md file, setting it all up, maintaining it, and then arguing with its output since after all that trouble, the damn thing is still wrong 10% of the time. And then you’ve made yourself dependent on a service that is going to explode in price when the AI bubble pops.
It’s a tool whose pros are more flashy and prominent than its cons.
For the most part I’m just focusing on learning and making myself a better programmer. I’d rather do that by going to the source (forum and blog posts, tutorials, Stack Overflow, and documentation) rather than have that information mixed in a blender and removed of its context and nuance by a bot that always gives an answer even when it can’t find anything useful.
looking back at that reverse engineering attempt, I think the reason I turned to trying to use AI was largely because there was next to no information about reverse engineering windows drivers (specifically pcie device drivers) that was remotely easy to follow (the closea I remember finding involved using qemu with an option that isn’t built into it by default to I think buffer all dma accesses through a file).
they seem fairly useful for highly copyright ignoring reverse engineering, mostly because they have some understanding of most of the windows functions the driver I’m trying to dissect is using.
The amount of time an LLM saves is negated by fussing over which service provider and model to use, what to put in your agents.md file, setting it all up, maintaining it, and then arguing with its output since after all that trouble, the damn thing is still wrong 10% of the time. And then you’ve made yourself dependent on a service that is going to explode in price when the AI bubble pops.
It’s a tool whose pros are more flashy and prominent than its cons.
For the most part I’m just focusing on learning and making myself a better programmer. I’d rather do that by going to the source (forum and blog posts, tutorials, Stack Overflow, and documentation) rather than have that information mixed in a blender and removed of its context and nuance by a bot that always gives an answer even when it can’t find anything useful.
looking back at that reverse engineering attempt, I think the reason I turned to trying to use AI was largely because there was next to no information about reverse engineering windows drivers (specifically pcie device drivers) that was remotely easy to follow (the closea I remember finding involved using qemu with an option that isn’t built into it by default to I think buffer all dma accesses through a file).
they seem fairly useful for highly copyright ignoring reverse engineering, mostly because they have some understanding of most of the windows functions the driver I’m trying to dissect is using.