trezm

This is what I want too.

I was a loyal railway customer for a while, but this response smacks of "we didn't want people to know" instead of "we wanted to take responsibility."

The options railway has given us are "rotate your keys and bring down your service" or "keep your service up and let the exposed keys remain at risk." Kind of a crap position, no? Mistakes are going to happen, but when the suggested mitigations are to stab yourself in the leg or stab yourself in the ass, it's hard to be sympathetic.

I have to imagine quite a few users are asking their agents to port their stacks over to alternate providers like I am. The cost of switching has never been cheaper thanks to AI.

I'm shocked this isn't getting higher up on the homepage. It's pretty significant at this point with no end in sight.

I'm trying to find details on this, any links?

Yes, totally. This is how I work as well! Frankly, it seems like LLMs are pretty good if you tell them after the fact to divide work like this too, "make stacked prs with model a, then model b, then service c" has done wonders for my mental health.

I can smell the screenshots -- that's how accurate the portrayal is. Well done.

Thanks! I was surprised at how well the open source models compare to the "professional" tools as well. I recently had a meeting where someone used another closed source solution and the result was emailed to me -- I preferred Lorraine's copy by a long shot!

I think those are valid points, and to further add to it, we'll see a bifurcation of what are currently called "software engineers"; those who adopt the technology because they consider it a craft, and those who fall behind by producing slop because they're just trying to leave for the day.