bilinguliar

Without a policy, I refuse to have a clear understanding!

Zig. I know it has generics. But I am now more aligned with where the language is moving. I admire how easy it is to do data-oriented design in Zig.

To put my money where my mouth is, I am donating $50 earned with Go to Zig every month.

You can take my place, as the same changes make me want to leave.

You should partner with a Cloud repatriation company. Ping me :)

Sqlite + Litestream for backups.

I like how snappy Ghostty is. I do not like how it starts lagging after a few alt-tabs to Chrome and back on Linux.

Using self-hosted Mox for transactional emails.

Guided by the last generation of people with the know-how.

> That is irrelevant.

Why?

They support Passkeys. This is exactly how I continue using them after moving away from Google Workspaces.

It is a nice post. A point of improvement would be to name fields idiomatically. Author should run a few Go linters.

As an asset who successfully infiltrated a rival country's tech company you want deniability. Bringing your own IDE does not look suspicious.

I suggest pushing washing machine metrics to Prometheus, it just asks for it.

Temporal if you do not want vendor locks.

AWS Step Functions or GCP Workflows if you are on the cloud.

I am using Beanstalkd, it is small and fast and you just apt-get it on Debian.

However, I have noticed that oftentimes devs are using queues where Workflow Engines would be a better fit.

If your message processing time is in tens of seconds – talk to your local Workflow Engine professional (: