It’s satisfying when your neurons make new connections. When you work with AI they don’t.

When you work with AI, it gives you the solution. You use your brain to manage the AI. Which is not as challenging and satisfying. When AI tells you the solution and you read (skim) it, you don’t really learn or understand. You still need time and effort for your brain to make the connections.

Stephen King on writing; “Look- here’s a table covered with red cloth. On it is a cage the size of a small fish aquarium. In the cage is a white rabbit with a pink nose and pink-rimmed eyes. […] On its back, clearly marked in blue ink, is the numeral 8. […] The most interesting thing here isn’t even the carrot-munching rabbit in the cage, but the number on its back. Not a six, not a four, not nineteen-point-five. It’s an eight. This is what we’re looking at, and we all see it. I didn’t tell you. You didn’t ask me. I never opened my mouth and you never opened yours. We’re not even in the same year together, let alone the same room… except we are together. We are close. We’re having a meeting of the minds. […] We’ve engaged in an act of telepathy. No mythy-mountain shit; real telepathy.”

Is human endeavor really just "neurons" and "reward pathways", skinner boxes nonsense? A writer writes, hoping his writings reaches the mind of others. A painter paints, hoping their paintings communicate a thousand words from his spirit's depths. I think the act of making effort is more than mastery, it is a commune with oneself, and others.

You can definitely use it as an incredibly powerful learning tool. I've been using it to guide me through Haskell and I've learned so much more than I did in college when I had spent way more time on it (that time being 10 years ago so I had forgotten most of it). It's invaluable being able to go and ask the AI questions and have it rephrase the parts you don't understand. I spent a good hour with it figuring out exactly what the traverse function does (`traverse (\x -> ['z', x]) "ab"` probably doesn't do what you think it should).

Spoiler: The <> combines lists as cross joins (for-loop within another for-loop). The lambda maps to new lists ['z', 'a'] and ['z', 'b'] (strings are just char arrays). It then computes the various combinations to recombine them so ['z', 'z'], ['z', 'b'], ['a', 'z'], ['a', 'b']. Note it's not all permutations since you don't have ['z', 'a'] even though that's actually one of the "base" arrays we got from the lambda. It took me a long time to really internalize that and it's still probably not a function I'd reach for.

It is kind of cool, though, that you can do `(,) <$> lista <> listb` and you get a nested for loop.