Clojurians Log v2

@michael.e.loughlin - FYI. https://youtu.be/oS64_hmB_98

@asier I'm watching the video, it seems to be exactly the type of information I'm looking for. Thank you!

This feature of Duct (coming soon) will be interesting: https://github.com/duct-framework/duct/pull/89

@michael.e.loughlin I wrote up a long post yesterday that Slack dropped apparently. The gist of it was I consider duct modules half-open, and therefore not great as encapsulated units of functionality and configuration. Where this makes sense to use is when you make this the architectural basis for your team(s) and you actually take the time to read through the sources of third party duct modules, and intend to write plenty more modules yourself. Then assuming it's all rock-solid the only major annoyance is duct forcing you to do all your interactive development in the dev namespace. Or you peel this back and simply rely on third-party integrant method dependencies, and write the config yourself, which gives you a system that is a lot more flexible.