shockleyje
So I’m one of his few remaining descendants and.. funny story, though likely for the best, despite knowing his professional history and subsequent legacy of “Doc Shock” I didn’t even consider to ride the coattails of our family name.
It wasn’t until a decade into my career when I found myself in a founding engineer role of a small database proxy startup, and presented with the problem of “how do I get a room full of engineers to hush up and listen” (as a conference speaker), did the idea to leverage the family name as a pseudo appeal-to-authority dawn on me.
I’m happy that I took the self-made route, rather than leveraging the family name earlier in my career (and to more direct effect). Though the dramatic irony of knowing it was through my own incompetence, not through some greater moral code, that I didn’t lean more into nepotism as a career advantage will never cease to get make me laugh at my own little inside joke at the self-schadenfrende of it.
But back to your quote, I can confidently say the “genius” apple doesn’t fall far from the tree in regard to Shockmeister’s sub-genius status. My only hope is that I can continue to avoid whatever apple gave him the eugenics bug.
Based on my relationship with intelligence, it’s not been my sheer intelligence that’s been my greatest asset. It’s actually the inverse! I can easily reform my mental model at different levels of resolution. This means I can be both an engineer’s engineer when building, while also being able to communicate the same ideas to hundreds of people in a conference context and achieve great sales funnel conversations from that.
I attribute whatever this latent predisposition to recognize potential applications of technologies strategically early to whatever led my former to his discovery. As a result, I have a great track record of spending ‘innovation tokens’ wisely, to quote Choose Boring Technologies.
Concretely, the latest investment I made was in standardizing my current startup around Mise. Not because it’s a great DX, but because I believe the primitives mise provides are a key enabler for agentic development in a distributed org and team context. I _may_ be productizing a public version of our organization’s agent runtime, since I believe my choices in technologies, conventions, onboarding flow, and most importantly - positioning within the organization - provide a turnkey solution to the problem every mid-size-and-up tier CTO has with their board: having a defined AI strategy where token spend justifies due to run costs scaling with respect to engineering & product deliverables produced.
Happy to answer any questions, though to be blunt, considering that Willie B (a.k.a. William Bradford) passed before I had the opportunity to meet him, I don’t have much tribal knowledge of his life to share. Though, to the credit of my immediate family’s character, he was already estranged leading up to his infamous public television appearances.
I’ve been considering writing a biography on what my experience with the duality of living ‘up’ to his (positive) professional legacy while navigating recognition of the harm he caused has done to affect me, both the headwinds & tailwinds.
I like the way this story portrays his success in solving open-ended problems as long as they aligned with the company direction. I've personally never made that connection between us, but it resonates with where I've personally found success, and currently am, in my career as well.
Fortunately, a lot of our beliefs about the world are quite different.
Most of the effort, honestly, went into the compatibility layer when bridging which version of the ID was accepted on a given API, and ensuring that this major change was implemented between services universally (i.e., is service B going to fail if I send a prefixed ID?).
All of this to say, I am hesitant to generally recommend migrating from UUID -> prefixed UUID, but I will be considering starting future projects of my own with UPID