Paul Tiberghien
2 followers · 1 following · 1052 views
on the atlas — 51
- Do Things that Don't Scale13 savers
- You don’t need “A Players” to build a great startup. You need people with something to prove1 savers
- Paul's Bookshelf / Curius1 savers
- Gumloop | Handbook1 savers
- How to do distributed locking — Martin Kleppmann’s blog3 savers
- How We Solved the Thundering Herd Problem | by Antross | The PayPal Technology Blog | Medium1 savers
- The data model behind Notion's flexibility6 savers
- Two Years of Telepathy | Updates | Neuralink3 savers
- Your lifetime earnings are probably determined in your 20s - The Washington Post1 savers
- How To 2D Track Creatively in After Effects | Tutorial - YouTube1 savers
- Active-Active for Multi-Regional Resiliency | by Netflix Technology Blog | Netflix TechBlog1 savers
- Love in the time of Linklater - by Keane Moraes1 savers
- Tao of Node - Design, Architecture & Best Practices | Alex Kondov - Software Engineer1 savers
- Exceptional Junior SWE | Mercor1 savers
- in defense of pretension. - by ayan artan - rent free.2 savers
- 12 Rules for Learning Foreign Languages in Record Time - The Only Post You'll Ever Need - The Blog of Author Tim Ferriss2 savers
- Make Something Heavy - by Anu - Working Theorys17 savers
- 5 things I learned from 5 years at Vercel | Lee Robinson4 savers
- Gmail110 savers
- The Art of Letting Bad Things Happen (and Weapons of Mass Distraction) - The Blog of Author Tim Ferriss1 savers
- Sign Up | LinkedIn24 savers
- UBC Course Scheduler1 savers
- The Fruits of Friendship - David Perell7 savers
- Learn to Sell, Learn to Build2 savers
- The Trouble with Optionality | Opinion | The Harvard Crimson27 savers
- A Brief History & Ethos of the Digital Garden31 savers
- Best time to post on social media: Q1 2025 update1 savers
- The Curve is Bending1 savers
- What to Do12 savers
- So Good They Can't Ignore You: Why Skills Trump Passion in the Quest for Work You Love1 savers
- Looking for Alice - by Henrik Karlsson - Escaping Flatland92 savers
- How to Do Great Work68 savers
- A blog post is a very long and complex search query to find fascinating people and make them route interesting stuff to your inbox67 savers
- AI 202755 savers
- Dario Amodei — The Adolescence of Technology44 savers
- Sometimes the reason you can’t find people you resonate with is because you misread the ones you meet32 savers
- So you wanna de-bog yourself - by Adam Mastroianni24 savers
- Advice on Upskilling - Justin Skycak24 savers
- Hugging the X-Axis - David Perell16 savers
- How to Earn a Billion Dollars11 savers
- The Bus Ticket Theory of Genius11 savers
- ‘Give Away Your Legos’ and Other Commandments for Scaling Startups | First Round Review9 savers
- The Wrong Abstraction — Sandi Metz8 savers
- The Marriage Decision: Everything Forever or Nothing Ever Again8 savers
- Why Figma Wins - kwokchain7 savers
- What if Love never finds you?6 savers
- Inside Stripe’s Engineering Culture - Part 14 savers
- One Big Idea - David Perell3 savers
- The Huggingface Incident - by Scott Alexander2 savers
- Inside Stripe’s Engineering Culture: Part 22 savers
- How to Build Wealth as a Career Person – Asher's Blog2 savers
highlights — 162
he showed us what it looks like to be gloriously, courageously and impossibly alive
He Wasn't Chasing Mountains - by Hassan KhanNims Purja died doing the thing that made him feel most completely alive.
He Wasn't Chasing Mountains - by Hassan Khannothing left except pure participation in reality
He Wasn't Chasing Mountains - by Hassan KhanHe climbed them chasing a version of himself that didn’t exist anywhere else, one that only surfaced when complete commitment met immense consequence.
He Wasn't Chasing Mountains - by Hassan KhanThe mountain demands everything. And in demanding everything, it gives something phenomenal back. It gives them a mind with nowhere else to be.
He Wasn't Chasing Mountains - by Hassan KhanWhen the stakes become genuinely meaningful, your brain can no longer afford distraction.
He Wasn't Chasing Mountains - by Hassan KhanOne of the strongest triggers of flow is consequence.
He Wasn't Chasing Mountains - by Hassan KhanThe reward wasn’t waiting at the end, it was hidden inside the doing itself.
He Wasn't Chasing Mountains - by Hassan KhanThey spoke of attention becoming so complete that the rest of the world just disappeared
He Wasn't Chasing Mountains - by Hassan KhanNims spent his life trying to convince us that our limits are rarely as fixed as we believe they are.
He Wasn't Chasing Mountains - by Hassan KhanDeath is an accepted part of the bargain in high altitude mountaineering
He Wasn't Chasing Mountains - by Hassan KhanBy flying at a sufficiently high altitude at an appropriate speed for current atmospheric conditions, Overture’s sonic boom never reaches the ground.
FAQ | Boom Supersonic100% sustainable aviation fuel (SAF)
FAQ | Boom SupersonicWe believe that life is better lived in person. Our mission at Boom is to make the world dramatically more accessible
FAQ | Boom SupersonicThink of credibility as points you can spend or lose.
The Definitive Guide to Forward Deployed EngineeringLearn to make requests that explain the why, not just the what.
The Definitive Guide to Forward Deployed EngineeringStaying calm is about preparation and repetition
The Definitive Guide to Forward Deployed EngineeringCommunication is a muscle you have to exercise.
The Definitive Guide to Forward Deployed EngineeringHow you handle a crisis matters as much as whether you fix it.
The Definitive Guide to Forward Deployed EngineeringThey know when to build a robust system and when to write a script that just works.
The Definitive Guide to Forward Deployed Engineeringthey become users before they become builders
The Definitive Guide to Forward Deployed EngineeringFDEs is that they’re the best source of product insight.
The Definitive Guide to Forward Deployed Engineeringit never gets properly deployed, configured, adopted, and integrated into customer workflows.
The Definitive Guide to Forward Deployed Engineeringsoftware that actually gets adopted is worth infinitely more than software that sits on a shelf.
The Definitive Guide to Forward Deployed EngineeringAn FDE is a software engineer who owns customer outcomes.
The Definitive Guide to Forward Deployed EngineeringThere's a more extreme variant where you don't just use your software, but are your software. When you only have a small number of users, you can sometimes get away with doing by hand things that you plan to automate later. This lets you launch faster, and when you do finally automate yourself out of the loop, you'll know exactly what to build because you'll have muscle memory from doing it yourself.
Do Things that Don't ScaleSome of your earliest, best people, the ones who built what you have, wouldn’t pass the screening process you have in place today.
You don’t need “A Players” to build a great startup. You need people with something to proveThings exist because of them.
You don’t need “A Players” to build a great startup. You need people with something to proveWhat does exceptional look like in this role?
You don’t need “A Players” to build a great startup. You need people with something to proveIn hiring, System 1 is almost always running the show. You form a quick impression and then spend the rest of the interview unconsciously trying to confirm it.
You don’t need “A Players” to build a great startup. You need people with something to proveStartups as weak situations
You don’t need “A Players” to build a great startup. You need people with something to prove(affinity bias is the no.1 watchout I personally have to look out for when I’m hiring
You don’t need “A Players” to build a great startup. You need people with something to prove“Something to prove” has a research base
You don’t need “A Players” to build a great startup. You need people with something to proveThey had something to prove.
You don’t need “A Players” to build a great startup. You need people with something to proveIt either exists in the person when they walk through the door, or it doesn’t.
You don’t need “A Players” to build a great startup. You need people with something to proveUnderneath the language, founders are rarely trying to hire for raw capability. They’re trying to hire for motivation.
You don’t need “A Players” to build a great startup. You need people with something to provePerformance is contextual.
You don’t need “A Players” to build a great startup. You need people with something to proveMoving faster and caring more is how we win.
Gumloop | HandbookEverything from loading animations, to keyboard shortcuts, to notification emails matter.
Gumloop | HandbookWe want Gumloop to be such an outstanding product that marketing is an afterthought.
Gumloop | HandbookAlmost every existing business has massive inefficiencies
Gumloop | HandbookWe want to enable every non technical person in a company to solve their own problems without needing to loop in a technical team.
Gumloop | Handbookyou need to include a fencing token with every write request to the storage service.
How to do distributed locking — Martin Kleppmann’s blogThis means that an application process may send a write request, and it may reach the storage server a minute later when the lease has already expired.
How to do distributed locking — Martin Kleppmann’s blogthere are many other reasons why your process might get paused.
How to do distributed locking — Martin Kleppmann’s blogRemember that GC can pause a running thread at any point, including the point that is maximally inconvenient for you (between the last check and the write operation).
How to do distributed locking — Martin Kleppmann’s blogThe lock has a timeout (i.e. it is a lease), which is always a good idea (otherwise a crashed client could end up holding a lock forever and never releasing it)
How to do distributed locking — Martin Kleppmann’s blogIt’s important to remember that a lock in a distributed system is not like a mutex in a multi-threaded application
How to do distributed locking — Martin Kleppmann’s blogwill argue that if you are using locks merely for efficiency purposes, it is unnecessary to incur the cost and complexity of Redlock,
How to do distributed locking — Martin Kleppmann’s blogDuring pre-launch testing, we discovered the Agent was too ambitious
The Crux of Every AI System: Evaluations | WHOOP Engineering