This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-09
Channels
- # announcements (26)
- # babashka (4)
- # beginners (17)
- # calva (21)
- # cider (13)
- # clerk (17)
- # clj-commons (23)
- # clj-kondo (3)
- # cljdoc (47)
- # cljsrn (10)
- # clojure (123)
- # clojure-belgium (2)
- # clojure-dev (25)
- # clojure-europe (34)
- # clojure-gamedev (2)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-norway (4)
- # clojure-uk (4)
- # clojurescript (86)
- # cursive (12)
- # datahike (2)
- # datomic (2)
- # emacs (4)
- # fulcro (6)
- # funcool (15)
- # instaparse (1)
- # integrant (11)
- # jobs (1)
- # joyride (9)
- # kaocha (3)
- # membrane (8)
- # off-topic (1)
- # pathom (4)
- # practicalli (2)
- # quil (1)
- # rdf (1)
- # reagent (9)
- # remote-jobs (1)
- # shadow-cljs (27)
- # spacemacs (4)
- # specter (1)
- # sql (11)
- # tools-deps (55)
- # vim (1)
morning
Good morning! Show me some art that you appreciate.
That’s nice! Love me some hexagons and gradients. Did you do it?
@U4EPGBKPV I’ve had fun with quil as well. I toy with p5js now to get some vanilla js under my nails, have enough Clojure in my day job 🙂
I did, too, when I was doing Java, and applied for a government Clojure job just for the heck of it. I thought that they wouldn’t be able to pay me as well as what I was getting in the private sector, so I thought that it would just be interview practice. Welp, turns out they could, and I’m still here 6 years later :hugging_face:
@U0AQ3HP9U which government is this?
@U0AQ3HP9U is that the same SKAT project I heard about?
@U7PBP4UVA to follow up; I had a job lined up, but it turned out that, against all assumptions and zeitgeists, I could continue working from home at my current workplace. The other job position was nice, too, but looking around for a new place had given me opportunity to reflect on the good aspects of my current workplace, so I was a little embarrassed when I had to say no to the new place, given the time and resources put into the interview process.
My job is not perfect, but it's quite good in a lot of ways, and especially in the ones that, it turns out, are important to me :hugging_face:
good morning!
moorning 🤧🥶
Morning!
moorning
so i find myself thinking of refactoring a variant/tagged-union type expressed as [<tag> <value>]
into a map {:tag <tag> :val-k-1 <val-1> :val-k-2 <val-2> ...}
largely because it will have more readable get-in
paths e.g. [:val-k-1 :id]
instead of [1 :id]
and it's easier to infer intent from literal values
this scenario has happened a few times with code i've written (although this time it's not my code - the tagged-unions are re-frame events, in a back-end port of re-frame)
should it be a guideline that if you need a tagged-union then you should default to reaching for a map-based representation unless there is a very good reason (such as order) for using a vector-based representation ?
Elements of Clojure discuss this at one point, I believe. The recommendation was that it is fine to use a vector of data in very local context, ie where the creation and consumption of the data is on the same text page. Maps for anything more remote.
yeah, that sounds sensible @U0522TWDA