1. When you write something intended to be read by an important person, go through it and cut every unnecessary word. 2. The reader of anything you publish is an important person.

Before you go all in on a language, answer this: Are companies actually hiring for it? Or is AI about to eat it?

Thinking back, I was damn right to use different instances for staging and prod from the start. Anyway, this was a while back and operations are good to go and... The new engine is kicking it!

Thankfully, the VPS provider offered support as soon as I requested it (because nothing helped on the console either).

...it would have been as straightforward as finding another VPS provider and setting up a instance, and then set up the same Docker Swarm with the app containers, observability stack and other services and then restoring the DB backup from S3 (thank God I have Bash scripts)

Never happened before, but I wasn't all that surprised when it did. It made me wonder, however, that this would have been problematic if it happened to the production instance. Fortunately, prod has double the resources, and I already have frequent database backups, so...

Nothing, because even the commands often joined the queue. Imagine `docker system prune -a -f` taking long and still not completing. It wasn't long until I realised what was happening. I wasn't the only tenant, so some other VPS instance (on same infra) was draining all the juice

If I struggled to SSH into the VPS, surely the pipeline would always fail at the deploy job. And when I would even get in, I realised that it was being choked. Every system process was was halted and queued. What Linux commands could I have run to salvage the situation?

And my stress levels hit the roof when it was time to go production, just because of The Noisy Neighbor. It was a massive improvement. Of course, I was firstly going to deliver to staging and be very certain every checks out. But no, its VPS instance was unhealthy...

I've done this thing manually over 7 times now. I will soon vex and automate it

Day 1: "I have no idea what the helly I'm doing or how far I'll get, but let's see what 101% effort gets us..." Day 366, today: "Oh, shoot! How did we come this far? Might as well keep testing the limits and forging ahead."

To sleep on a problem and wake up with an unmistakable solution like a vivid vision feels like ecstasy. "I know what to do" becomes an assertive statement that speaks of control from within.

Note to self: You see the world through YOUR lens, and there are 8 billion more out there.

First class BSc in Actuarial science with two professional actuarial exams in the bag 📌

I'm going to deploy this new engine soon and only me would know the battles won (and lost), yet the users will really "feel" it regardless. Can't wait.

Scatterfocus. It's how I've been clearing up this much tech debt lately. That run, shower, or even cooking... and the eureka moment hits, then the way forward becomes less foggy once more.

Note to self: Strive to improve your taste - the ability to tell what's good. Go out there, learn what makes the good stuff good and the bad stuff bad. Art of delivering better quality.

Note to self: Gardens aren't natural. Someone's doing the work, and they're relentless against undesired...

22 80 443 3000 5432 8000 8080

Building an RBAC system is the perfect project for Go learners You will master authentication & authorization (JWT, bcrypt, sessions ) Clean architecture (layers, interfaces, dependency injection) Database design (many-to-many relationships, transactions) & Go fundamentals