Recent well liked threads

Sep 30, 2022
—— lies in marriage.

markhyuck alternative universe.
by— yayay.


Image
Image
Image
Image
⚠️ATTENTION⚠️ Image
Read 193 tweets
May 13, 2023
—— loving can hurt.
(lies in marriage bagian kedua)

markhyuck alternative universe.
written by yayay.


Image
Image
Image
Image
73. Gak mungkin Image
74. Let's meet again Image
Read 100 tweets
May 20, 2024
⚪️ Remember

All suspected cases of child abuse should be reported to
Child Protective Services.

Medical practitioners are obligated to report child abuse even if that means breaking patient-physician confidentiality.

🟢 Always notify Child Protective Services.
@threadreaderapp unroll
Read 2 tweets
Dec 3, 2025
Arsenal 2 : 0 Brentford

▪ xG: 2.22 - 0.55
▪ xThreat: 1.1 - 0.95
▪ Possession: 62.2% - 37.8%
▪ Field Tilt: 75.3% - 24.7%
▪ Def Action Height: 52.0 - 37.6

Donations ko-fi.com/markstatsImage
Image
Image
Image
Arsenal 2 : 0 Brentford

▪ Penbox shots: 10 - 5
▪ Deep Entries: 13 - 6
▪ Buildup completion: 83.2% - 75.3%
▪ PPDA: 7.3 - 14.1
▪ High turnovers: 5 - 0 Image
Image
Image
Image
Declan Rice vs. Brentford

Successful Passes: 44
Expected Threat: 0.2
Progression via pass: 3.91
Progression via carry: 2.13

Donations ko-fi.com/markstatsImage
Read 3 tweets
Jan 8
Arsenal 0 : 0 Liverpool

▪ xG: 1.0 - 0.28
▪ xThreat: 1.32 - 0.72
▪ Possession: 47.7% - 52.3%
▪ Field Tilt: 64.4% - 35.6%
▪ Def Action Height: 55.0 - 36.3

Donations ko-fi.com/markstatsImage
Image
Image
Image
Arsenal 0 : 0 Liverpool

▪ Penbox shots: 6 - 2
▪ Deep Entries: 15 - 3
▪ Buildup completion: 86.6% - 86.4%
▪ PPDA: 12.8 - 16.5
▪ High turnovers: 8 - 1 Image
Image
Image
Image
William Saliba vs. Liverpool

Successful Passes: 79
Expected Threat: 0.23
Progression via pass: 5.47
Progression via carry: 4.23

Donations ko-fi.com/markstatsImage
Read 3 tweets
Jan 30
Perplexity just replaced my entire research workflow.

No more opening 50 tabs. No more saving bookmarks. No more "where did I see that?"

Here are 10 Perplexity prompts that replaced my research tools: Image
1. Competitive Intelligence Dashboard

Prompt I use:

"
Create a competitive analysis for [COMPANY/PRODUCT] covering:

1. Recent product launches (last 90 days)
2. Pricing changes (with before/after if available)
3. Customer sentiment (Reddit, Twitter, G2 reviews - categorize positive/negative themes)
4. Technical stack (from job postings and tech blogs)
5. Funding/financial news (any recent rounds, partnerships, layoffs)

Format as a table:
| Category | Key Findings | Source Date | Impact Assessment |

Focus on information from the last 30 days. Cite every claim.
"
2. Technical Comparison Matrix

Prompt:

"
Compare [TOOL A] vs [TOOL B] vs [TOOL C] for [SPECIFIC USE CASE]:

Build a decision matrix:
| Feature | Tool A | Tool B | Tool C | Winner & Why |

Must include:
- Pricing (exact tiers, hidden costs)
- Performance benchmarks (from independent tests)
- Integration options (with [MY STACK])
- Community size (GitHub stars, Discord members, Stack Overflow activity)
- Recent updates (last 3 months)
- Known issues (from issue trackers, Reddit)

