I got through two fears past week:

1. Fear of heights.

I had to get on the roof of our 4 story apartment building to see where the leak is coming from and how to fix it. Climbing up the second time was way more easier. Even though I had more confidence in the second climb, I was still extra-extra careful.

2. Fear of deploying my project to production.

I was scared that everything might go wrong on the day of launch (my hands were shaking tbh). I prepared by setting up logs, settings up rollbacks, setting up testing and carefully testing the MVP manually.

With all of that, the first day of launching @JonliChatBot's MVP went good. All systems were stable, there were minimal runtime issues and people seemed to like the idea (which I really appreciate).

My thought after these experiences:

Be a blind optimist.
Be an extra cautious pessimist.
Be a realistically optimistic pessimist.

Perplexity's view on "Optmistic Pessimism":

Being a realistic optimistic pessimist means embracing a balanced viewpoint that recognizes life's complexities while fostering hope and resilience. This mindset allows individuals to face challenges head-on while maintaining a belief in their capacity for growth and success.

Gentlemen (and very few ladies) – we must start taking more risks in the coming year and getting out of the comfort zone

It's exactly 1 week until the end of the year. What will you do differently next year?

I need GTA 6 Trailer 2...now!

Perhaps a beginning of a new era?

Btw I’ve deleted Instagram and it somewhat helps to focus more on courses that I bought. Another reason why I’m not active there

If you're interested, you can follow me on x.com/ramzcoder or threads.net/@ramzcoder

Just bought ramzcoder.com and jonlichat.com

I’ve planned out all the courses I’ll watch over the next 6 months.

The first course, called Docker mastery is 21 hours long. I’ve been trying to spend an hour a day on average to watch and practice.

I’m combing video lessons with docs, youtube videos, articles, perplexity and claude.

I’ve reached Docker Swarm section and I’m now learning how to orchestrate containers on multiple nodes.

I’ve also switched to Neovim and I’ll be exclusively coding on it for the whole year (except for unusual circumstances, if such will happen for unknown reasons).

I’m also re-reading Clean Architecture and tbh, I’m now understanding far more than when I partially read it the first time.

I’m refactoring Jonli Chat too, although not as fast as a month ago. But I’ll get to it.

So that’s where I’m at. And yes, I still spend more time on X and Threads than anywhere else.

This will be epic. Lex is going interview the legends

Reading a book on customers’ needs

While I'm just getting started with Docker Swarm, I know for sure that there are differences between Docker Compose and Docker Swarm.

Docker Compose essentialy automates the process of starting containers, setting up networks, building images, publishing ports and setting up environment for you, so that you don't do it every time by hand with docker container run for each container. You just write one or more yml files and declaratively describe the services you need.

Docker Compose is good for development, so that you start multiple containers that depend on each other, but it won't handle orchestrating containers on multiple nodes, load balancing them, doing blue-green deployments, replicating containers between multiple nodes, etc.

So Docker Swarm is definitely the correct choice for when you want to ensure to have multiple nodes.

For now I'm playing around with Docker Swarm locally via multipass. I do plan to try and deploy multiple DigitalOcean droplets, initialize a Swarm and try to manage managers and workers, deploy stuff and break stuff.

As for Kubernetes, what I know for now is that it's more complex and allows more stuff to be done. Docker Swarm is pretty easy to set up, it comes with sensible defaults and you don't really have to do much.

I have about 120 lessons to watch. I do have a Docker book that I want to finish as well.