maybe you get more 'points' from the compiler if the value is observable in an _ambient_ way, where you can sense something going wrong in your program without having to explicitly inspect anything

rfid bookmarks

dynamic types vs. static types / non-hygienic vs. hygienic macros / memory-unsafe vs. memory-safe systems programming all feel like echoes of the same argument at different scales

i wonder if there are people who have synesthesia for like concurrency problems -- like sliding threads against each other and feeling for where they might catch

sometimes i just want to have multiple variables that are 'knotted' together so i have to set them at the same time and they can't get out of sync -- this is a lot of the use of compound datatypes…

when my friends know me

"Your implementation of this method should be as fast as possible and do as little work as possible."

need memcpy w stride

:0