|
> that means nothing We currently have a tracking code that is deprecated, and stopping it from going out is a one line removal in a switch statement. I have a ticket for it, it’s 1 point, easy. I’d wager a guess that if I told an LLM “we don’t want the ‘worker-item-click-apply’ event to fire”, I’m going to get a mix of code edits, maybe a new module, and probably a filter at the API call level, because it’s going to be too clever. > What happens when you have to write a new feature and it will take hundreds of lines of code? Unless you're an elder god of programming, the LLM will lap you easily. Then I’m going to write hundreds of lines, I’m going to write tests, I’m going to painstakingly compare my work to Figma, and I’m going to do it a lot slower than an LLM. I’m also going to understand the code, inside and out, and when our new engineer hops in to help add a feature or fix a bug, I’ll know where to send them, I’ll be able to explain the code to them, and we will both grow a better understanding of our codebase. Could an LLM do that, or help? Sure, and I know that it will take a lot of effort and refinement that is just going to be churn. |