Another example is the ACID nature of Arvo. Arvo is a pure function f(logs) of its event log, so formally Arvo is just a function run against an event log. A naive implementation has very bad asymptotics; processing each new event is O(n) in the number of historical events.
-
Show this thread
-
12) Correctness is more important than optimality.
1 reply 0 retweets 8 likesShow this thread -
13) If you don't completely understand your code and the semantics of all the code it depends on, your code is wrong.
1 reply 0 retweets 12 likesShow this thread -
14) Deterministic beats heuristic. Heuristics are evil and should only be used where determinism is infeasible, such as in cache reclamation.
1 reply 0 retweets 5 likesShow this thread -
15) Stateless is better than stateful.
1 reply 1 retweet 7 likesShow this thread -
16) Explicit state is better than implicit state.
1 reply 1 retweet 9 likesShow this thread -
17) Referential transparency is honesty and stability. Lack of referential transparency and other forms of disingenuousness are some of the world's big problems. Only deviate from referential transparency if absolutely necessary.
1 reply 0 retweets 4 likesShow this thread -
18) Responsibilities should be clearly separated. This applies from kernel modules through network citizens.
1 reply 0 retweets 4 likesShow this thread -
19) Dualities must be faced head-on and analyzed differently at different layers. Statically typed vs. dynamically typed, imperative vs. functional, code vs. data, and effectful vs. pure can all be a matter of perspective, and all relevant perspectives must have coherent answers
1 reply 1 retweet 6 likesShow this thread -
20) One hundred lines of simplicity is better than twenty lines of complexity. It's not enough for an abstraction to reduce code duplication; it must actually make the code simpler.
1 reply 0 retweets 11 likesShow this thread
21) Prefer mechanical simplicity to mathematical simplicity. Often mechanical simplicity and mathematical simplicity go together.
-
-
22) The Law of Leaky Abstractions is a lie; abstract airtightly. If your abstractions are leaking, it's not due to some law of the universe; you just suck at abstracting. Usually, you didn't specify the abstraction narrowly enough.
1 reply 0 retweets 8 likesShow this thread -
23) Some cliches are repeated because they are true; others must be repeated because they are not.
0 replies 0 retweets 5 likesShow this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.