Productivity

When I kick the bucket drum, I’ll leave behind three creations: my spawn and 10 buckets of bits. One bucket full of code and another brimming with notes. /* No, not these kinds of notes. */ Perhaps the artifact in this Game Over scene will instead be more akin to a single, large, loud volume where .exe and .wav files have gone to fade out their filename extensions and merge with abandon. In the game loop of my biocomputer, this is the degree to which for-loops and 16-bar loops play off each other and engage in a constant, consonant, interdisciplinary dance of call and response. I am reflecting not on some shallow, semantic version of symbols and cymbals in symbiosis but a real, requisite reciprocity recursing deep into namespace SubBass. ...

While my perception of my own knowledge path has been something like “I know nothing” -> “I know everything” -> “I know nothing”, engineers at any level can become overly convinced that their own approach is the correct one. A junior engineer straight out of school may be overly biased toward approaches taught there, which may or may not be effective in, for instance, a heavily product- and market-driven environment. Someone with a few years of experience may, due to their own definition of what success looks like, believe they have arrived and there’s not much more to learn. (This was me during the dot-com bubble.) A senior engineer with a decade or more of either going deep or wide can become too set in their ways and reluctant to incorporate different thinking, like single-brain groupthink. The rock star engineer, if you subscribe to such a thing, may well have developed an ego matching the size and approach attributes of a tropical island dictatorship. ...