Remind me of some quotes:

And once the storm is over, you won’t remember how you made it through, how you managed to survive. You won’t even be sure, whether the storm is really over. But one thing is certain. When you come out of the storm, you won’t be the same person who walked in. That’s what this storm’s all about.

No man ever steps in the same river twice, for it's not the same river and he's not the same man.

Recently, I came back home after 2.5 years of studying and working abroad. Home (family, friends, scene, etc.) didn't change much, but I definitely felt something off that it was hard to describe. I grew out of it, I suppose.

Welcome to the endless civil war between Linux distros.

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

My boss allows people to WFH officially, but also establishes several small office spaces so people can come to hang out if they feel lonely, or want to get to know their colleagues more. I think this is the best of both world.

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.

Officially, it should be 7 hours a day. But normally I work 5-6 hours. The rest are wasted on distractions and context switching. But deep work (i.e. actually getting things done) is normally 2-3 hours.

I also count meetings and chatting with colleagues are actual work. Those sessions might seem superficial but the way we collaborate with others is also important.

You have a pretty solid skill for a JR, to be honest. Sometimes I work with a mid-senior one and they don't know a single thing (well, a bit of exaggeration but they somehow "hacked" the system to get to that title).

Anyway, ignore the job requirements with 3+ years of Exp and apply anyway. Accept the first position that you feel "good enough" to gain practical experience. It will be your stepping stone to another job. Don't think that your first company will be ever be your final company for 10 or more years.

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.

42 degrees in Rome tomorrow (Tuesday). I'm going to take a siesta as well.

2 years are a bit extreme. I think 4-5 years is a good option. But if only if I don't like the company (culture, people, policy, etc.) or I don't see any advancement in my career.

I feel personal attack.

Add some needs:

• Configure the text editor daily.
• Switch to a new distro every month.