tra3

I do this exact workflow with random internet recipes and ChatGPT or Claude pretty frequently. In fact modifying a recipe on the fly has been pretty handy.

The base recipes are still vetted by the staff right?

That sounds like a lot. Is the rust process serving parallel requests?

I know that latest rails suggests SQLite as one of the production options. I don’t get how it’d work with concurrent access though. Time to look into it.

With respect, that's a wall of text.

Seems unnecessarily harsh. LLMs are a power tool. I'm not on-board with how it's being used in a lot of places, once things shake out I believe it's going to be net positive.

Microwave meals vs Michelin star chefs? Lots of people work in the restaurant industry but it’s notoriously difficult.

What’s too old?

I'm very much against this. I love agentic coding, because I get where I'm going much faster, but I retain at least a high level understanding of architecture and trade offs that have been made. But that's in my personal projects. For work, there's a huge push to deliver much faster. The quality is an afterthought.

> Now, if you have an idea, then go use AI to prototype, to validate, to iterate.

That's another huge gap. Folks without software background cannot seem to grasp incremental improvement. This is why we're on v5. The solution to product's shortcomings is to start a brand new project.

I'm waiting to see if people start dropping massive trees on their houses, or if we're all arborists now.

> But the idea that everyone needs give up hand coding is absurd.

Unfortunately (?) this seems to be the ground truth for the majority of people I speak to. What's not clear to me yet, is whether we'll stop reading code. I suspect that reading is going away as well. There's a push at $WORK to expedite 50-files/20,000 line PRs via agentic reviews..

If this continues, then language readability and "pleasure" of hand coding will likely diminish. I'm still not clear where we're going to land with libraries and re-use. Non-technical pressures are forcing functionality to be re-vibe coded instead.

I've always loved Rails for its pragmatic approach; I've delivered many projects with it. I'll be sad when it disappears but it seems inevitable.

I think of an emulator as a separate project/product typically. Perhaps that's what they are saying?

Fascinating! Thank you for the links.

Never been, but the titular burning man installation comes to mind.