my claude code often gets stuck when it runs dev server or similar and then for some reason just waits forever on it. is there a way to teach it to never get stuck
i should say βsing in with your AT handleβ is easily my second favorite.
sounds exactly like @ handle, but clear tie to AT and visually different
doesnβt require so much arguing, capitalizes on AT wordplay
but it needs to link to normie explainer etc
in case you missed it: yesterday i wrote about a new open source tool i made, called RSC Explorer.
it lets you interactively step through how the React Server Components protocol works directly in the browser β no server needed.
RE:
also it is so much EASIER to make comprehensive tests now if you know what youβre doing.
in my three vibecoded projects i made the kind of tests iβd never bother to do before. and they saved my ass many times
you do need to steer it to test the right things which requires some experience and taste
RE:
