Great talk, it clarified a lot of stuff I had read and sounded too disconnected. The live typing complemented the theory very well. I knew how to use data types and data constructors intuitively but there is nothing like understanding where things come from and where they can lead you if you apply the concepts to the extreme.
Not actually about modeling data. Was hoping to learn some best practices for application data modeling. Instead, we saw how to implement Bool. (Like most tutorials show.) A better title would be: Introduction to the Haskell type system.
Scott Wlaschin has that kind of information ('making invalid states unrepresentable' and things like that) but in F# context, mostly. Still, it may be what you are looking for. Those type systems have the same roots.
This talk is unnecessarily complex. I'm not sure why the speaker used so many needlessly academic words when teaching such a basic class. The result is making simple concepts hard to grasp because of all the academic bloat that accompanies it. Other then that a relatively good introduction to Haskell ADT's... if you're academically inclined.
I felt like the talk was not complex at all. He used some academic words but explained them as he went. I think that is a good way to introduce someone to thinking in a way that is unfamiliar, especially because those words become useful when talking about Haskell in the community.
Perhaps so, I may have different opinions if I were to watch the talk again. But I remember watching this talk and feeling sorry for people who were just starting out (main audience of this talk), and wouldn't have a clue about the lingo. Been feeling recently that a lot of the functional community (Haskell in particular) suffers from a kind of academic elitism and in many cases simple concepts can be hard to grasp when presented assuming an academic background (I'm guilty of this too..). I may be wrong, but hey :)
Haskell Beginner Workshop: Very patient and careful presentation!! Thank's for publishing!
Great talk, it clarified a lot of stuff I had read and sounded too disconnected. The live typing complemented the theory very well. I knew how to use data types and data constructors intuitively but there is nothing like understanding where things come from and where they can lead you if you apply the concepts to the extreme.
Great talk! Too bad the sound goes out of sync with the video at 45:15
Not actually about modeling data. Was hoping to learn some best practices for application data modeling. Instead, we saw how to implement Bool. (Like most tutorials show.) A better title would be: Introduction to the Haskell type system.
Scott Wlaschin has that kind of information ('making invalid states unrepresentable' and things like that) but in F# context, mostly. Still, it may be what you are looking for. Those type systems have the same roots.
TIL not to use Identity to teach types ;)
This talk is unnecessarily complex. I'm not sure why the speaker used so many needlessly academic words when teaching such a basic class. The result is making simple concepts hard to grasp because of all the academic bloat that accompanies it. Other then that a relatively good introduction to Haskell ADT's... if you're academically inclined.
I felt like the talk was not complex at all. He used some academic words but explained them as he went. I think that is a good way to introduce someone to thinking in a way that is unfamiliar, especially because those words become useful when talking about Haskell in the community.
Perhaps so, I may have different opinions if I were to watch the talk again. But I remember watching this talk and feeling sorry for people who were just starting out (main audience of this talk), and wouldn't have a clue about the lingo. Been feeling recently that a lot of the functional community (Haskell in particular) suffers from a kind of academic elitism and in many cases simple concepts can be hard to grasp when presented assuming an academic background (I'm guilty of this too..). I may be wrong, but hey :)