“If it compiles, it works” is a common sentiment expressed by Elm users (as well as Rust and Haskell and Ocaml users). But this episode is more than its title suggests: the two hosts thoughtfully examine their own experiences and feelings to figure out
what they mean when they say ‘if it compiles it works’ – do they feel it with every program? No? What sort of programs do they feel it with?
and where does that feeling come from? How does the language/compiler contribute?
is it just programs that give you ‘yay, the compiler has my back’ feelings? No, it’s also certain changes; but what kind of changes?
and which of their Elm projects did not give them ‘if it compiles it works’ feelings?
and what was it about those programs that made them feel the compiler’s assurances were not enough?
which programming choice make it likely that you will still confuse yourself despite the compiler’s assurances?
Super interesting stuff, discussed in a rigorous experiental way that I haven’t seen before in programming podcast or article.
“If it compiles, it works” is a common sentiment expressed by Elm users (as well as Rust and Haskell and Ocaml users). But this episode is more than its title suggests: the two hosts thoughtfully examine their own experiences and feelings to figure out
Super interesting stuff, discussed in a rigorous experiental way that I haven’t seen before in programming podcast or article.