Thread by @jeanqasaur

In the last few years, I've talked with hundreds, if not thousands, of software developers.

What I've learned: there's a HUGE gap between what developer-influencers are writing about, versus the daily reality of most developers. BUT PEOPLE DON'T TALK ABOUT THE OTHER STUFF. 1/

A disproportionate amount of writing and tooling comes from companies like Facebook, Netflix, LinkedIn, Google, and Amazon. Many people assume there's a trickle-down effect: great engineers at companies with money to burn come up with good solutions to problems everyone has. 2/

But the solutions that engineers at a Netflix or LinkedIn or Facebook come up with aren't for the vast majority of software shops: they're often best for big companies that can afford to set a high engineering bar, that can afford large infrastructure teams and ops teams. 3/

SO MANY of the software teams I've talked to have sheepishly told me that their software practices differ from the recommended standard.

When I listen to why, it makes a lot of sense for their needs: different org size, different eng team makeup, different shipping cadence. 4/

Many assume it's a matter a time before certain practices permeate the entire software industry.

But if you have piles of legacy code and/or limited engineering bandwidth, it absolutely does not make sense to redo your entire system using something that "makes sense." 5/

To start shedding unattainable software standards, let's:

🛑 Stop thinking of software as homogeneously represented by a small number of unrepresentative companies

🗯 Start being more honest about "real software process"

🛠 Demand more solutions to the real problems!!

end/