When planning small-to-medium sized changes, I found that it was a little bit faster than GPT-5.5 (high) and produced equivalent results. on large changes its results were fine but GPT's were more thoroughly thought through. DS v4 beats the absolute pants off GPT when it comes tone and style though.

... bingo!

Might add support for custom WASM plugins down the road, but everything shipped with the system will be Rust.

I'm all in favour of using AI for development, even for letting AI build the whole thing. Be lazy about it though and it will come back to bite you.

A concurrency framework seems like the wrong thing to be lazy about.

After seeing this post I checked my recent photos. I'm using a Pixel 6 Pro with the most recent android release and the stock camera app. None of my recent photos have location in the EXIF, even locally, and there's no option to turn it on.

It's particularly galling that the Camera app still wants location permissions and if you view a photo in the Google Photos app, the location is still there. Google can have those exact locations, but no one, not even the user, can.

It's abusive as hell.

presumably you'd be wrapping up the offsite on a Friday, so people would fly back that morning or Saturday morning. if they fly back Friday then they lose a day of offsite time, if they fly back Saturday then they lose their weekend to travel and recovery.

if a large % of your team is within 5-8 flight hours and it's only a handful of people coming from further away, then I'd spring for an extra night or two at the hotel/airbnb for the people with extra long flights.

cost and activities are hard to gauge without knowing team size. smaller teams can usually share a large airbnb which helps a lot with cost. larger teams means hotels and the cost balloons.

similar story for activities. larger teams limits your options and makes pleasing everyone hard. I'd recommend booking one or two "all-hands" activities, like dinner at a fancy restaurant, and researching some "this is a thing if anyone is interested" ahead of time. with a large team, make arrangements if enough people opt-in, or for smaller teams make it easy for people to go off and do that on their own. I've had good success with booking a few all hands activities and setting up a shared space where people can hang out together. smaller activities tend to naturally grow out of those interactions.

legitimate messages or not, this will look like spam if you get a surprise burst of traffic. and providers will nuke your SIM, maybe blacklist your phone's IMEI, if they suspect you're using it for spam.

also is it weird that "That's its whole life now." made feel a bit sorry for the phone? might be spending too much time in opencode...

the things they "didn't realize" or "didn't know" are basics. they're things you would know if you spent any time at all with terraform or AWS.

all the remediations are table stakes. things you should at least know about before using terraform. things you would learn by skimming the docs (or at least asking Claude about best practices).

even ignoring the technical aspects, a tiny amount of consideration at any point in that process would have made it clear to any competent person that they should stop and question their assumptions.

I mean, shit happens. good engineers take down prod all the time. but damn man, to miss those basics entirely while selling courses on engineering is just astounding.

the grifter mentality is probably so deeply engrained that I'm willing to bet that they never once thought "I'm totally qualified to sell courses", let alone question the thought.