think having claude know, use, and suggest approaches like this when fixing problems would make vibecoding a lot more compelling. i’m sure it can get there with a bunch of prompting but this needs to be knowledge available to it out of the RE: View quoted note β†’
i wrote about how to fix any bug [How to Fix Any Bug β€” overreact...]( )
trying to teach claude to root cause bugs by removing things
this is the way to learn with ai. you can start anywhere and backfill. you have to remain curious and careful and not just passively eat up plausible explanations. but if you put in the effort and the model is good, it’s powerful RE:
this looks like it'll be a banger release [nextjs.org/blog/next-16...]( ) [Next.js 16 (beta)]( )
at the crossroads: currently i have a fully client-side SPA written with React Router 6. i like that i can deploy it for free anywhere however i do want stuff like OG images, ideally SSR for SEO, and i'd like low-latency access to data layer feeling tempted to port to Next
kind of interesting that it's not hard to add some realtime behaviors to atproto apps just by listening to jetstream from the client. no server needed
my β€œFor You” feed has gotten really good
alas no the bug is still there. i also have no idea where it is coming from. really annoying RE: View quoted note β†’
man idk vibecoding is such a rollercoaster. yesterday: - it recreated most of my project from scratch with a proper architecture, in a way that allowed proper testing and pretty much fixed all business logic bugs (yay) - but then when i asked it to reskin it to old ui, it introduced so many bugs