News for hackers. Stuff that matters.
Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by bodge5000 on Saturday January 31, 2026 @10:17AM (#46837378)
> No more AI thought pieces until you tell us what you build!

Absolutely agree with this, the ratio of talk to output is insane, especially when the talk is all about how much better output is. So far the only example I've seen is Claude Code which is mired in its own technical problems and is literally built by an AI company.

> Write your own code without assistance on whatever interval makes sense to you, otherwise you'll atrophy those muscles

This is the one thing that concerns me, for the same reason as "AI writes the code, humans review it" does. The fact of the matter is, most people will get lazy and complacent pretty quickly, and the depth of which they review the code/ the frequency they "go it alone" will get less and less until eventually it just stops happening. We all (most of us anyway) do it, its just part of being human, for the same reason that thousands of people start going to the gym in January and stop by March.

Arguably, AI coding was at its best when it was pretty bad, because you HAD to review it frequently and there were immediate incentives to just take the keyboard and do it yourself sometimes. Now, we still have some serious faults, they're just not as immediate, which will lead to complacency for a lot of people.

Maybe one day AI will be able to reliably write the 100% of the code without review. The worry is that we stop paying attention first, which all in all looks quite likely

Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by Kerrick on Saturday January 31, 2026 @12:08PM (#46838454)
> Absolutely agree with this, the ratio of talk to output is insane, especially when the talk is all about how much better output is.

Those of us building are having so much fun we aren't slowing down to write think pieces.

I don't mean this flippantly. I'm a blogger. I love writing! But since a brief post on December 22 I haven't blogged because I have been too busy implementing incredible amounts of software with AI.

Since you'll want receipts, here they are:

- https://git.sr.ht/~kerrick/ratatui_ruby/tree/trunk/item/READ...

- https://git.sr.ht/~kerrick/rooibos/tree/trunk/item/README.rd...

- https://git.sr.ht/~kerrick/tokra/tree

Between Christmas and New Year's Day I was on vacation, so I had plenty of time. Since then, it's only been nights & weekends (and some early mornings and lunch breaks).

Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by yojat661 on Saturday January 31, 2026 @07:01PM (#46842184)
Are these software popular? Are these maintainable long term? Are you getting feedback from users?
Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by Kerrick on Sunday February 01, 2026 @06:45PM (#46850592)
RatatuiRuby is pretty new still: its beta launch was Jan 20. Octobox's TUI is built on it [0], and Sidekiq is using it to build theirs [1].

I believe they'll be maintainable long-term, as they've got extensive tests and documentation, and I built a theory of the program [2] on the Ruby side of it as I reviewed and guided the agent's work.

I am getting feedback from users, the largest of which drove the creation of (and iteration upon) Rooibos. As a rendering library, RatatuiRuby doesn't do much to guide the design or architecture of an application. Rooibos is an MVU/TEA framework [3] to do exactly that.

Tokra is basically a tech demo at this stage, [4] so (hopefully) no users yet.

[0]: https://ruby.social/@[email protected]/1159351822843...

[1]: https://ruby.social/@getajobmike/115940044592981164

[2]: https://www.sciencedirect.com/science/article/abs/pii/016560...

[3]: https://guide.elm-lang.org/architecture/

[4]: https://ruby.social/@kerrick/115983502510721565

Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by yojat661 on Sunday February 08, 2026 @06:22PM (#46939655)
Appreciate the response. My primary concern with llm coding is long term maintainability. The paper you linked seems interesting, will give it a read!
Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by g8oz on Saturday January 31, 2026 @11:03AM (#46837808)
But simonw said that dark factories are the way forward /s
Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by malfist on Saturday January 31, 2026 @02:11PM (#46839731)
Lights out manufacturing is always the boogieman that's being built or coming tomorrow. Never seems to happen though. The Wikipedia article for it only cites two such factories, and at least one of them requires humans still and isn't fully lights out.
Re:A Step Behind the Bleeding Edge: A Philosophy on AI in Dev by kranner on Saturday January 31, 2026 @09:01PM (#46842928)
It's a reference to this article about entirely automated software production (eventually and hypothetical): https://news.ycombinator.com/item?id=46739117