Skip to content
0:00 / 0:00

#clojure#anomalies#de.otto/nom

How I learned to stop worrying and ignore anomalies (by Svante von Erichsen)

London Clojurians

3.9K subscribers • 52 videos on Hallway

YouTube
  • Recommended by 3 people: 3 in engineering communities.
  • Presented by Svante von Erichsen, software developer
  • Linked in the descriptionotto-de/nom

Intermediate. Assumes working knowledge.

1.7K views4 years ago3 recommendations

Programming languagesSoftware designLisp and ClojureDesign patterns

Svante von Erichsen introduces the de.otto/nom library and compares different error handling approaches in Clojure.

The London Clojurians are happy to present: Title: **How I learned to stop worrying and ignore anomalies** Speaker: **Svante von Erichsen** Time: **2022-03-29 @ (London time)** Local time: time.is/1830_29_Mar_2022_in_London/ (click here for local time) RSVP: meetup.com/London-Clojurians/events/283118185/ Svante von Erichsen (github.com/Harleqin) will be presenting: "How I learned to stop worrying and ignore anomalies" Anomalies are a way to return errors in your program flow, made popular by e. g. several Cognitect libraries. We recently published a toolbox, de.otto/nom (github.com/otto-de/nom) for ignoring them on the happy path. In this talk, we'll see what it does and compare that with some alternatives, such as railway-oriented programming, exceptions, and Failjure. This might be a missing piece, a sweet spot, or a crazy idea. Svante is a software developer at OTTO, a large e-commerce platform from Hamburg. Originally a chemist, he started learning Common Lisp around 2008. After starting with professional software development in 2011, he joined a startup using Clojure in 2016, and in 2018 switched to a team at OTTO also working in Clojure. His non-programming interests include playing Go, training Karate, and making Music. If you missed this event, you can watch the recording on our YouTube channel: youtube.com/c/LondonClojurians (The recording will be uploaded a couple of days after the event.) Please, consider supporting the London Clojurians with a small donation: opencollective.com/london-clojurians/ Your contributions will enable the sustainability of the London Clojurians community and support our varied set of online and in-person events: - ClojureBridge London: supports under-represented groups discover Clojure - re:Clojure: our **free** to attend annual community conference - monthly meetup events with speakers from all over the world - subscription and admin costs such as domain name & Zoom plan for larger online meetups Thank you to our sponsors: - juxt.pro/ - flexiana.com/ - cognitect.com/ - gaiwan.co/ - freshcodeit.com/ - healthunlocked.com/ - hyde-housing.co.uk/ - And many individual sponsors

Why it's here

3 people recommend this

What people say. Recommended as a good comparison of various ways to handle anomalies and errors in Clojure.

u/Wolfy87in r/Clojure • Recommends

On “New Clojurians: Ask Anything - October 14, 2024”

…d container. So maybe that option was what you were really looking for all along :) ## Alternatively... You could consider errors as values like https://github.com/fmnoise/flow or https://github.com/otto-de/nom (which is a nice helper for the concepts expressed in https://github.com/cognitect-labs/anomalies). Here's a talk on anomalies and nom link to this video I've just meandered here, but if you have specific follow up questions please fire away, I'll try to help.…

u/BrunoBonacciin r/Clojure • Recommends

London Clojurians Talk: How I learned to stop worrying and ignore anomalies (by Svante von Erichsen)

u/StJeeWain r/Clojure • Recommends

On “How to handle errors or failed computations in clojure?”

anomaly handling in clojure this video compares several ways of handling anomalies and I find it pretty good

u/BrunoBonacciin r/Clojure • Mentions

On “[ANN] London Clojurians Talk: How I learned to stop worrying and ignore anomalies (by Svante von Erichsen)”

Hi all, the recording of this event is now available on our YouTube channel: link to this video