3 ms·
I know it is hard to strike a good balance between academic and technical focus, especially when writing about haskell, but I think starting out with language e
by maweki 7y ago
I know it is hard to strike a good balance between academic and technical focus, especially when writing about haskell, but I think starting out with language extensions and imports without writing about what and how we're going to do it, makes for difficult reading.
The smaller parts with the types and small implementations should be at the top and only at the end all is easily combined.
And I highly doubt that the author went about writing the chatbot by writing out all the language extensions and imports first (which makes the coding-along line at the and a bit cynical).
Edit: This sounds so negative. I think the article is good and shows how the small pieces work together but I think the order is all wrong.
- moleike 7y agoHi, author here. I agree that straight away throwing a bunch of language extensions without an explanation of why we need them at all wasn't a good idea. The original blog post was written in literate Haskell, that's the reason why the code is organized that way. I will think about rearranging the code blocks or add more explanations to make it all fit more naturally. Thanks for your feedback!
- maweki 7y agoWhen I teach or write about Haskell I try to break down the parts in a way that the parts can be tested using ghci and just composing it at the end. I think there are quite a few parts in there that one can easily "try out on their own".