I don't know if Telegram, Slack, Discord, GitHub Actions, GitLab CI, Jenkins, or Kubernetes will be around (or without massive breaking changes) in 20 years, but email absolutely will be.

I knew a guy who would brag that he used Outlook as his build system 20 years ago. Builds would take 9 to 24 months depending on the complexity of the project. But, as the CTO of a mid-sized software company, it worked for him.

Memories of waiting for months to get access to a MS SQL database and ending up putting an Access database on a network share for multiple user access instead. A horrible, horrible hack solution. But it worked!

>When you leave software developers alone for too long, they start developing software

I've gotten so bored at work lately I've been coding for fun again

/Mail/Messaging in SMTP, and you have what it is: A message broker and queue. It has durability, retries, everything

This is horrifying.

>Shoddy stuff that has no chance of making its way into production is permissible

That's cute.

As a dev currently working at a company where getting an access request fulfilled can sometimes take weeks, I feel this author's pain.

But it seems like an enormous security hole, even with a codeword "password". The author didn't mention it, but I hope they're using whatever version of their company's E2E email encryption is for these messages.

Might need to implement this at current project but with Teams

Realest post I've read in a long time

Hacky is as hacky does.

that guy is a fuckin legend

If your build pipeline is anything more than a deploy.sh file containing

  docker build -t your-docker-registry/xxx:latest .

  docker push your-docker-registry/xxx:latest

  kubectl rollout restart deployment xxx-deployment