Re:AI Makes Tech Debt More Expensive
by MarcelOlsz on Thursday November 14, 2024 @03:50PM
(#42141069)
Try using Cursor with the latest claude-3-5-sonnet-20241022.
Re:AI Makes Tech Debt More Expensive
by PaulHoule on Thursday November 14, 2024 @04:00PM
(#42141154)
Unfortunately I “think different” and use Windows. I use Microsoft Copilot and would say it is qualitatively similar to codeium in quality, a real quantitative eval would be a lot of work.
Re:AI Makes Tech Debt More Expensive
by MarcelOlsz on Thursday November 14, 2024 @04:01PM
(#42141165)
Cursor (cursor.com) is just a vscode wrapper, should work fine with Windows. If you're already in the AI coding space I seriously urge you to at least give it a go.
Re:AI Makes Tech Debt More Expensive
by PaulHoule on Thursday November 14, 2024 @04:23PM
(#42141385)
I'll look into it.
I'll add that my experience with the Codium plugin for IntelliJ is night and day different from the Windsurf editor from Codium.
The first one "just doesn't work" and struggles to see files that are in my project, the second basically works.
Re:AI Makes Tech Debt More Expensive
by MarcelOlsz on Thursday November 14, 2024 @04:27PM
(#42141405)
You can also look into https://www.greptile.com/ to ask codebase questions. There's so many AI coding tools out there now. I've heard good things about https://codebuddy.ca/ as well (for IntelliJ) and https://www.continue.dev/ (also for IntelliJ).
>The first one "just doesn't work"
Haha. You're on a roll.
Re:AI Makes Tech Debt More Expensive
by lubujackson on Friday November 15, 2024 @11:24AM
(#42148341)
Seconding Cursor. I have a friend who used Copilot 6 mo. ago and found it vaguely helpful... but turned him on to Cursor and it's a whole new ballgame.
Cross between actually useful autocomplete, personalized StackOverflow and error diagnosis (just paste and error message in chat). I know I am just scratching the usefulness and I pretty much never do changes across multiple files, but I definitely see firm net positives at this point.
It also screwed up the imports of my tests pretty bad, some imports that worked before got changed for no good reason. It replaced the JetBrains NotNull annotation with a totally different annotation.
It was able to figure out how to update a DAO object when I added a new field. It got the type of the field wrong when updating the object corresponding to a row in that database column even though it wrote the liquibase migration and should have known the type —- we had chatted plenty about that migration.
It got many things right but I had to fix a lot of mistakes. It is not clear that it really saves time.