I am a software developer and mostly write about coding related issues. A lot of my posts are related to the Elm programming language (and related). Some are more general.
-
Laziness would be good for Time.Extra.posixToParts -
No more imports -
Structural Custom Types -
SimulatedHttp, functors and sed -
Let signatures -
Immutability bugs again -
Templating HTML and String interpolation -
Overusing Right Pizza -
Case for if-then-else -
Uses and definitions -
Another polymorphism blind spot -
Polymorphism blind spot -
Elm missing features #1033 -
Elm input states -
Elm-format features -
Tailwind so far -
Elm paradox -
Response to a Tailwind Critique -
Elm-review as an optimiser -
Clients as a pitfall -
Is Elm faking work -
Paul Grahams's Programming Language Questions -
Impossible states and stale messages -
Html.Lazy and extensible records -
Let-in Let-in -
Unrelated bar usages -
Pattern matching records -
Missing language feature - Remove from scope -
Stale Messages in Elm -
Embedding HTML into an Elm program -
Surprising Elm -
Laziness again -
Generating from types -
Nested records and defensive programming -
Unit type and empty records -
Splitting Elm messages -
Type classes are meta-programming -
Lambdas again -
Safe dead code removal and compile-time laziness -
Frugal syntax formatter -
More compile time laziness -
Elm's Maybe.withDefault -
Elm and lambda expressions -
Elm records and let declarations -
Hungarian notation and Elm maybes. -
Elm - Minor imports syntax tweak -
Terser error messages -
Extensible custom types in Elm -
Elm errors with filenames -
Elm open source model -
Elm and comma separated lists -
Indent with two or four spaces -
My opinionated import style -
Or patterns -
Defensive programming and validations -
Elm extensible record syntax and warnings -
Elm catalog -
CLR, Purescript, and Elm -
Builder pattern record update operator