Rank overall winner with confidence score (1-10) and reasoning.

Cite every benchmark and review.
"
Read 15 tweets
Jan 30
Dr. Peter Attia & Dr. Rhonda Patrick recently unpacked one of the most misunderstood debates in longevity science.

After years of low- vs high-protein arguments, they explained what actually matters for living longer and staying functional.

Their 12 key insights: Image
1. Longevity science was built on animal models, and they misled us.

Most protein-restriction data comes from mice and worms.

They live in sterile environments.
No infections. No injuries. No hospital stays.

Humans don’t age like that. Image
2. Humans don’t die the way lab animals do.

Lab animals mostly die from:
• lymphomas
• artificial cancers

Humans mostly die from:
• heart disease
• dementia
• frailty
• falls
• loss of independence

Muscle loss matters far more in humans.
Read 16 tweets
Jan 31
Most people treat their iPhone camera like a point-and-shoot toy.

They’re carrying one of the best true pocket cameras and using about 50% of its potential.

Here are the settings you need to change to fix that:

Starting with the one that confuses nearly everyone…
1. STOP THE LENS SWITCH MADNESS

That jumping between lenses when you get close? That’s the auto macro control trying to "help."

Settings → Camera → Macro Control → ON

Now you control which lens you use when up close and personal.
2. THE ONE FOR THE PRO’S (THE PHONES NOT THE PEOPLE)

If you have Pro/Pro Max: Settings → Camera → Formats → Apple ProRAW → ON

This gives you the most flexible photos possible and stores the most
information in the photo. Now your edits will hold up better.
Read 8 tweets
Jan 31
🧵L’overtourism nei centri storici italiani e spagnoli.

Spiegato quasi solo con Airbnb/affitti brevi: affollamento, caro-affitti, snaturamento città. Disagi reali, ma narrazione mediatica che scherma cause strutturali più profonde e di lungo periodo.
Una cortina fumogena.→
Dati ufficiali (ISTAT, Nomisma, INE, Banco de España, ENAC 2025-26): affitti brevi = quota marginale.
In Italia ~1,3% dello stock abitativo totale (Nomisma 2024-2025), contro 13% case vuote o sottoutilizzate.
In Spagna ~1,4%.
NON sono la causa principale della crisi abitativa. →
Il VERO MOTORE?
Boom voli low-cost.
In Italia ENAC 2025: 63% passeggeri su low-cost (145 su 229 mln totali).
"democratizzazione" di viaggi prima impensabili.
Airbnb e c. ORGANIZZANO offerta GIÀ esistente (seconde case, eredità inutilizzate), NON la creano. Causa vs effetto. →
Read 19 tweets
Jan 31
I'm Boris and I created Claude Code. I wanted to quickly share a few tips for using Claude Code, sourced directly from the Claude Code team. The way the team uses Claude is different than how I use it. Remember: there is no one right way to use Claude Code -- everyones' setup is different. You should experiment to see what works for you!
1. Do more in parallel

Spin up 3–5 git worktrees at once, each running its own Claude session in parallel. It's the single biggest productivity unlock, and the top tip from the team. Personally, I use multiple git checkouts, but most of the Claude Code team prefers worktrees -- it's the reason @amorriscode built native support for them into the Claude Desktop app!

Some people also name their worktrees and set up shell aliases (za, zb, zc) so they can hop between them in one keystroke. Others have a dedicated "analysis" worktree that's only for reading logs and running BigQuery

See code.claude.com/docs/en/common…Image
2. Start every complex task in plan mode. Pour your energy into the plan so Claude can 1-shot the implementation.

One person has one Claude write the plan, then they spin up a second Claude to review it as a staff engineer.

Another says the moment something goes sideways, they switch back to plan mode and re-plan. Don't keep pushing. They also explicitly tell Claude to enter plan mode for verification steps, not just for the buildImage
Read 12 tweets