In Clojure, we use the Entity pattern all the time. Usually, it’s the first thing we notice when learning Clojure. The Entity pattern essentially means we use a HashMap to represent information about an entity. We look at how that works, and then we go over a variety of the Entity patterns called Variant Entity. We also look at a code smell and an anti-pattern.
Parts of courses on specific topics
Clojure obeys the Java standard library’s equality partitions. Namely, sequential, map, and set partitions for collections. These allow us to swap out different concrete implementations of our collections while still having equivalent logical collections.
In this lesson, we go over three tools to help you write and modify code faster. These are autocomplete, brace matching, and visual argument prompts. You may be familiar with these tools, but it’s important to think of them as options.
How do you assert that appropriate errors are thrown when they should?
We define a function to indicate an error.
We need to design an Event Sourcing system to be used by the rest of the app. I sketch it out on the whiteboard.