Alexander Lew¶
[Talk] Probabilistic scripts for automating common-sense tasks: https://www.youtube.com/watch?v=MiiWzJE0fEA&feature=youtu.be&ab_channel=StrangeLoop
Note
How can we use probablistic methods for cleaning data using the data that is being fixed. A declarative (instead of implerative) and principled (instead of heuristical) approacht to the problem. A different take on ‘declarative’ programing. Interesting to see why we won’t use ‘prolog’ i.e. we don’t know the constraints of the system. https://youtu.be/MiiWzJE0fEA?t=480
Eric Shull¶
[Talk] Communicating Sequential Processes in Go: https://www.youtube.com/watch?v=3gXWA6WEvOM&t=2047s&ab_channel=SoftwareGR
Jay Parlar¶
[Talk] Finding bugs without running or even looking at code: https://www.youtube.com/watch?v=FvNRlE4E9QQ&feature=youtu.be&ab_channel=StrangeLoop
Note
Bottom line, if you write stuff down, it helps you find problems. The more specific you are about your design, the more problems you find. The best you can do is to use formal methods to specify the systems. This is where alloy comes in.
Jay Parlar goes through a simple example and uses alloy to find counter examples in the system that doesn’t satisfy the checks.
Nicholas Kariniemi¶
Clojure compilation: https://blog.ndk.io/clojure-compilation.html
Why CSP matters - Part I: https://blog.ndk.io/why-csp-matters1.html
Why CSP matters - Part II: https://blog.ndk.io/why-csp-matters2.html
Reid McKenzie (arrdem)¶
Why Scala (and other static languages) don’t have a repl like clojure: https://stackoverflow.com/a/27391533/1589512