* Be sure to read the agreements (https://github.com/vanfp/haskell-workshop) before RSVP
* Join the #hffp-workshop and #haskell-lunch-reading channels on VanDev Slack for announcements and help, get an invite via https://yvrdev.herokuapp.com/
* There are three (3) cohorts running at the same time, (1x evening, 2x lunch (the other lunch group is Spring '18))
* Pictures will be taken at the event and will be published on the Meetup event
Prep: Required Reading - chapter 7 (More functional patterns)
What to bring: Your laptop to work on exercises with others in the group
Try to do the exercises before you come and think of any questions you might have. There is not enough time during a lunch meetup to read the chapter and go through all the exercises together.
This event is happening at the Mobify office during lunch hour. Please be mindful of the space and make sure you're with the group at all times while at the office. Bathroom access is tricky, so try to accommodate for that before coming.
The Vancouver Functional Programming Meetup is organizing a space where people interested in learning the language can work together doing exercises from the book Haskell From First Principles (https://haskellbook.com/). Participants are expected to have their own copy of the book, and do all required readings and [at least attempt the] exercises before group sessions. Can't afford the book? (ex. you're a student) Let us know and we'll try to find you a book sponsor.
Why would I ever learn Haskell?
* Functional Programming (FP) is becoming more prevalent in our industry as time progresses, understanding it has become a crucial aspect if you aim to land at a software gig. We argue Haskell is one of the best languages there is to learn FP given it forces you to think in FP terms to use it effectively
* Haskell enforces some of the best software development practices by default, in the beginning, the language may feel constrained to work with, but as time progresses you'll get insight around the *why* the language is designed explicitly in that way, and what is better, how you can replicate that in your day to day language to avoid accidental complexity in your software.