Clojurians Log v2

Nice talk! I like that he states that architecture is about organizing large and long-lived systems to improve changeability, modularity, and more, instead of getting stuck in what can be called design and architecture respectively.

I'm currently in the process of establishing a functional mindset, in combination with vertical slicing, clean architecture and domain driven design in a big team of object oriented developers. It's a challenge, but after some exposure, the developers really see the benefits, even in object oriented languages like java or kotlin.

can you recommend some good online resources on combinators?

I'm not really happy with the online resources I've found. On wikipedia there's https://en.wikipedia.org/wiki/Combinatory_logic and https://en.wikipedia.org/wiki/Fixed-point_combinator and there are some libraries implementing combinators for various languages.

@lsolbach the hardest part is to establish something that can only be shown, not spoken of. In my case I also try to bring Continuous Delivery (which requires trunk-based development, for example)

We have these guidelines, too and it is not really followed by the teams. Also the tests have to be enhanced a lot to give some of the teams the confidence, that nothing bad happens when you commit to main. It's a gradual process but at least I see constant progress.

The talk made me take a deeper look into combinators. What I find a bit difficult, coming from an OO background, even after 10+ years of clojure usage, is the terminology mismatch between the FP community and even Clojure. There are quite a few combinators in clojure.core, e.g. some-fn or every-pred, but it's not documented that they are actually combinators. It's a bit of an unknown unknown without an FP background.

Thanks for sharing; what a great talk! Any talk that mentions DDD instantly gains a special place in my heart.