Thread by @patio11

Likewise recommended.

https://twitter.com/dinodaizovi/status/1442653112024580096

(Not wholly descriptive of things I’ve seen in my career but really important to understand broad strokes of how large software-oriented orgs operate compared to small shops and large non-software orgs.)

(And while there are lots of differences between and within companies it is, unsurprisingly, trivially true that e.g. eng team randomly picked at Google is more similar to one at Amazon than a randomly selected writer of code at Washington University or the IRS.)

(For one, astoundingly higher likelihood that an engineer randomly picked at Google has worked for Amazon than that they worked for IRS!)

It's a trueism in tech / finance that "Your most valuable asset leaves the building every night" (though I suppose these days might need to update that language) but underappreciated that things which resemble IP move around and are remixed as people move around and do remixing.

Aside: one of the reasons that hiring is sort of incestuous among a circle of tech firms is a belief that there is a very large body of industry practice that you need to know to be effective and that if you have 15 years in your career and 0 in big tech you're effectively green.

I always believed that to be disastrously untrue with respect to technical skills specifically but am coming around slightly with regards to the technical skill that is "knowing how to operate at AppAmaGooBookSoft", which includes e.g. dependency management by org chart not PR.

There's an obvious followup question "To what degree does this sort of thing describe development at Stripe in 2021?" and I think it deserves more considered writing by someone closer to it day-to-day; hopefully that happens sometime.