Pareto Optimal Dev
Search site
Haskell
Links to this note
"Simple Haskell" can result in simple code but complex codebases
Choosing "Fancy Haskell" can be for pragmatic reasons
examples of considering pareto optimality in software development
Learning Haskell by doing
Package management and configuration in emacs
Prefer macro-level simplicity even if it means micro-level complexity
Comments
View/Make Comment