Open psygo opened 3 years ago
This table, and different visualizations for it might become a small but interesting TUI — with brick, for example. I think I'm gonna give it a shot at some point — says the rookie who doesn't know what the hell he is doing.
@psygo Composing a vocabulary would be nice! I believe there are some of such things already, but I don't quite remember are they good enough or not.
I personally won't be doing this because I'm a bit busy on books writing.
Again, if there will be a good list of terms with helpful explanations, I'll be happy to reference it from the post.
I personally won't be doing this because I'm a bit busy on books writing.
Please include something like this on one of your books. I would buy a book for a map of Haskell alone.
I think I'm gonna fork this repo at some point and work on these suggestions on my own pace (this, #4, and #5). Once I feel like they are good enough, then I might either publish the content on a post on my website or give you a heads up here.
Please include something like this on one of your books.
@psygo I did!
So far I've noticed the pattern that many online tutorials — and even books — are so convoluted that they manage to, with their explanations, overcomplicate the concepts. And, as a beginner, I think that the path of being able to use the API with only the minimum amount of details necessary is usually much easier to cope with — or at least that's what I think happens with many beginners, not all. So I think that a summarized table of concept-and-short-definition would be a great resource — there should, of course, be a disclaimer somewhere that this table cannot ultimately replace working through the derivations of the concepts.
A table of tools and definitions really helps beginners become productive at the beginning, until they eventually know everything by heart, from regular use.
I don't have the necessary competence to create or complete such a table, but here's an example:
<>
), sometimes seen as concatenation⊥
)It would be nice if someone converted that table into a UML-like diagram and also a Venn diagram for alternative visualizations. The Typeclassopedia features a very nice diagram in that vein, maybe we could double-down on that.