Should big upside be big downside here?
> Take time replying. There’s small upside in replying instantly (however good it feels) & big upside [ed: see also Thinkie Upside, Downside].
> Take time replying. There’s small upside in replying instantly (however good it feels) & big upside [ed: see also Thinkie Upside, Downside].
October 5, 2025 at 10:46 PM
Should big upside be big downside here?
> Take time replying. There’s small upside in replying instantly (however good it feels) & big upside [ed: see also Thinkie Upside, Downside].
> Take time replying. There’s small upside in replying instantly (however good it feels) & big upside [ed: see also Thinkie Upside, Downside].
I love how you ask questions to gradually uncover how notebook-driven workflows can complement traditional software development!
Happy birthday :)
If you're inclined to dig deeper into notebook workflows, there's innovation going on in the Clojure community now — with the notebook inside the REPL.
Happy birthday :)
If you're inclined to dig deeper into notebook workflows, there's innovation going on in the Clojure community now — with the notebook inside the REPL.
April 17, 2025 at 1:12 PM
I love how you ask questions to gradually uncover how notebook-driven workflows can complement traditional software development!
Happy birthday :)
If you're inclined to dig deeper into notebook workflows, there's innovation going on in the Clojure community now — with the notebook inside the REPL.
Happy birthday :)
If you're inclined to dig deeper into notebook workflows, there's innovation going on in the Clojure community now — with the notebook inside the REPL.