I’ll have to take a look at this as a way to move off my homegrown serverless email on AWS. Doesn’t look like it has parity with being able to send email from many subsystems safely (with delay and veto)[1], but is pretty close on the receive side automation[2].

[1] https://github.com/mlhpdx/email-origin [2] https://github.com/mlhpdx/email-delivery

I dug up my original AWS account confirmation email from 2006 a while (years) back. Now I need to go find it again to see if I was earlier.

We have a moderately complex set of services we deploy with some separation of application code and infrastructure. No application code that runs on VMs is deployed as part of the infrastructure IaC - that’s all loaded once the “empty” infra is in place. The grey area is around non-VM compute like Lambda and Step Functions, which can be a part of the infra templates.

The way these services work requires an initial set of code to create the resources, and while it would be possible to send a “no-op” payload for the infrastructure deployment and then update it with real application code later, that seems pedantic (to us).

Maybe someday that changes, but for now it isn’t at all burdensome and we’ve been very successful with this approach.

Yeah, we've solidified that the day-0 path of deploying an empty image or no-op code deploy when first provisioning a service is the way to go and then letting CI/CD pick up the actual deployments longterm. I can see the "this seems pedantic" POV, but this is what we've found works across a number of cloud native services and accomplishes the end goal of managing infra with IaC and deploying with whatever tool we want for the application layer.

We have a similar array of deployment targets and the method is context dependent. The Kubernetes declarative manifests and reconciliation loop for applications is winning out, for our devs and industry at large. The cloud funcs / lambda are an annoying corner case, we do that with a late step in CI/CD currently, with a move to a dedicated Argo setup just for CD (workflows, not CD because that only does helm well)

Run it over WireGuard? I have this setup — cloud hosted private DNS protected by NOISE/ChaCha20. Only my devices can use it, because only they are configured as peers.

Does that mean running your own DNS in the cloud is a better answer? This is what I do.

What would they run on these days? I mean other than my old Gateway 2000 dual Pentium Pro with 32MB of RAM and dual booting BeOS and NT4?

Yes — talking and hearing/reading about it. I don’t fault folks for being excited when first getting into ut, but it’s rare to hear anything new said. And what is new is increasingly niche and unlikely to have any application to what I do.

If you read the history you’ll see the appropriate word is “restarted” the EV revolution. It was on and off again in a slow march to the point that allowed Tesla to exist. I’m not diminishing the role Tesla played, but it has to be taken in context. They stood on shoulders.

An over 125 year, often abandoned, stuttering march filled with stories of invisible battles by the entrenched to keep the status quo.

I think looking at every carmaker’s lineup should make it obvious that they don’t give a crap what powers a car, they are just trying to sell what’s popular. EVs were trendy for a couple years and a margin-subsidizing $7000 was available so everybody enthusiastically brought out EVs. Now they’re less popular so they’re all pulling back. Arguably even Tesla is doing so, given that Musk has intimidated that he didn’t really think Tesla was going to keep selling cars forever.

When the demand is sufficient, the cars will be sold in numbers to match it. Demand will increase as it becomes practical to own an EV for more people. This mainly has to do with charging infrastructure at every level, which is capital intensive for both individuals and governments.

It’s simply satire, not “truth”.

The statement doesn’t claim any fact: it’s a hypotheical not unlike a “based on real events” movie/book/etc that never quotes or attributes specific actions to a subject.

And that’s why Atlassian is very likely to lose over and over as they appeal (but never say never these days in the US).

Was the CEO dialing in from the headquarters of an NBA team they owned? Yes.

Were they calling to aggressively dismiss employee claims (without video I cannot prove "yelling", but that is a way that word is used in common parlance)? Yes.

Does downleveling employees have a significant negative impact on their careers? Yes.

This wasn't satire, it was truth.

American raised by a Brit here, and I was literally just doing this during lunch out. I consider the upside down fork just plain torture.