rowanseymour

Very impressive. Love the motion blur on stars as you move around and fascinating to toggle on asteroids to see how busy our solar system really is.

I might try this but I've gotten so accustomed to talking to agents as I would a human - I worry that if I get accustomed to speaking coldly and directly to agents I'll find myself talking like that to people.

I think that's something that has changed in the last 6 months. It used to be standard practice to let Claude scan everything once and describe your repo in the CLAUDE.md - the logic being you don't want to do that every time for every prompt. But now I think the tooling has gotten so good at just grepping around your repos, and maintaining memory from previous sessions, that the best practice is only use CLAUDE.md for things that aren't obvious from the code.

Right now I feel like I'm getting so much value out of working daily with Fable, but I'd be embarrassed to share my sessions because they're pretty much how I would talk to a colleague. Spelling mistakes and half-baked thoughts included. Gone are the formal sounding prompts and specs I was proudly writing 6 months ago. But it's getting the results.

To be clear I don't want to detract from what you've made here. Agentic engineering done right does still require a lot time and attention IMO. But you've still got a challenge on your hands to demonstrate to potential adopters that you're in it for the long haul.

I think a challenge for a vibe coded library to gain adoption is if there is a lack of human time investment in its creation, how do we know there will be investment in its maintenance?

I know plenty of women who have delayed starting a family and they were well aware of the increased risks.. as they struggled to meet the right person, establish themselves professionally etc. They were certainly not brainwashed.

Maybe but those people are also having claude summarize their inbox and get nice little daily reports on things they might want to look into.

We even find ourselves creating PRs in situations where the code is going to be merged immediately anyway, and tagging other devs, just so they have a convenient way to see what got merged and why. So people don't lose track of what is in the codebase.

I'm back in the UK for a bit and one of the first things I notice besides the infuriating and pointless "Accept Cookies" popups on every webpage is that I can't view half the news about Palestine on Twitter/X without handing over a government ID to prove I'm an adult. No thanks. Please let's find a way to protect children without giving up the right to anonymity on the internet.

To be clear I meant it's good to be small team on the assumption that we're all using AI... I honestly can't imagine not using AI in May 2026.

Now feels like a very good time to be a small team of experienced developers who can largely work on stuff by themselves and not a corporation of hundreds of developers of varying abilities all now trying to show how much code they can generate and how many tokens they can burn.

I think one problem is that a lot of sleep doctors are essentially CPAP salespeople and they will just keep pushing that even if you protest that you don't feel any better. I got better answers from an ENT doc who did a Drug-Induced Sleep Endoscopy and told me mechanically why I was not breathing well at night.

IMO if you've got a use case that requires querying in so many ways that you need several indexes, then DynamoDB is probably the wrong choice. It excels at stuff like user specific histories that are well partitioned, read back in one way, and ideally can be written asynchronously by a separate writer process.