bochoh

I've been using cursor lately to handle some (most) of the grunt work and it's been surprisingly useful for two things: keeping documentation from going stale and spotting gaps in test coverage. For example, I'll ask it things like "what's the most likely way this function could break?" and it will suggest edge cases I hadn't thought of.

That said, it's not (maybe?) magic and sometimes hallucinates test cases that are rubbish so some critical thinking is still required.

I'm curious what y'all are using to keep docs/tests maintainable? Are you leaning on AI or doing it the old fashioned way?

Follow-up a few years after https://news.ycombinator.com/item?id=25584421

Are you tempted by M2 / M3? I'm still happily plugging away on a base m1 mini (8/256) and don't feel like I've noticed any degradation here 3 years later.