Why this page exists
This page describes how Haskell World is made. It is here so that you can decide how much weight to give anything else on the site.
Standards
Sourcing, checking, bylines, dates and commercial links, set out so you can judge what you read on Haskell World.
This page describes how Haskell World is made. It is here so that you can decide how much weight to give anything else on the site.
Some links on this site are commercial. They never buy a rewrite of the surrounding paragraph.
Requests to soften a verdict are declined, and we keep them on file. More than one has become the subject of its own paragraph later.
You can always see who wrote a page and what else they have put their name to. That traceability is deliberate, and it is why nothing here goes out unsigned.
Finnian Burke, Backend systems and language design writer. Finnian Burke spent eight years building distributed systems before leaving to write about the programming patterns that actually hold up under pressure. He has worked with Haskell, Rust, and Go in production, and writes mostly about the parts of functional programming that turn out to be useful regardless of the language you use day to day.
Sonja Reiter, Open source and developer tools writer. Sonja Reiter contributed to three major open source projects and started writing documentation when she noticed most tooling guides were written by people who had never taught anyone to use them. She covers build tools, package ecosystems, and the invisible quality-of-life differences between development setups.
Adil Sato, Programming languages and tutorials writer. Adil Sato teaches programming concepts at a community college and writes online guides for the questions students ask most in the second week of class, not the first. His focus is on making type systems, monads, and functional patterns understandable without reducing them to metaphors that break down the moment you try to use them for real work.
A subject earns a page when somebody has asked about it twice, or when we went looking for the answer ourselves and came back empty handed.
A draft goes through four hands worth of work. The writer separates what they know from what they assume. The assumptions are either checked against something nameable or deleted. What is left gets written up. Then a second person reads it looking only for overconfidence, which is the failure this subject invites most.
The date you see is real. A tidy up of wording leaves it alone; only a change to what the piece recommends moves the modified date, along with a note saying so.
Write to info@haskell.world with the page address and what is wrong. Factual errors are fixed quickly. If the correction changes the conclusion of a piece, we add a short note at the foot of the page rather than quietly editing it.