Things I think about when putting together effective method-level documentation.
Code written with reduce can be intimidating. This 2-step approach can help.
Branching early helps structure multi-step forms.
The contents of a map block should probably be an instance method on each item.
RSpec custom matchers can be written using plain old objects.
Rocket launches show us that we can know that two future events will be simultaneous, or what the local time will be, but not both.
Links to some of the best Elm data modeling resources around the web.
Using #tally to calculate the distribution of letters in a piece of text.
A visual answer to the question “what data is created when I execute this test?”.