Technologies: Primarily backend engineering - APIs, databases (SQL and NoSQL), making complex systems work together. Enough of a full-stack dev (React, etc) to build personal apps for myself and my loved ones, but it's not my specialty. I'm expert in Typescript / Javascript, conversant in Ruby and Python, happy to learn other languages.
I'm a backend engineer with ~7 years of experience, most recently in the Risk division at Stripe for 3.5 years. On my teams, I've been known for making myself an expert on complex code and data, for being an excellent debugger and reviewer, for improving efficiency (on my last team, I took our core cron job's runtime from 8 hours to 15 minutes), and for working to invest in technical foundations.
I'm especially interested in complex technical problems, working with data and databases, and gaining new skills.
Somehow I've known about supernovas for many years without realizing that the word and concept "nova" exists as well. It's from the Latin for "new": the appearance of what seems to be a new star, because the star going nova brightened enough to become visible from Earth. (It got picked up from Tycho Brahe describing what we'd now call a supernova, though.)
The mechanism for non-super novas is very interesting: a white dwarf in a binary star system steals hydrogen from the other star, then heats it until it starts to fuse, which blows it all off into space!
> Microsoft has a similar problem where nobody gets promoted from fixing bugs or maintaining stuff, everyone gets rewarded for new innovative [thing] so every two-three years there's a completely new UI framework or similar.
Is there any big (or even medium-sized) company where this isn't true? I feel like it's just a rule of corporate culture that flashy overpromising projects get you promoted and regularly doing important but mundane and hard-to-measure things gets you PIP'd.
HN has really impressed upon me the value of site loading speed - one big reason I often check the comments first is that _they're there instantly_, whereas clicking on the actual link is a bit of a crapshoot! It's surprising how influential that difference is.
Remote: Yes
Willing to relocate: No
Technologies: Primarily backend engineering - APIs, databases (SQL and NoSQL), making complex systems work together. Enough of a full-stack dev (React, etc) to build personal apps for myself and my loved ones, but it's not my specialty. I'm expert in Typescript / Javascript, conversant in Ruby and Python, happy to learn other languages.
Resume: https://www.dropbox.com/scl/fi/3y2tf55v4zopivr4xze8w/Sam-Lie...
Email: samliebow [at] gmail [dot] com
I'm a backend engineer with ~7 years of experience, most recently in the Risk division at Stripe for 3.5 years. On my teams, I've been known for making myself an expert on complex code and data, for being an excellent debugger and reviewer, for improving efficiency (on my last team, I took our core cron job's runtime from 8 hours to 15 minutes), and for working to invest in technical foundations.
I'm especially interested in complex technical problems, working with data and databases, and gaining new skills.