This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # asami (13)
- # babashka (6)
- # beginners (38)
- # calva (14)
- # cider (15)
- # circleci (13)
- # clj-kondo (4)
- # cljsrn (18)
- # clojure (164)
- # clojure-bay-area (3)
- # clojure-europe (46)
- # clojure-italy (8)
- # clojure-losangeles (3)
- # clojure-norway (3)
- # clojure-sweden (24)
- # clojure-uk (115)
- # clojurescript (79)
- # cursive (11)
- # datomic (24)
- # docker (2)
- # events (9)
- # figwheel-main (31)
- # fulcro (5)
- # honeysql (6)
- # jackdaw (7)
- # jobs (3)
- # jobs-discuss (16)
- # joker (1)
- # kaocha (6)
- # keechma (1)
- # lein-figwheel (1)
- # malli (6)
- # pathom (10)
- # podcasts (13)
- # practicalli (3)
- # react (4)
- # reagent (3)
- # reitit (8)
- # remote-jobs (3)
- # shadow-cljs (21)
- # sql (12)
- # tools-deps (20)
- # xtdb (24)
I've been thinking more about this and now feel guilty every time I write a function that tweaks a map rather than calling update with a function that just works on the value https://clojurians.slack.com/archives/CBJ5CGE0G/p1619255965278400
To me, I guess the difference is what you make top-level
(defn whatever-foo [my-map] (update my-map :foo #(...does whatever...)))
I guess it’s in the same vein as https://stuartsierra.com/2015/08/10/clojure-donts-redundant-map
(defn whatever [foo] ... does whatever...)
So the latter fn, can do
whatever to a
foo regardless of wether the
foo resides in a map or not (and under which key the
foo might be stored.
I think my only annoyance is that having a function that works on a map does encode knowledge about the structure in the function and this does matter when I'm working on two fields at once (tho maybe that is the right time for a bit of coupling as it relies on the structure of the map to make sense in the domain)
It was not clear to me whether you preferred the first whatever or the second whatever
Anyone here got an idea? I could secretly put this dynvar into
clojure.core but that would be evil.
It would be very useful if clojure had something like a proxy-var, which just proxied everything to another var. This would also solve the potemkin/import-vars stuff.
It was partly a miss-communication, I now realize. I thought I had been given more time than I had. So learning there is to double check this several times.
Not sure actually, will check the recording, but when we planned it there was only two speakers. I thought the time of the event was extended, but apparently we were supposed to shorten down… All that said though. I had underestimated how much I like to talk about Clojure, so I was also going a bit longer on that part than I had plan. In combination: Not good.
I've been there. Although by today I'm still convinced that they accidently cut me short on my very first presentation. Midway through i got that sign "5min" and I was speeding up like nothing. It was a little crazy.
Tomorrow I'll do a presentation for a company for their in-house monthly developer meetup, first time I'm doing something like that
@ordnungswidrig it will be made available. Not sure when. What you mention is exactly what happened today. He (the host) apologized deeply for this afterwards. It's new for him as well, so we both learned valuable things today. I'll keep at it. It was fun after all. Even though the live coding ended in a stupid crash of the app and I was too stressed out to see where I had errored.
My very first talk was a Clojure talk and I had live coding in it. I believe it went well, although it’s not recorded, so I don’t know. @ikitommi does 🙂
Then I did a talk with live coding that did not go well at all, and I basically stopped trying to live code after that. Just too much which can go wrong, and personally, I’m unsure about how valuable it is for people to see me evaluate forms which I’ve typed up already. I guess that to demonstrate “hot code reloading” to non believers, it’s worth it.
For some reason I'm more comfortable with live coding in an online talk than on stage. I try to avoid it on stage, but online it feels more natural since I'm at my own desk... or something...
Also depends on the length of the talk. When I'm really time constrained (a 20 minute talk) I avoid it
Yeah, definitely easier online. This was digital, but much more on stage than what you probably refer to as online.
I’d say it was worth it even though I ended up in a crash. And I will probably do it again. There was other factors involved today that threw me off balance so I couldn’t fix my stupid error because my brain totally shut down.
FWIW, I have given a few presentations that I thought went like shit, but years later someone came to me and told me he is doing Clojure professionally because he started trying it because of those talks (I remember one at a school and one at a non-Clojure IRL meetup).
I got some super nice comments in the live chat and also in another channel on this Slack. So, yeah, it was probably not all shit. I will need to work hard with figuring out how to stay within my time checkpoints. I get carried away speaking about Clojure, it is a much bigger deal for me than I had realised.