

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.
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:
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.
Still grinding ToTK (90 hours in). I haven’t finished the main story yet even though I bought the game on the release date. I’m taking it slow and enjoy the journey.
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.
+1 for Go and Input fonts. You have the same stack as me.
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 got some tastes of FP while writing Ruby. And then I got times to tinker with Emacs Lisp. Fascinated by the idea of FP, I tried Clojure after that (without even knowing Java). And then I wanted to discover more Lisp-family languages: Common Lisp, Scheme, Racket, etc. You name it. This summer I was to learn Haskell, but got distracted by some university homeworks with Java Stream API…
Salvatore Sanfilippo - creator of Redis.
Well, he actually received many appreciations from the community. But it’s worth knowing IMO.
This guy is a genius. Also check out his other videos. Super funny and sarcastic.
I’ve been using this guide for writing a CLI tool for my company. Kudos to the authors for the amazing insights.
I was skeptical at first, but after using phind.com it partially changed my opinion on using AI for development assistance.
It massively helps me to filter out information and leads me to the right answer.
Like the other day, I searched on how to write some Latex symbols or how to use Java Stream API, it spit out the result immediately that saved my precious time on searching the Internet.
I don’t use CoPilot though.
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