Reddit is already blocking some Proton VPN IPs…

This is actually not a good advice, from my experience. If we don’t monitor, refactor, or improve the code, the software will rot, sooner or later. “Don’t touch” doesn’t mean we don’t ever think about the code, but we make the conscious choice not to modify it.

my nerdy friend that went on that journey with me is a musician and fashion model lol.

Maybe his/her experience in keeping the system simple and beautiful helped him/her recognise the passion in art.

Haha your post made me reflect my journey. I had fun in college tinkering Arch Linux with i3. Now I’m an Infra Engineer (or DevOps Engineer, Platform Engineer, SRE, whatver) and still do the same job—keeping the system “reliable”.

That’s why I like it. No BS, no ads, no commercials, no show-offs, etc. Just some people with a bit of free time share their knowledge and stories.

I do wish we have more vibrant non-tech communities, though.

Then you have Clojure - a machine gun that shoots shivs.

Clojure. It’s just fun to write.

Firstly, it’s functional and “Lispy”. My code is super expressive. Writing code is like writing prose where I can choose a word (function) from a large vocabulary [1]. I can focus on high-level concepts and modifying states instead of fighting with low-level logic.

Secondly, it runs on JVM - an already robust and performant platform.

And there are so many good things that I cannot simply write in some words. The father of Clojure, Rich Hickey, is a genius in expressing Clojure’s design. You should check out some of his talks [2].

Too bad that Clojure is too “niche” that I haven’t got a chance to make a living by writing Clojure, yet. But learning it is one of the best decisions I’ve ever made in my career. Yes, it’s that good.

[1] https://clojuredocs.org/

[2] https://github.com/tallesl/Rich-Hickey-fanclub

Code aesthetic: If your code looks like a triangle, you’re seriously doing something wrong.

Let’s be honest, even if you finish that 600-page book, you might not “crack” the algorithm interview. The inteview requires you to grind the question, or simply a lot of practices.

I usually check in with myself:

• Am I growing in my career?
• Am I happy with my current workplace: people, culture, flexibility?
• Am I valued to the company, i.e. my opinions are considered and regarded to some certain?

If one or two of these conditions failed, I would consider moving. After all, if I went to a workplace and I didn’t find any joy or recognition, the paycheck wouldn’t make me stay.

Well, people tend to pick the easiest way to achieve an objective, even though the solution is not simple nor optimised.

AWS (Route53 specifically). Not common but my personal lab runs on AWS so it’s nice to have a place for everything.

insert Thanos stone meme.

We self host an instance to share knowledge about self-hosting that instance.

Wow you’re self-hosting a password manager! Don’t you feel scared if something went wrong?

I’m also running Adguard as my DNS-level adblocker on my Pi 3. Feels way more content than Pihole.

Could you list some of your “stuffs” that you run on your k3s? I’m curious.

Well, obvious reason: you can’t edit an outdated video with easy effort. But with text you can.

But for a tech talk or demo, I’d still prefer a video than written text.

It’s sad to see it spit out text from the training set without the actual knowledge of date and time. Like it would be more awesome if it could call time.Now(), but it 'll be a different story.

+1 for Go and Input fonts. You have the same stack as me.

+1 for Tailscale if one wants to get a private VPN up and running quickly.

Salvatore Sanfilippo - creator of Redis.

Well, he actually received many appreciations from the community. But it’s worth knowing IMO.

https://www.eu-startups.com/2011/01/an-interview-with-salvatore-sanfilippo-creator-of-redis-working-out-of-sicily/

And my questions got lost in a flood of messages… Even Discord now has to implement forums feature to prevent this problem.

I’ve been using this guide for writing a CLI tool for my company. Kudos to the authors for the amazing insights.