If you’ve built software at any scale, you know how the game works. You get requirements from somewhere — usually they’re wrong or at best incomplete. You do your best to implement and … Continue reading Regulated software for software people
Today I’m setting aside my belief that all crypto is doomed to fail. It is, but that’s a medium-term diagnosis — at least for now, and ignoring the day-to-day bugs that occur in … Continue reading More crypto hijinks, aka WTF happened to Terra-Luna?
Have I mentioned how much I love our place on Whidbey Island? The ocean and animals are always present, and the house is built perfectly to take advantage of all that natural beauty. … Continue reading Milling (boards) and drilling (pockets)
So I guess I’m retired now.
I’ve been writing software for more than thirty years. I’m pretty OK at it, but not in the way most folks think about being good at writing code. I struggle to wrap my head around complex algorithms and kill a lot of trees tracing variables by hand on paper to understand them. I suspect, though, that that weakness is actually the reason behind whatever success I have had, because it’s forced me to focus on a few things that make or break large-scale production systems:
- Get the data model right.
- Fear complexity and crosstalk.
- Imagine the future.
Most of what I write will be Java, since that’s my go-to. I’ll link to files directly, but you can also find it in all its repo glory at https://github.com/seanno/shutdownhook.
I write about other stuff too, like my amateurish but super-fun attempts at building stuff out of wood — primarily the driftwood that washes up on our beach. Don’t say I didn’t give you fair warning.
Wayback machine: in previous lives, I wrote a few pieces about my work at Adaptive Biotechnologies and a ton while at Microsoft trying to help individuals get better healthcare.