Happy to hear any feedback!
Quick personal feedback: based on the title I was expecting to discover some amazing, breakthrough, never-seen-before technique that adds a new dimension to âdoing CI fastâ with Haskell.
Then 2 minutes into the article, I was a bit underwhelmed, thinking to myself (sarcastically) âah yeah, well you implemented caching, good jobâ.
Apart from that, I can feel an overuse of âsuper-fastâ, âlightning-speedâ and similar qualifiers that are more an annoyance than anything else.
All in all, article tone and title are overselling what is essentially a basic 101 practice. Itâs a good and useful thing to explain how to implement CI caching specifically in Haskell, but maybe the article would gain being more honest and to-the-point.
Other than that itâs very clear and easy to read, and informative.
Iâm not the only person to over-sell a post in the title⌠I donât think itâs that sneaky, but I apologise if it was. I didnât say âsuper-fastâ - I gave an empirical metric based on my data.
Yes, everything there is completely straightforward to anyone with any CI experience. But many people are not familiar with CI, even intimidated by it (I was.) They were my target audience - I wanted to demonstrate that a large and complex config file is unneccesary, with only 14 lines of the unfamiliar technology you can go beyond making CI work - you can make it work for you.
Maybe I wasnât sufficiently clear that the post wasnât very Haskell-specific.
Thank you for your feedback!
Nice post! Clear and to the point!