clojure-europe 2022-07-13

robert-stuttaford06:07:23

hi, stardust!

reefersleep07:07:42

Good morning, citizens

dharrigan07:07:34

Those photos from JWST are really outstanding

➕ 3

dharrigan07:07:55

And I love the science that they detected water on an exoplanet

slipset07:07:36

Morning from vacation land. Here’s a thing we did recently. At Ardoq we have several engineering teams, and while every team is allowed and encouraged to change whatever code they need, there is still some sense of ownership, ie this ns “belongs” to that team. Furthermore, we monitor our logs for messages of level ERROR . Now, up until recently, we’ve had one channel in slack production-alarms which got a message every time there was an error in the logs. This is good, but not great, as every team spends time monitoring the production-alarms channel. So, to fix this we added {:team "this-team"} metadata to our ns-decls, and augmented our logging to add team info to the log information we send to our ELK stack. This way, we can have alerts pr team in slack 🙂 I guess the general learning here for me at least is that Clojure meta data is sometimes very useful, and the fact that you can attach meta data to most things is also very useful, but 🙂 meta data is also very opaque and fragile and should be used sparingly/with care :)

🙌 8

👍 2

jcf09:07:35

I love the use of metadata here! This seems like a great example of where we could use namespaced keywords to reduce the opacity.

^{:com.ardoq.slack.team/id "ABC123"}

My thinking is we're introducing a global name, owned by Ardoq, that's self-documenting enough that a fresh pair of eyes would know what we're describing.

➕ 1

jcf09:07:52

I might have to borrow this idea. Thanks for sharing, @slipset!

simongray08:07:44

morning

🌅 1

otfrom09:07:54

morning

ray09:07:48

Good morning, buzzing

😀 1

🐝 5