This is interesting but in my experience an avoidable issue if you force the LLM to write extensive E2E tests before writing any code. I also force mine to run performance benchmarks against any new commit before it’s committed.
I have backend bugs that I need to manage myself, usually from unknown-unknowns that I don’t think I can easily avoid, but I never have frontend bugs (since Opus 4.6 anyway).
And if you force the LLM to write extensive E2E tests and performance benchmarks before writing any Svelte code, you're even better off.
In the "Unix Haters Handbook", "X-Windows Disaster" chapter, "Ice Cube: The Lethal Weapon" section, I quoted Jamie Zawinski, whose timeless and tactile observation also applies to React:
> Using these toolkits is like trying to make a bookshelf out of mashed potatoes.
blakeashleyjr · · focus · HN ↗
I've had to work on a Next.js for work and much prefer Sveltekit. Excited to try this release!
383toast · · focus · HN ↗
Recursing · · focus · HN ↗
smt88 · · focus · HN ↗
I have backend bugs that I need to manage myself, usually from unknown-unknowns that I don’t think I can easily avoid, but I never have frontend bugs (since Opus 4.6 anyway).
DonHopkins · · focus · HN ↗
In the "Unix Haters Handbook", "X-Windows Disaster" chapter, "Ice Cube: The Lethal Weapon" section, I quoted Jamie Zawinski, whose timeless and tactile observation also applies to React:
> Using these toolkits is like trying to make a bookshelf out of mashed potatoes.
<a href="https://news.ycombinator.com/item?id=35631889">https://news.ycombinator.com/item?id=35631889
<a href="https://donhopkins.medium.com/the-x-windows-disaster-128d398ebd47#3f73" rel="nofollow">https://donhopkins.medium.com/the-x-windows-disaster-128d398...
<a href="https://www.youtube.com/watch?v=mg8xfl4L6HQ" rel="nofollow">https://www.youtube.com/watch?v=mg8xfl4L6HQ
justin66 · · focus · HN ↗