If you have many ports, they could be all over your project, and therefore hard to manage and easy for forget about. Keep track of all of them by representing your outgoing ports in a union type like..
type JsMsg
= Download
| Login Login.Payload
| Logout
| Track Tracking.Payload
Hello! I like making predictions and bets. I like measuring objectivity. I view it as a form of self improvement and a way of building self awareness of how well I know things. I write down what I think and what I expect and then follow up with my own records years later to see where my thinking went wrong. Then I try not to be wrong again. When I started doing this, losing would really hurt, but at this point I get a lot of joy from dissecting where I go wrong.
In this document I am going to go over bets and predictions I made that came to completion in 2020. Here are some previous write-ups I have done on previous years of predicting.
Back in December 2017, I started working on something I called Elmish-Wasm, which was just an experimental repo to compile something Elm-like to Wasm. I made some progress, but the helpful people I talked and I came to the conclusion that most of what I had so far (Haskell and Regex to interpret .elm files into rudimentary wasm) was something the Elm compiler and the Elm AST already did. Writing that code was a lot of fun, but maybe not the most valuable way to explore Elm and WebAssembly. Before jumping back into this project I would like to record the important facts and questions related to compiling Elm to Wasm.
A lot of people talk about Web Assembly as if its C++ that runs in the browser. Thats not the case. This belief must come from that fact that C can currently compile to web assembly. Wasm is human-unreadable bytecode. There is a human-readable version of wasm, called wat. It looks like this..
;; A function that adds two numbe
Hello! I like making predictions. I like measuring objectivity. I like self improvement and self reflection. Thats why I write down what I think and what I expect and then follow up with my own records years later to see where my thinking went wrong. Then I try not to be wrong again. One way I do this (a fun way of doing this) is gambling in prediction markets.
This is document is a summary of my performence in the political betting market during 2019. Here are some previous write-ups I have done on previous years of predicting.
This is the point in these check-in write ups where I explain political betting and predictions, but I have alrea
Last year I read and watched a bunch of history and military tactics material, mostly focused on World War II. I am definitely not an expert, and I dont suppose my thoughts are 100% correct, but I do have a new and improved understanding of WWII and maybe I can summarize it below.
There are two sections below: turning points, and broad strokes. Turning points are single key events that seem to have mattered a lot, and broad strokes are the big qualitative differences between the two sides that seemed to matter.
| bool listen(time: int) { | |
| // Blocking function that waits for `time` and then returns a bool representing | |
| // if there was a hit within that time period | |
| } | |
| int main() { | |
| // Succeeded in hitting the correct knock | |
| int succeeded = false; | |
| // A knock is a sequence of durations. Each duration is |
| M a ---------- M b | |
| | \ / | | |
| | \ / | | |
| | \ / | | |
| | \/ | | |
| | /\ | | |
| | / \ | | |
| | / \ | | |
| | / \ | | |
| a -------------- b |