Software Engineer

I'm a computing generalist who mostly writes code, but has held a broad variety of roles, including k-root operator, network researcher, data engineer, trainer and car counter. Much of my code is on the system or platform level, but I can also build websites, apps, tooling or do data analysis or even a bit of GPU programming. Mostly I learn by doing, picking up skills as needed on the job or when hacking on open-source projects.

I've spent much of my career thinking about how we could build and operate software projects better. I've identified some problems common to most places I've worked and abstractions I think could solve them. This focus helps me be a better engineer and maybe someday I can turn these ideas into a company.

For the past 8 years I've spent half my time freelancing and am open to new gigs.

But I'm now hoping to find a permanent high-level IC position in a team of sharp, dedicated peers where I feel that craftsmanship is valued. I find when you dig into the weeds there is an infinite amount of interesting challenges in almost every domain; ideally we would be working on something with great potential to advance humanity and bring financial independence.

My style is modest, easy to understand architectures, ample docs and extra layers of security. I enjoy giving code reviews, accepting criticism and sharing knowledge. I'd say the most important skill of an engineer is managing the inevitable complexity that arises as systems grow, for example to isolate it by dividing a system into loosely-coupled components