mjdowney
My OCaml:
let foo (x: bar): baz =
(\* Is this quuxable? *)
match is_quuxable x with
| Yes ->
(* Then, we have to ... \*)
All the OCaml I see in the wild: qlet%bind f = 's 't 'a 'b (fun ꙮ -> ꙮ ((<_<')) ꙮ)
[@@ppx_gov_backdoor (~b~e~p~i~s)]Three-outcome Kelly criterion for p(win, loss, ruin)
Show HN: Chrome extension to execute ChatGPT output inline (HTML/JS –> iframe)
https://github.com/matthewdowney/rendergpt
I've found it particularly useful for drawing SVGs.Also allows mixing in new code blocks one by one, so you can have a REPL-like conversation and add/overwrite JavaScript functions one by one.Screenshots and install instructions in the GitHub readme.Taking suggestions for any other kinds of structured output to render, too!
Help me find: interactive tutorial for a JavaScript scheme interpreter
Does anybody remember this, posted on HN?It was an interactive tutorial on a single page web app, where you have a code editor, some explanation for what the code is doing, and arrows to skip forward or backwards in the tutorial. You can then edit the code and see different results.IIRC the code was in JavaScript and it created a basic lisp/scheme interpreter.It explained succinctly concepts of...
After getting into all the second brain stuff and trying out quite a few ways of organizing this kind of information, I've started to think very carefully about what sort of implicit commitment I'm making when I write something down. I use a system of tags for things I need to look at later in some way, and I almost never tag links, but I often search back through them to find something particular that comes to mind, and I'm glad I store them.
Maybe you would have success reorienting your perspective to feel like "just" bookmarking is enough, such that there's not an implicit responsibility to come back and do something particular with the bookmarks? Or if you want that responsibility, that you can have one kind of bookmark that you're "just" saving, and another kind that you are okay committing to review?
Then it might become clearer just by the size of the folders if you're "assigning" yourself an impossible amount of work.
These are not the sweeping, fundamental changes that Bret Victor envisioned, but we are collectively moving toward more interactive programming. Imagine modern web development without hot reloading.
Clojure is the language where I see this happening most, and which is seeing the most expansion toward "visualization and interactivity as part of a the backend dev experience".
Sizing bets on FTX claims and a Monte Carlo simulation
If, for whatever reason, consumers of content are not immediately attuned to the difference between vacuous GPT-nonsense and something that would bring them value if they just thought hard enough, it might lead to an overall reduction of returns to thoughtful, high-quality content, even if that content is only momentarily over the head of the reader, but wouldn't be in the long run.
This obviously to the detriment of both the consumers and producers of content.
https://gist.github.com/matthewdowney/dab4d12d001152dec473e3...
Poker players make bets based on bank roll size and very good understanding of expected value. They either use Kelly criterion[1] or develop competing heuristics for value at risk[2].
Plenty of areas where psychology adds an interesting human dimension to decision making, but this and other risk-neutrality scenarios are not part of this category!
[1] https://en.wikipedia.org/wiki/Kelly_criterion#Criticism [2] http://www.eecs.harvard.edu/cs286r/courses/fall12/papers/Tho...