Clojure error messages and stacktraces are the number one most complained-about feature of Clojure. We look at some tips and resources for dealing with them.
Parts of courses on specific topics
Sometimes you want to test values that are almost right. Random values won’t cut it. What you can do is to generate correct values and mess them up. That’s called mutation testing, and it’s what we look at in this lesson.
We start factoring our User Interface into components, which are reusable pieces of our GUI.
We can put together generators that we need from the existing generators. There are four tools provided by test.check that help us do this. In this lesson, we go over such-that, fmap, bind, and let.
In this lesson, we learn to move our calculations from our components into Reactive Subscriptions. We don’t want to store calculated values in the database, because that would de-normalize the data. We learn how calculated subscriptions are a solution to database de-normalization.
This lesson teaches how to use functional abstraction to make changes to data structures quick and easy. This lesson includes a video screencast, a git repo, and two exercises. The video is 14 minutes long.
This lesson demonstrates and evaluates many different representations of playing cards. The lesson includes a video screencast, a git repository with all code, and some exercises. The video is 14 minutes long.
We interviewed Jason Gilman about his upcoming Clojure/conj 2016 talk about Proto REPL.
We interviewed Jason Hemann about his upcoming Code Mesh talk with Dan Friedman.
We interviewed Jay Martin about his upcoming Clojure Remote 2017 keynote called “The Value of Learning”.
We Interviewed Jean Yang about her upcoming Curry On 2017 talk about Preventing Information Leaks by Construction.
We interviewed Joe Armstrong about his upcoming Code Mesh keynote. He’ll also be interviewing Alan Kay on stage.
We interviewed Jon Pither about his upcoming ClojuTRE 2017 talk called Clojure Flavoured Devops.
Issue 381 – June 08, 2020 · Archives · Subscribe Police brutality has to stop ⚖️ All 50 United States are rising up in grief and anger after the brutal murder of George Floyd. And much of the world is demonstrating in solidarity. No Clojure in this issue. There’s too much at stake. Black people […]
Issue 380 – June 01, 2020 · Archives · Subscribe Clojure Tip 💡 what can you iterate through? I was helping a friend solve a coding challenge the other day and I quickly found a linear algorithm when he was sure it had to be quadratic. The key was that there were two collections. If […]
Issue 379 – May 25, 2020 · Archives · Subscribe Clojure Tip 💡 get has unexpected behavior, as expected Some people wonder about why get returns nil when the key is not found in the map. I actually like that behavior and dislike the behavior in other languages when it is an error to ask […]
Issue 378 – May 18, 2020 · Archives · Subscribe Clojure Tip 💡 Clojure nudges us to constant-time operations I recently received a question about why Clojure has contains? (which is really contains-key?) and not a contains-value?. It seems like such a common thing to want to do, shouldn’t Clojure give it to us? I […]
Issue 377 – May 11, 2020 · Archives · Subscribe Clojure Tip 💡 Three states of key-value pairs Sometimes I’m using a map and I want to both get the value for a key and check if the key exists in the map at the same time. In most cases, it would look something like […]