One thing my team has struggled with in enterprise C# development is the complexity of unit test setup. This is complicated by Domain Driven Design, which encourages the use of concrete classes for entities and values. Test setup often becomes nontrivial as you are often required to set up considerably more of the object graph than what’s really necessary for the test at hand, simply because of the constructor signature on, say, a value object that you want to test.
This is much less of a problem in a dynamic language like Clojure, where there are no hard and fast rules about constructing objects – you can just create a map with only the properties you need for the test. For example, here’s a test in my Hearts project that invokes a function named next-player-pos and passes it a game of Hearts, which here is simply represented as an empty map {}:
(deftest next-player-at-start-is-first-player (with-redefs [first-player (constantly {:pos 2})] (is (= 2 (next-player-pos {})))))
Today, there are alot of options when it comes to choosing a career. With the boom in developer trends over the last 20 years, having a job as a ‘computer nerd’ is actually pretty cool and less nerdy. There are many different titles and options out there, so don’t limit yourself!
