Hi. I was just laid off from my job at Mozilla (along with 250 of my coworkers). I’m looking for full-time engineering work, ideally in Rust, which I’ve come to love.
I’m located in Portland, OR, but willing to relocate after COVID dies down, but have quite a bit of experience working remotely as well.
I have a resume here (last update 8/15/20), it’s a bit rough around the edges and I intend to keep working on it a bit, but nothing good will come of me spending too long on it, so here it is.
I’ll try to update it periodically, but if the date listed above sounds like while ago, or you want the version that includes the bits I didn’t feel comfortable publishing on the internet (nothing scandalous, just personal info) feel free to send me an email and I’ll send you the unabridged copy of whatever is latest.
References are also available on request.
I really hate selling myself, so I’m going to paste an excerpt of something from an email I received from the most senior engineer on my team at the time when he heard I was laid off:
I don’t think we’d be successfully shipping as much as we are today without your input…
I think “thoroughness and rigor” is a pretty good summary of what I notice most about your work, and it’s a very valuable thing that can sadly be in short supply sometimes.
I joked once in slack that one of my favorite technical strategies was to post something that I knew to be incomplete but headed in vaguely the right direction, and wait for you to weigh in with the actual correct details, edge-cases, or things I hadn’t considered. Self-deprecating, yes, but also meant very genuinely; thank you.
(Sorry Ryan, if you didn’t want me to quote you, you shouldn’t have been so nice 😳)
I don’t think I’m quite worthy of this, but for things that must ship (and are not just prototypes or experiments), I do try to ensure my work is somewhat rigorously correct, or at least has a comment discussing the shortcomings.
(Admittedly; I also worked on Firefox Sync, which works well in practice, but is distantly far from a “rigorously correct” distributed system 😛)
Additionally, he’s right in calling out my exhaustively detailed github comments. Since my work is open source, some of my greatest hits are:
- uniffi-rs#244: Unnecessary sources of overhead in uniffi
- application-services#3349: Optimize project layout to avoid bad build performance
- Note: These were not written for work, and are a bit less professional in tone, but I’m somewhat proud of the investigative work that went into them:
(None of these are the issue that he was referring to, but that one was a much more run-of-the-mill “here are some facts I know about the problem”, and not something that I look back on and think “Wow, that took a lot of work, good job me”)
Anyway, if you would like me to program your Rust things, or leave overly-detailed comments in your issue trackers, please reach out.