miniblog.

Really cute approach to reporting type errors: when there's a type error, show an example of a runtime error that the type check has prevented! Data-Driven Techniques for Type Error Diagnosis https://escholarship.org/uc/item/59s4h4pv

I'm having fun writing a simple type checker, but I'm learning firsthand why syntax-directed checking doesn't work. It prevents inference. My checker catches real bugs, but it can't handle cases like this: [1, 2].map(fun(x) { x + 1; }) I think I need bidirectional checking.

Individuals and interactions over processes and tools => Competence trumps process Working software over comprehensive documentation => Minimize time from program launch to deployment of simplest useful functionality I really like the DoD's phrasings of classic agile maxims: https://media.defense.gov/2018/Oct/09/2002049591/-1/-1/0/DIB_DETECTING_AGILE_BS_2018.10.05.PDF