> So, it was really fascinating that I had the menu gem basically demo working on my laptop in a few hours, and then it took me a week because I was trying to make it do it
Reminds me of work where I spend more time figuring out how to run repos than actually modifying code. A lot of my work is focused on figuring out the development environment and deployment process - all with very locked down permissions.
I do think LLMs are likely to change industry considerably, as LLM-guided rewrites are sometimes easier than adding a new feature or fixing a bug - especially if the rewrite is something into more LLM-friendly (i.e., a popular framework). Each rewrite makes the code further Claude-codeable or Cursor-codeable; ready to iterate even faster.
andai
The last 10% always takes 1000% of the time...
afiodorovOP
I am not saying rewrites are always warranted, but I think LLMs change the cost-benefit balance considerably.
steveklabnik
I am with you on this. I'm very much not sure about rewrites, but LLMs do change the cost-benefit balance of refactorings considerably, for me. Both in a "they let me make a more informed decision about proceeding with the refactoring" and "they are faster at doing it than I am".
Aeolun
Jup. Claude develops the first 90% without a sweat, and then starts flailing.
Reminds me of work where I spend more time figuring out how to run repos than actually modifying code. A lot of my work is focused on figuring out the development environment and deployment process - all with very locked down permissions.
I do think LLMs are likely to change industry considerably, as LLM-guided rewrites are sometimes easier than adding a new feature or fixing a bug - especially if the rewrite is something into more LLM-friendly (i.e., a popular framework). Each rewrite makes the code further Claude-codeable or Cursor-codeable; ready to iterate even faster.