Haskell User Group
From HaskellWiki
(Difference between revisions)
(→Topics) |
(there's no such thing as “too easy”) |
||
| (7 intermediate revisions not shown.) | |||
| Line 3: | Line 3: | ||
Want to start a Haskell User Group? These resources may help. They are geared towards a non-academic crowd who probably does not know anything about Haskell or Functional Programming and have regular meetings to talk about Haskell or FP. This page has a slightly different emphasis than a Haskell for Beginners one or a How to Learn Haskell page might. It specifically plays off the tendency for Haskell User Groups to have people with varying degrees of expertise/familiarity in Haskell. | Want to start a Haskell User Group? These resources may help. They are geared towards a non-academic crowd who probably does not know anything about Haskell or Functional Programming and have regular meetings to talk about Haskell or FP. This page has a slightly different emphasis than a Haskell for Beginners one or a How to Learn Haskell page might. It specifically plays off the tendency for Haskell User Groups to have people with varying degrees of expertise/familiarity in Haskell. | ||
| - | == Topics == | + | == Topics and debates == |
Great topics to cover | Great topics to cover | ||
| Line 12: | Line 12: | ||
* Laziness | * Laziness | ||
* Typeclasses | * Typeclasses | ||
| + | * Monads (save for later) | ||
== Coding Dojo == | == Coding Dojo == | ||
Best exercises for a Haskell coding Dojo | Best exercises for a Haskell coding Dojo | ||
| + | |||
| + | * Project Euler 1 is great for comparing languages - there's no such thing as "too" simple | ||
== Papers == | == Papers == | ||
| Line 21: | Line 24: | ||
Must-read academic papers for a non-academic non-FP crowd. Good Functional Pearls might also be nice here. | Must-read academic papers for a non-academic non-FP crowd. Good Functional Pearls might also be nice here. | ||
| - | + | # Why Functional Programming Matters | |
| - | + | # Tackling the Awkward Squad | |
| - | + | # Composing Contracts | |
| - | + | # Beautiful Concurrency | |
| - | + | ||
== User group tips and tricks == | == User group tips and tricks == | ||
Most likely external links to non-Haskell-specific sites | Most likely external links to non-Haskell-specific sites | ||
| + | |||
| + | * Consider GitHub as a place to put your code samples and talks. GitHub allows for organisation repositories, eg the [https://github.com/organizations/functionalbrighton Functional Brighton] one | ||
| + | * When trying to demonstrate techniques/technologies, don't be afraid of making your examples “too trivial”. Err on the side of simple. | ||
| + | |||
| + | [[Category:Community]] | ||
Current revision
Contents |
1 Haskell User Group Starter Kit
Want to start a Haskell User Group? These resources may help. They are geared towards a non-academic crowd who probably does not know anything about Haskell or Functional Programming and have regular meetings to talk about Haskell or FP. This page has a slightly different emphasis than a Haskell for Beginners one or a How to Learn Haskell page might. It specifically plays off the tendency for Haskell User Groups to have people with varying degrees of expertise/familiarity in Haskell.
1.1 Topics and debates
Great topics to cover
- What is functional programming?
- Solving problems a functional way
- Practical Haskell - IO, etc
- Laziness
- Typeclasses
- Monads (save for later)
1.2 Coding Dojo
Best exercises for a Haskell coding Dojo
- Project Euler 1 is great for comparing languages - there's no such thing as "too" simple
1.3 Papers
Must-read academic papers for a non-academic non-FP crowd. Good Functional Pearls might also be nice here.
- Why Functional Programming Matters
- Tackling the Awkward Squad
- Composing Contracts
- Beautiful Concurrency
1.4 User group tips and tricks
Most likely external links to non-Haskell-specific sites
- Consider GitHub as a place to put your code samples and talks. GitHub allows for organisation repositories, eg the Functional Brighton one
- When trying to demonstrate techniques/technologies, don't be afraid of making your examples “too trivial”. Err on the side of simple.
