Mark
_@mark.youngman.info
npub1f0rw...zj2x
One day, I'll be good at producing quality software and will have intelligent things to say about it
"To realize the spirit of Mu you must, without being sidetracked, travel along an iron rail stretching to infinity. One halt, much less many, will thwart enlightenment. The narrowest separation from Mu becomes a separation of miles. So take care, be vigilant! Don’t let go of Mu even for a moment while sitting, standing, walking, eating, or working.”
One underrated thing about vim modal editing is the magic of having the cursor bounce and then transforming characters in a few keystrokes. It's not even about efficiency. It's the innocent fun of a kid in a jungle gym. And it never seems to get old. It significantly increases the joy of coding for me
AWS charges for unauthorised writes to S3: https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-can-make-your-aws-bill-explode-934a383cb8b1
Long article, but worth the read.
https://medium.com/@john_25313/c-isnt-a-hangover-rust-isn-t-a-hangover-cure-580c9b35b5ce
"But, the reputation that memory safety problems currently have of being plentiful and trivial for sophisticated attackers to find and exploit is wrong.
[...]
C programs generally have a small number of external dependencies, where often those dependencies are among the most used pieces of software out there [...] Most other languages are much better equipped to support programmers leveraging the work of other programmers. In some sense, that’s a good thing from a business perspective. But from a security perspective, more dependencies not only tends to increase our attack surface, but it leaves us more open to supply chain attacks.
[...]
I have personally always been far more concerned about minimizing dependencies than buffer overflows. There are straightforward approaches to minimizing memory safety problems [...] But digging into each and every dependency?
[...]
My intent here isn’t to argue for using C over Rust, it’s to show that decisions around language choice are far more complex than the sound bytes people fling around."
Current mood:
Maybe disaster recover drills would be useful - prevent high-level disagreement in the moment and lead to a more polished response https://freedom-to-tinker.com/2015/07/28/analyzing-the-2013-bitcoin-fork-centralized-decision-making-saved-the-day/
Old article about Autotools
Why GNU Autotools is not my favorite build system | Jussi Pakkanen's development blog
List of qualities of a great dev. I only skimmed it - it's too long. I bet it was written by a dev or team who over complicate problems. They've certainly done that with this pdf. https://www.microsoft.com/en-us/research/uploads/prod/2019/03/Paul-Li-MSR-Tech-Report.pdf
