+1

Impact Evaluators.md

··· 245 245 - [Community Notes Note ranking algorithm](https://communitynotes.x.com/guide/en/under-the-hood/ranking-notes) 246 246 - [Deep Funding is a Special Case of Generalized Impact Evaluators](https://hackmd.io/@dwddao/HypnqpQKke) 247 247 - [An Analysis of Pairwise Preference](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3359677) 248 248 + - [Analysing public goods games using reinforcement learning: effect of increasing group size on cooperation](https://royalsocietypublishing.org/doi/10.1098/rsos.241195)

+1

Making Decisions.md

··· 47 47 - [It's often not _how much force_ you can bring to bear, so much as whether you can apply that force _effectively_](https://www.lesswrong.com/posts/rQKstXH8ZMAdN5iqD/concentration-of-force). 48 48 - You don't feel the consequences/pain of the actions you don't take! A good decision can still have unintended consequences. 49 49 - [Most of the time there is no particular individual or approximation of an individual who's in charge](https://jscaseddon.co/2024/02/science-for-steering-vs-for-decision-making/). There’s a social or political process, in which many decision makers, each with different motivations that may or may not include anything other than self interest, negotiate, collaborate, compete, haggle, ... 50 50 + - Usually the baseline is "nothing" so the right heuristic is usually not "is it ideal" but rather "is it better than nothing?" 50 51 51 52  52 53

+1

Programming.md

··· 35 35 - You should be able to "punch through" your abstraction layer and get to the code behind it in cases you need that. 36 36 - Sometimes you have to stop sharpening the saw, and just start cutting. 37 37 - Software which is broken because there is no incentive to ship good software is going to stay broken until the incentives change. 38 38 + - [Software that's fast changes behavior](https://www.catherinejue.com/fast). Fast eliminates cognitive friction and signals simplicity. 38 39 - **Choose portability over efficiency**. 39 40 - If today's hardware just about runs a program with just about adequate efficiency, tomorrow's will run it with power to spare. 40 41 - The developer task is to make sure his program will run on that new hardware with minimal effort.