[ggm]

I read a lot of beginner/tute FP stuff. A mistake they make is doing 2 sentences of "here's how to conceptualise this new notation and what Int -> Int -> Boolean means"

And then they get bored and just go full bore ¿ conjunctivitis applique to unbound ¤ variable 》》-> is a Mongolian {....} ... forgetting they were in tutorial mode. Or, showing examples which embed syntax which is apparently the same as before but "oh shit, I forgot a : means something else in this context" so having explained syntactically what a : means.. confusing you again.

Or showing REPL prompts without explaining if the # is a prompt or part of the command. The list is frankly endless.

Decades ago, this was C programmers trying to explain basic imperative syntax and then using a "compute prime" with a recursive function call or a ternary operator or bitshift.

So my next blog maybe will be "seven cardinal sins of blogs about basics" which will have only one sin: forgetting the job, the only one job you had (or apparently set yourself)

[arjie]

Hahaha, this is so accurate. I do this so often because I start off with a certain mindset and then when I get maybe 10% of the way through I find that I won't finish the post in any time if I write at this pace. So I have this idea! "Imperfect is Okay! I'll publish it and refine it over time by expounding on each section". Then I publish it and never look at it again. Hilarious! In the end, this entire genre of writing is no longer useful so I suppose not much harm is done.