7 ms·
Cool stuff. The readme is pretty lengthy so it was a little hard to identify what is the core problem this tool is aiming to solve and how is it tackling it dif
by iddan 10mo ago
Cool stuff. The readme is pretty lengthy so it was a little hard to identify what is the core problem this tool is aiming to solve and how is it tackling it differently than the present solutions.
- mimischi 10mo agoA classic issue of AI generated READMEs. Never to the point, always repetitive and verbose
- kieckerjan 10mo agoAnd full of marketing hyperbole. When I have an AI produce a README I always have to ask it to tone it down and keep it factual.
- SwellJoe 10mo agoI'm not saying it is or isn't written by an LLM, but, Yegge writes a lot and usually well. It somehow seems unlikely he'd outsource the front page to AI, even if he's a regular user of AI for coding and code docs.
- cube2222 10mo agoFunnily, AI already knows what stereotypical AI sounds like, so when I tell Claude to write a README but "make it not sounds like AI, no buzzwords, to the point, no repetition, but also don't overdo it, keep it natural" it does a very decent job. Actually drastically improves any kind of writing by AI, even if just for my own consumption.
- zaphirplane 10mo agoThis looks like a ticketing cli
- simonw 10mo agoThat's exactly what this is, but it's one that's designed with coding agents in mind as its principle users.
- vdm 10mo agohttps://steve-yegge.medium.com/beads-best-practices-2db636b9760c https://steve-yegge.medium.com/beads-best-practices-2db636b9...