access to all the information about a pipeline, and we may want to
process and/or pass through more of it later.
> Thanks for all the help! I'm learning a ton.
>>
>
Cheers :)
On Monday, December 14, 2020 at 11:35:15 PM UTC-6 aditya@gmail.com
>> wrote:
>>
>>&g
I'd try to separate the "I/O or side-effecting" parts from the "purely data
processing" parts. This makes the program much easier to test --- the
"purer" the code, the better it is. This also helps tease apart
domain-agnostic parts from domain-specialised parts, which is useful,
because
Thanks to all the 4clojure maintainers and contributors, and special thanks
to you, Alan for keeping the lights on for so long.
4clojure helped me as I muddled through learning Clojure almost eight years
ago (good grief, eight years!). At the time it was perhaps the only
beginner-accessible
So from an ops point of view, I like your first approach; viz. pass the
environment parameter explicitly.
I prefer being explicit about every single invocation of any ops task.
The namespace solution, while being "legal", causes the configuration to
become implicit, one has to look at the REPL
