And you are here why?

1. Identify the key features of whatever you are working on (e.g. “ consensus algorithm ”, “ FIFO Queue ”, “ Bubble sort ”) 2. Explain why your preferred language is the best language to implement whatever it is ( golang ,   C# , whatever. It doesn’t matter, as long as it is   your preferred language) 3. Preemptively claim that any weaknesses are actually strengths (The goofier the point, the better. e.g. “ Buffer overflows are   good , they help identify security threats! ”, “ Package management is not needed, because dependency fais an NP-complete problem! ”) 4. Randomly interject with comments about features that are “unique” to your language (It doesn’t matter if they actually are. The distraction   is   the point. e.g. “ Returning the value and error, of course, makes golang superior to everything else ”)

“ Wisdom gained is proportional to the size and number of f**k-ups ”  —  Me Herewith an excellent collection of Fun Things You Can Do With Virtual Memory . It’s really kinda cool, in that it’ll walk you through how you can use virtual memory to • create   Monster   arrays (easy!) • have performant Unique IDs (hint: it’s the VM address) • create gapless ring buffers (by mapping multiple virtual pages to the same physical page and oh,   so   much more, all of it really,   really   nifty. And when I read it, well, I shuddered. “ Why ” you wonder? Because these are   exactly   the kind of tricks that • Beginners use because… “ Hey,   Cool ! Check out what I just did! ” • TechBros use because they believe they are smart enough to (safely!) use. • But the   only   people who should be using these are people who are   wise   (and that is, like, very,   very   few people) And that brings me to the topic at hand, ...