, 10 tweets, 2 min read Read on Twitter
Stripe is hiring. stripe.com/jobs

Some of the things which I like about the developer experience, coming from the polar opposite of Google scale:
You can pretty predictably get issued a new laptop (on day one) and immediately pull down the set of dependencies necessary to run your own instanced copy of (a subset up to the whole enchilada of) Stripe, somewhere in the cloud.
It feels surprisingly close to running a Rails monolith on localhost in terms of change behavior/poke/observe changed response loop, and the gap has been sharply narrowing over the last ~2 years.
(“Our developer experience gets magically upgraded continuously with a discontinuous upgrade every 6 months or so and this isn’t disruptive and you won’t want to stick on the old way” seems worth calling out as a feature.)
You’ve probably had a test suite before, but we have a test suite robust enough to have folks like yours truly deploy code without being unduly worried that credit card processing is going to go down worldwide.

(“This hardly ever happens” a good joke. Also literally true.)
We have a very nice, surprisingly simple, app which coordinates deploys of X00 services by X00 engineers in a way which minimizes contention, helps folks understand when their code uniquely has caused a regression, and lets someone who noticed a problem zero in on why quickly.
Livegrep exists, which you can get for yourself (and should, today, it is amazing).

You can grep substantially every line of code for every repository in a browser with X0 millisecond response time. Forget a function signature or commonly used pattern? 2 seconds of typing.
We have a nice internal frameworks and toolkits which make it easy to ship pages (and increasingly other things) and have them look like they were bespoke designed by the Stripe design team.

It’s gradually approaching “Bootstrap except phenomenal” (and gets better all the time).
All internal developer tooling very happily takes pull requests from all developers at the company, so if you see a possibility for a better error message or coverage for an interaction or edge case, just fixing it is an option.
(I can’t express how happy “JIRA: Hey it would really be nice if you prettyprinted the JavaScript linter errors in the web interface because following the textual stack traces to find the bug is driving me batty. Comment on my own JIRA: now you do.” makes me.)
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Patrick McKenzie
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!