Should have used Go with Bubbletea.

> People must be hiding under a rock if they don't think this will have big consequences to society

People are not paying much mind to these freelance style jobs. It absolutely will have an impact on society.

This rule of three structure too: "We are a Western European company, so GDPR and data sovereignty are at the heart of our architecture, not an afterthought."

That emdash in your response. Chefs kiss

Even better it could just support WASM and be language agnostic.

It's actually already using wasmtime as one layer in its sandbox. I just think that trying to support other languages, especially in a fully language agnostic way, would make things like documentation far more complex than I could handle and make the service complex enough that the only people who could understand it would be the type of person who don't really need a service like this in the first place.

So which approach worked better?

Challenging to answer, because we're at different levels of programming. I'm Senior / Architect type with many years of experience programming, and he's an ME using code to help him with data processing and analysis.

I have a hunch if you asked which approach we took based on background, you'd think I was the one using the detailed prompt approach and him the vague.

Are they using these tests as a form of RLHF?

Puppeteer. Absolute game changer for building web frontends.

Playwright MCP is worth checking out too - similar idea but handles more browser contexts out of the box. Been using it for scraping and form automation.

Thanks to LetsEncrypt DNS-01, you can absolutely spin up a production-like environment with SSL and everything. It's definitely worth doing.

Not when that provider is AWS and the outage is hitting news websites. You share the link to AWS being down and go back to sleep.

News is one thing, if the app/service down impacts revenue, safety or security you won't be getting any sleep AWS or not.

No. You sit on the call and wait to restore your service to your users. There’s bullshit toil in disabling scale in as the outage gets longer.

Eventually, AWS has a VP of something dial in to your call to apologize. They’re unprepared and offer no new information. The get handed to a side call for executive bullshit.

AWS comes back. Your support rep only vaguely knows what’s going on. Your system serves some errors but digs out.

Then you go to sleep.