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.)
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:
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.)
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.
Just because you found an exception to a general pattern, you argued that the entire pattern is false.
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.
Just because you found an exception to a general pattern, you argued that the exception *is* the pattern.
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.
Just because you found one thing missing in a list of generally useful things, you argued that the entire list is useless.
Just because a thing worked for you, you argued that everyone should do that thing, all the time.
Just because a thing worked for Musk / Bezos / Jobs / [insert your idol], you argued that everyone should do that thing, all the time.
Just because a thing worked for you, you argued that no one should do the opposite of that thing, ever, under any circumstance.
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.
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.
More from Shreyas Doshi
(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
Breaking into PMing - a \U0001f9f5 // A question folks from eng/design/other functions often have how to become a PM in a tech co.
— Sriram Krishnan (@sriramk) April 14, 2020
It can seem non-obvious and differs with each company but here are some patterns I've seen work. All the below assumes you have no PMing on your resume.
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
There is no One Correct Way\u2122 to learn
— Shreyas Doshi (@shreyas) August 15, 2020
Don\u2019t feel pressured to read 70 books/year just becos Super-Successful Person X does that
Videos, Podcasts, Audiobooks, Discussions\u2014all are fine
What to do:
Understand your preferred learning style
Don't resist it, embrace it
Commit to it
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
A B2B Product Management Story: on discovering problems that customers actually care about
— Shreyas Doshi (@shreyas) March 28, 2021
Very visual story thread\U0001f447\U0001f3fe pic.twitter.com/SQKpmLtBGC
The 3 types / hats / modes of product
3 types of product leaders:
— Shreyas Doshi (@shreyas) March 26, 2021
1) The Operator
2) The Craftsperson
3) The Visionary
It is important for you as a startup founder or CEO, product manager, or a product leader to deeply understand these types, as you make decisions on whom to hire or whom to work for.
Thread\U0001f447\U0001f3fe
An extremely important observation about product
There are 3 levels to product work
— Shreyas Doshi (@shreyas) March 12, 2021
(1) The Execution level
(2) The Impact level
(3) The Optics level
When an individual & their team are fixated on different levels, often there is conflict.
E.g.
PM is fixated on (2), Team on (1)
PM on (3), Team on (2)
PM on (2), Team on (3)
A thread on getting work
How I like to plan my work:
— Shreyas Doshi (@shreyas) March 17, 2021
Limit meetings
\u21d2 Long scheduled work blocks
At end of the work day, plan next day
\u21d2 Easier to disconnect, be present
Fit the next day's tasks in calendar
\u21d2 Forces prioritizing
Plan next week on Friday evening
\u21d2 Go into weekend with a clear mind
You May Also Like
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:
I'm increasingly interested in the idea of "personal moats" in the context of careers.
— Erik Torenberg (@eriktorenberg) November 22, 2018
Moats should be:
- Hard to learn and hard to do (but perhaps easier for you)
- Skills that are rare and valuable
- Legible
- Compounding over time
- Unique to your own talents & interests https://t.co/bB3k1YcH5b
2/ Like a company moat, you want to build career capital while you sleep.
As Andrew Chen noted:
People talk about \u201cpassive income\u201d a lot but not about \u201cpassive social capital\u201d or \u201cpassive networking\u201d or \u201cpassive knowledge gaining\u201d but that\u2019s what you can architect if you have a thing and it grows over time without intensive constant effort to sustain it
— Andrew Chen (@andrewchen) November 22, 2018
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
Things that look like moats but likely aren\u2019t or may fade:
— Erik Torenberg (@eriktorenberg) November 22, 2018
- Proprietary networks
- Being something other than one of the best at any tournament style-game
- Many "awards"
- Twitter followers or general reach without "respect"
- Anything that depends on information asymmetry https://t.co/abjxesVIh9
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.
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.