Haskell Errors & Edge Cases
Errors & Edge Cases for Haskell: Writes the happy path well.
Who it is for
Writes the happy path well.
The behaviour people get wrong after they are already productive in the language.
You will get the most out of it if you have written Haskell recently enough to read it without effort, and have been surprised by it at least once. If you are picking the language up for the first time, start with Haskell Essentials and come back to this one.
It is also built for interview preparation: the questions are the ones that get asked because they separate people who have read the documentation from people who have hit the behaviour in production.
How long it takes
Planned at 90 graded questions, which is about 68 minutes of answering and roughly 18 days at five a day.
Nothing ships until every runnable snippet in it has been executed and matched against its answer.
Syllabus
What you will be asked about
This course is in production
It is planned as ten topics of ten questions, the same shape as every other course in the catalogue: one concept card, six multiple-choice questions, one predict-the-output, one ordering task and one matching task per topic. The topics themselves are mined from Haskell 2010 Language Report, and nothing is listed here until the questions exist and have been executed — a syllabus written before the content is a promise, and this page only carries facts.
Free and paid courses are decided per course, not per language, and this one will be included in a subscription.
The rest of the track
Haskell at every depth
Haskell Essentials
Essentials for Haskell: Knows the syntax, not yet the behaviour.
Haskell Core
Core for Haskell: Works in it, has gaps.
Haskell Data & Collections
Data & Collections for Haskell: Comfortable, but surprised by how containers behave.
Haskell Standard Library
Standard Library for Haskell: Reaches for a dependency before the built-in.
Haskell Idioms & Pitfalls
Idioms & Pitfalls for Haskell: Fluent, writes it like another language.
Haskell Advanced
Advanced for Haskell: Confident; wants the traps.
Haskell Performance
Performance for Haskell: Has never measured anything.
Haskell Testing
Testing for Haskell: Tests the code they wrote, not the code they meant.
Haskell Interview Questions
Interview Questions for Haskell: Preparing, and short of time.
Haskell Errors & Edge Cases is being written
Start with what is already live.
Every track that is already live works the same way: five questions a day, mixed across the courses you have enrolled in.
Browse the catalogue