That's a small number of data center impacted and won't explain the 5x increase.

If it happened to "them" it could happen to us. You never know when the next war will be.

Yeah, but the risks are massive. Amazon wrote off its Dubai data center, it's a complete loss.

This is a catastrophic event that you can't mitigate except with cold storage offline.

It's a total loss only for people that were too cheap to pay for multi-regional data storage. Most people balk at monthly S3 fees, so willingly paying double the cost is a non-starter for those led by the bean counters. Disaster recovery is a known thing that should not be blamed on the loss of a single data center in a stupid war. AWS even has automation of duplicating selected data to another region.

Only a loss if you didn't have cross region backup

Then that's an issue with the indexes isn't it.

Yeah, kind of eye raising if people are still using Cursor now days.

Honestly depending on what you're doing, consider Gemini + Claud combo. Use Opus/Fable for design/architecture/complex work and have Gemini Flash 3.8 do the code gen and the rest of the simple stuff.

Yeah, I've tried this as well, but via Antigravity - it was very effective. I wish to have some smart router that monitors the trends of your usage and has skills-based routing to the best model for the job.

By usage trend I mean something considering Codex almost predictable resets, your usage, and maybe even plan ahead using your backlog to know what you will need sooner.

For example, if you want to ship a lot of UI/UX this week, save Claude for it, and use other models to do the coding.

In fact, I completely revamped the way I do testing and even GitHub Actions, because I started to get hit with a lot of GitHub Actions costs. So, what I did was a smart test actions, which verify if the code has test attestations for local runs, so, they just skip burning GitHub Actions redundantly - the code has already been tested successfully locally.

Another huge burn from Actions came from squashed PRs - my attestations didn't work as the commit hash changes, so, I needed to put that into consideration as well.

In general, I'm completely revamping my release cycle, not allowing PRs to age, and main no longer represents Production. Agents keep merging as soon as possible and then another process assesses if there's a good enough release candidate having enough features that pass more extensive tests. There's no point to always test and always fix piece by piece if you're not going to release.

So, the RC candidate also generate a changelog, blog posts with the features, and so on.

It's amazing how many things fail due to bad thermal design.

SendCutSend has CNC machining but the costs are no where comparable. And they don't have metal 3D printing available either. Surr you can laser cutter some things out of metal, but that's not really comparable to 3D parts.

That's for FDM. This is resin.

>This just seems like it's aimed at SLA novices

That's exactly it. That's why the entire influencer campaign exist and almost every influencer is saying the same thing.

Resin is generally very stiff but also very brittle. They are not as tough as composites (depending on resin used).

What do you use? I assume you're using ChatGPT or similar instead?

Claude opus 5.5 medium in incognito mode