A surprisingly high % of stupid arguments & fights on Twitter are rooted in a tiny number of fairly obvious fallacies.

Stupid arguments & the fallacies that feed them, a thread:

Fallacy 1/

Just because it’s true that all squares are rectangles, you argued that all rectangles must be squares. (And you did it with so much swagger.)
Example of Fallacy 1

X says: Successful people aren’t afraid of hard work.

Y argues: That’s BS. I work 90 hours a week at Tech Co and am still stuck in this dead-end job.
Fallacy 2/

Just because you found an exception to a general pattern, you argued that the entire pattern is false.
Example of Fallacy 2

X says: Venture capital is useful for startups.

Y argues: Not true. Foo’s startup took VC money and they crashed & burned.

Z piles on: I agree with Y. In fact, Bar’s startup did not take VC money and it’s worth a bajillion.
Fallacy 2′/

Just because you found an exception to a general pattern, you argued that the exception *is* the pattern.
(further examples are left as an exercise for the reader)
Fallacy 3/

Just because you did not agree with one small aspect of what someone said, you argued that it makes sense to ignore everything they said.
Fallacy 4/

Just because you found one thing missing in a list of generally useful things, you argued that the entire list is useless.
Fallacy 5/

Just because a thing worked for you, you argued that everyone should do that thing, all the time.
Fallacy 5′/

Just because a thing worked for Musk / Bezos / Jobs / [insert your idol], you argued that everyone should do that thing, all the time.
Fallacy 6/

Just because a thing worked for you, you argued that no one should do the opposite of that thing, ever, under any circumstance.
Fallacy 6′/

Just because a thing worked for Musk / Bezos / Jobs / [insert your idol], you argued that no one should do the opposite of that thing, ever, under any circumstance.
Fallacy 7/

Just because a good idea wouldn’t work if “everyone did it”, you argued that it is in fact a terrible idea and *no one* should do it.
While this thread won't solve any of the bad faith conversations that unfortunately happen on Twitter, I hope it can help prevent some of the good faith conversations from taking a stupid turn.
Did I miss any other fallacies?

More from Shreyas Doshi

A thread of resources for aspiring & new Product Managers:

(should also be useful for Eng, Design, Data Science, Mktg, Ops folks who want to get better at PM work or want to build more empathy for your PM friends ☺️)

(oh, and pls also share *your* favorite resources below)

👇🏾

1/

Product Management - Start Here by @cagan
(hard to go wrong if you start with Marty Cagan’s

2/

Tips for Breaking into PM by @sriramk
(I’ve recommended this thread in my DMs more often than any other thread, by a pretty wide


3/

Top 100 Product Management Resources by @sachinrekhi
(well-categorized index so you can focus on whatever’s most useful right

4/

Brief interruption.

It’s important to understand your preferred learning style and go all in on that learning style (vs. struggling / procrastinating as you force a non-preferred learning
🗓️Recap of March 2021 content

Includes:
Solve THE problem
3 types of product leaders
Levels of product work
Getting work done
“I don’t know”
Good people, bad managers
Customer segmentation
LinkedIn Envy
On communication
Important definitions
Life-changing books
& much more..

👇🏾

A story that often plays out when we are not rigorous enough about the importance of the customer problem our product


The 3 types / hats / modes of product


An extremely important observation about product


A thread on getting work

You May Also Like

1/ Some initial thoughts on personal moats:

Like company moats, your personal moat should be a competitive advantage that is not only durable—it should also compound over time.

Characteristics of a personal moat below:


2/ Like a company moat, you want to build career capital while you sleep.

As Andrew Chen noted:


3/ You don’t want to build a competitive advantage that is fleeting or that will get commoditized

Things that might get commoditized over time (some longer than


4/ Before the arrival of recorded music, what used to be scarce was the actual music itself — required an in-person artist.

After recorded music, the music itself became abundant and what became scarce was curation, distribution, and self space.

5/ Similarly, in careers, what used to be (more) scarce were things like ideas, money, and exclusive relationships.

In the internet economy, what has become scarce are things like specific knowledge, rare & valuable skills, and great reputations.
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.