install package -> hack on package

"Please remember that the kernel is for running userspace" https://lwn.net/Articles/803421/

finally learning about `perf probe` -- https://bristot.me/using-perf-probe-to-measure-execution-time-of-user-space-code-on-linux/ -- think I want to add a hook to scripting language so I can inject probes at script level. might just JIT & call a stub C function with unique name and then probe that

trying to hold to the old rule that when you're writing a script, you use the long-form versions of command-line arguments (`--pid` instead of `p`, etc) because documentation and future readability is more important than convenience of typing

Feel like I spend most of my time looking at weird-shaped USB cables on Amazon

I think that this feeling of exploration requires that you have 'limbs'/'actuators' that you control and use to interact with the space, that you're continually moving around and making active choices to inspect & poke at things, and "feed" interfaces are antithetical to that sort of engagement https://mastodon.social/@rjkwon/112299691696820710

anyway, i think you're only allowed to run your own code on your computer if every keystroke of the source code has been signed by your keyboard

(https://old.reddit.com/r/todayilearned/comments/a5e6a7/til_that_in_victorian_london_mail_was_delivered/#ebm4qdk)