What I miss about working at Stripe Few insights on what made Stripe a great company to work for.
- Everyone is encouraged to write everything down and then share it to a Google Group that anyone at the company could subscribe to and read, whether it was a meaningful strategy document, personal musings on a topic, or a mundane email exchange
- Conversations often found their way to a whitepaper or book someone had recently read or posted in our inspiration Slack channel.
- It felt like magic, but there was deep thought, care, and intention behind everything
- They had high standards and they avoided the lgtm (looks good to me) culture
- Stripe is a big mood (Culture of doing things)
- If you think disenchantment is a sign of disaster, you’ll probably abandon what you’re doing. In order to stick with anything for a long period of time, you have to believe that disenchantment is a normal, healthy part of experience. Continuity is only possible if change is factored in
- We live in waves: peaks and troughs followed by peaks and troughs. When you’re at a local minima, it’s easy to catastrophize and believe that everything is doomed. When you’re at a local maxima, it’s easy to believe that this is the best things will ever be. Usually neither is true
- There’s this joke I make a lot about having “real thoughts”—real thoughts in this case referring to an opinion that’s not reflexive, not a product of your immediate environment. Something that springs from actual sustained engagement with the world around you. It’s hard to have a real thought
- That’s the fight—sticking with something long enough to have actually meaningful observations. You have to weather a lot of peaks and troughs to get there, but the time spent is worth it
Working in the software industry, circa 1989 Software industry is a very different place 30 years ago, lots of things we all take for granted didn’t exist.
- The Internet existed but not the Web
- Companies paid for software entirely up front and got to use the release they bought forever
- The whole industry did very long release projects, such as two months of requirements gathering and design specification followed by nine months of coding and then three months of testing
- Every release went out with a whole bunch of known bugs that we’d fix in what we called a “fast follower” released several weeks later. Smart customers learned not to install the release until the “fast follower” was available
- The software engineering team had two titles: Software Engineer and Senior Software Engineer. This was typical in the industry. You had to have at least 10 years of experience, but more likely 15 years, as a Software Engineer before being considered for promotion to Senior
Won’t address climate change for yourselves? How about for the guy who designs heat maps? A plea to stop climate change from the guy who makes maps
My point is, unless you are here with some kind of innovative new color that is clearly hotter than red and won’t create these ambiguities, our only alternative is to stop climate change. If you won’t do it for the charismatic megafauna or the less charismatic fauna of normal size, or for your grandchildren, or for yourselves, do it for me, the guy who designed the heat scale for weather maps. I know this is a stupider reason than the reasons that already exist for you to take action, but people often do things for asinine reasons that they would not do for good ones, so maybe if you think about me having to color the map a confusing shade of vermilion or cochineal or, I guess, go back around? I have nothing! you will take pity in a way that you didn’t when human beings were literally dying? I don’t know, man. I’m not sure how many more heat waves like this my map can take. And that is the problem, of course. My map.