Here is an interesting article ‘Stacked Diffs Versus Pull Requests’ written by Jackson Gabbard.
Important note about the quality of the codebase (in context of stacked diff, i.e. trunk based development):
In this model, every commit must pass lint. It must pass unit tests. It must build. Every commit should have a test plan. A description. A meaningful title. Every. Single. Commit. This level of discipline means the code quality bar is fundamentally higher than the Pull Request world… I didn't think a lot about it before, but it definitely seems realistic.
Nice tool to control and monitoring cache state.
Source
The 2020 State of Enterprise Machine Learning report
download
A couple of articles about distributed transactions and scalability:
Online Event Processing Achieving consistency where distributed transactions have failed [link]
written by Martin Kleppmann [twitter], Alastair R. Beresford [twitter], and Boerge Svingen [twitter]
Life beyond Distributed Transactions: an Apostate’s Opinion [link]
written by Pat Helland [twitter]
Got tired to enter ssh passphrases on mac os and want to know how easily force ssh-agent to remember ssh keys?
Add this snippet to ~/.ssh/config file:
Host * AddKeysToAgent yes UseKeychain yes Source