This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-07-25
Channels
- # announcements (1)
- # babashka (15)
- # biff (15)
- # calva (9)
- # cherry (18)
- # cider (43)
- # cljs-dev (1)
- # cljsrn (10)
- # clojure (14)
- # clojure-europe (47)
- # clojurescript (29)
- # clr (5)
- # conjure (1)
- # core-logic (17)
- # datomic (8)
- # emacs (22)
- # fulcro (3)
- # gratitude (1)
- # hoplon (23)
- # humor (1)
- # hyperfiddle (34)
- # jobs (1)
- # kaocha (1)
- # malli (3)
- # nrepl (4)
- # off-topic (18)
- # pathom (12)
- # pedestal (1)
- # polylith (1)
- # portal (17)
- # practicalli (1)
- # re-frame (19)
- # reitit (8)
- # releases (1)
- # rewrite-clj (4)
- # shadow-cljs (15)
- # sql (23)
- # tools-build (4)
Hello there, just join Slack and just started being interested in Clojure. I watched the brilliant talk https://www.youtube.com/watch?v=c5QF2HjHLSE&list=PLZdCLR02grLpIQQkyGLgIyt0eHE56aJqd, which is very inspiring, and I have some questions. How do you guys understand the difference between the "Decision Matrix" and the "Imp DM". What is the difference between the "Approach" discussed in Phase: Direction and the "Impl Approach" in Phase: Design? Do you have any insight to share? Thank you. From the https://download.clojure.org/presentations/DesignInPractice.pdf, there are two examples offered for the DM and Impl DM respectively. The DM one has the problem "Can't use Java methods that take Java functional interfaces without using an adapter or reify." to solve. The problem of Impl DM is "Need Java experience to access Math via static functions Direction Not generic - just j.Math". My limited knowledge can't help me understand why these two problems are on a different level.
You use a DM when you are comparing solutions to a problem, and that can happen any time. Obviously in exploring solution approaches to the main problem, but often as you get into the actual implementation there will be many micro decisions too. It’s uncommon for us to make 5 or 10 small DMs in the course of a significant piece of work for different aspects. And it’s not uncommon for these to interact and or feedback to prior DMs
On my phone atm, so I would need to look at those DMs again to say more (those specific ones were mostly work I did)
Sometimes the problem evolves as you work through it too and better understand it or change scoping
> On my phone atm, so I would need to look at those DMs again to say more (those specific ones were mostly work I did) Oh great, thank you for taking a look at my question. I really want to know more context to better understand this approach. 🙏
Any US citizens here? I want to discuss an opportunity.
Good. DM me to discuss!
Clojure joke of the day: you can take a horse to paredit but you can't make it slurp
I demand a barf joke now
@U052A8RUT take that back
Amazing - I had a Countour ROAM camera, a very old model. When I moved, I forgot it on my mom's house, never bothered again about it - I think the camera was forgotten somewhere, without ever charging, for about 4 years now. I just connected to my computer - it charged, and it still works!
Now that's what I call engineering!
Yeah, I mean, I forgot to charge my Kindle for, like, 6 months and it basically died
I heard about these stories... terrible "agile" engineering 😕