that - Used to be a scientist; it’s still an area that works closely with research (when people listen) - Multiple implementations: the same goal - It has a lot of maths, if you want to
for everyone (democratic: more power to the algorithms vs. shiny stuff) - Many (productive!) ways to represent them and study them (math, graph theory, topology, code)
100% coverage of unit tests is the least of our concerns 2. Having a container-based approach for tests helps a lot 3. Testing in production: 4. Property-based testing: Fred Hebert