So I bought two accounts on your service--one for personal use, and one for business use. Please react, large companies!

Microsoft: WHAT THE HELL IS HAPPENING OH MY GOD PLEASE KILL ME AND END MY TORMENT
Slack: You're my favorite two daily active users.
Google: Fuck your business account, why would you pay us? What is wrong with you?
LinkedIn: Has either account tried premium?
GitHub: Two accounts? Sure. Okay. Okay. Sure. Your green squares graph is gonna suck.
Amazon: there are disturbing and weird crossovers between them, like your MFA—but nevermind that. Every time you spin up a new AWS account you're New To Us and must be onboarded.
Apple: WTF is a business?!
Twitter: Your account is temporarily restricted.
Dropbox: Would either account be interested in some nonsense that has nothing to do with "a folder, synced everywhere?"
MongoDB: We lost both of your accounts. Oops.
Netflix: Between those two accounts, you currently have 40 profiles spread across all 6 continents we serve. This is... fine.
Oracle: We have no idea what a personal user account might be, but we're going to audit you just the same.
WebEx: Can we take you out to dinner? You're 40% of this quarter's net new sales.
OnlyFans: I'm sorry--did you say a business account? And you're not a sex worker? Can you please explain this to one of our product managers, because we're highly confused.
The IRS: We're going to audit the piss out of you just as soon as we can find an auditor who takes one look at this thread and doesn't quit on the spot.

More from Corey Quinn

More from Business

There are 100s of threads on building and running startups.

Here are 10 that are pure gold:

Fund-raising is hard for all of us.

@justinkan shares some unique insights on how to do it well.


We rarely hear honest reflections from founders on what they messed up.

@apartovi shares his reflections on a deal that went wrong with Steve Jobs.


Some gems in this thread by @agazdecki on a wide variety of founder


shares some solid principles learned from building a multi-billion dollar business.

You May Also Like

This is a pretty valiant attempt to defend the "Feminist Glaciology" article, which says conventional wisdom is wrong, and this is a solid piece of scholarship. I'll beg to differ, because I think Jeffery, here, is confusing scholarship with "saying things that seem right".


The article is, at heart, deeply weird, even essentialist. Here, for example, is the claim that proposing climate engineering is a "man" thing. Also a "man" thing: attempting to get distance from a topic, approaching it in a disinterested fashion.


Also a "man" thing—physical courage. (I guess, not quite: physical courage "co-constitutes" masculinist glaciology along with nationalism and colonialism.)


There's criticism of a New York Times article that talks about glaciology adventures, which makes a similar point.


At the heart of this chunk is the claim that glaciology excludes women because of a narrative of scientific objectivity and physical adventure. This is a strong claim! It's not enough to say, hey, sure, sounds good. Is it true?
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.