Anecdotally one of my stumbling blocks with clojure was how to deal with errors. The language style heavily pushes to just coding the happy path and using nil p

Anecdotally one of my stumbling blocks with clojure was how to deal with errors. The language style heavily pushes to just coding the happy path and using nil punning, instead of exceptions, but sometimes you need to signal errors, so some libraries use keywords for error codes - but now that we have spec the community seems to be shifting opinion to “exceptions are ok-ish if a result of not conforming”. Both error codes and nils make spec definitions ugly, thus all the “maybe not” opinion by Rick... it seems someehat overwhelming, to be honest.