> We're supposed to be engineers. Criticising a concept based on conjecture and insult is unbecoming of our culture.
The entire thing is nothing but conjecture. No real software has been produced by the concept to date, except more garbage software that takes hundreds of thousands of lines where a few thousand would do.
And to be clear, Beads and Gastown are unbecoming of our “culture” and any self respecting engineer would recoil in horror at the concept.
How is it conjecture when you just admitted you're aware of a repo with hundreds of thousands of lines of code.
Your argument belies a lazyness or skill issue. You abandon the possibility of proof to sling mud.
People have made a shit ton of economic value with shit code over the course of history of software and now that's accelerating with this sort of shite. I appreciate its ugly but i will not follow you by fashioning a duvet out of arrogance and throwing rocks people investigating the ugly.
What they're doing it at least an interesting spectacle and ill wait for the show to end before writing my review.
There are some good ideas in the tools. I hope our culture has room left for curiosity and exploration in that way. I also highly doubt these will catch on over one-shotting and Jira though. Here’s one quick thought from each:
Beads keeps the issue tracker state in git. This can only work if you don’t have a PR/Review-Gate to submitting patches (to file bugs/issues/etc) but I’ve found it unexpectedly helpful for personal projects. Helpful enough to entertain the idea in other contexts.
Gastown uses an AI Agent _as the orchestrator_, and to kick stalled agents, and, that’s such an obvious thing in hindsight I can’t believe I hadn’t thought of it. I have adopted this in a few other contexts now.