This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-01
Channels
- # announcements (6)
- # beginners (68)
- # calva (5)
- # cider (3)
- # clara (1)
- # clojure (49)
- # clojure-europe (24)
- # clojure-nl (2)
- # clojure-norway (28)
- # clojure-seattle (1)
- # clojure-uk (5)
- # clojurescript (3)
- # conjure (5)
- # core-typed (6)
- # data-science (1)
- # datalevin (3)
- # datascript (3)
- # datavis (1)
- # datomic (19)
- # events (2)
- # fulcro (6)
- # gratitude (1)
- # helix (6)
- # hyperfiddle (19)
- # joyride (6)
- # lsp (20)
- # music (1)
- # nbb (12)
- # pathom (2)
- # pedestal (10)
- # re-frame (3)
- # reitit (3)
- # ring (5)
- # shadow-cljs (26)
- # yamlscript (17)
https://www.endatabas.com/ some XTDB guys got tired of Clojure and switched to Common Lisp?
Wow, that’s interesting. Håkan Råberg is behind it. He was the architect behind XTDB.
Morning!
Morning
Good morning 🙂
What's your experiences in talking clients out of requesting applications that have way too many rules, making them really tough to grok, both from a user, initial developer, maintaining developer and tester perspective? Or are you satisfied with the way(s) that you manage such complexity in code?
I think it’s very easy/tempting to fall into the complexity trap, and that the art is to understand the customers problem, and to create solutions which solve them well. This is not the same as implementing whatever the customer asks for. What the customer asks for is for you to implement their solution to their (unstated) problem.
Hard agree 🙂
We are using product discovery and design phases to create MVPs. This way in the relatively short time you remove (or move to the other phases) most of the complexities (in requirements)
måning