• 2 Posts
  • 52 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle






  • 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









  • 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.






  • “Code is the documentation” is the paradise we all want to be someday. But some people use that as an excuse to not write the documentation explaining why this piece of code exists in the first place. I find it extremely annoying when there is not a single architecture diagram is available and someone tell me to figure it out by reading his/her spaghetti code.