Ryan

14 posts

Ryan banner
Ryan

Ryan

@ryanstp_

Building @elise_ai • VP Engineering

انضم Nisan 2026
21 يتبع10 المتابعون
pdawg
pdawg@prathamgrv·
this is by far my favourite tweet of all time
pdawg tweet media
English
48
297
4.4K
146.4K
Ryan
Ryan@ryanstp_·
@forgebitz what's the thinking here? agree that ive seen non-tech folk be intimidated w the CLI right now, but i think over time CLI and chat will just kind of merge into the same thing?
English
0
0
1
113
Klaas
Klaas@forgebitz·
as much as i like the cli don't think it the future for most people's work
English
56
2
85
9.1K
Ryan
Ryan@ryanstp_·
@icanvardar this has to be rage bait right? still believe taste is important and hard to come-by but FE has validation & feedback build-in natively (the browser) which makes the feedback loop for the model sm easier
English
0
0
1
272
Can Vardar
Can Vardar@icanvardar·
frontend is so much harder than backend
English
71
1
147
21.6K
Ryan
Ryan@ryanstp_·
@lennysan @rabois posted about the takes on hiring but this hit hard too. seeing a ton of success on the product ops/implementation side too where the top person can basically own most of the client facing assets
English
0
0
1
93
Lenny Rachitsky
Lenny Rachitsky@lennysan·
.@rabois: "I've noticed that in some of the best organizations, the number one consumer of tokens is the CMO."
Lenny Rachitsky@lennysan

"High performance machines don't have psychological safety. They're about winning." Keith Rabois (@rabois) was COO of Square, part of the PayPal Mafia, an early investor in Stripe, Palantir, Airbnb, DoorDash, and Ramp, and a 2x founder. He's spent 25 years obsessing over how to build world-class teams. In our in-depth conversation, we discuss: 🔸 How to identify undiscovered talent 🔸 Keith's barrels vs. ammunition hiring framework 🔸 The three traits of the best-performing companies right now 🔸 Why talking to customers is actively harmful for consumer products 🔸 Why the PM role is dying 🔸 The specific interview question he asks every senior candidate 🔸 Why CMOs (not engineers) are becoming the #1 consumer of AI tokens Watch now 👇 youtu.be/xCd9ykretlg

English
11
2
44
23K
Ryan
Ryan@ryanstp_·
most underrated skill is ability to write a plan with _just_ the right amount of info. even more valuable now that with ai that person can genuinely just plan everything lol
a16z@a16z

.@pmarca: "The person who writes down the thing has tremendous power." "There are so few people who will just like write down the thing. And so we see this at companies all the time, which is, one of the ways you find the up-and-comers at a tech company is just, okay, who wrote down the plan? And, you know, that doesn't mean they came up with everything. And that doesn't mean that they had all the ideas, but they're actually able to organize their thoughts and then actually have the energy and the motivation and the skill to be able to communicate in a written form. That actually stands out." With @david_perell

English
1
0
3
64
Hesse Philosophy
Hesse Philosophy@HermannHessed·
“The future is already here – it's just not evenly distributed.” ―William Gibson
Hesse Philosophy tweet media
English
5
38
168
5.2K
Ryan
Ryan@ryanstp_·
.@rabois on @lennysan - essential listening for all eng leaders, especially on hiring & talent. my favorite: ask candidates what their company should do differently, then immediately ask what they did about it. top people have opinions and act on them. especially as AI makes builders w business acumen even more valuable!
Lenny Rachitsky@lennysan

My biggest takeaways from @rabois: 1. The team you build is the company you build. Founders get distracted by markets, customers, and technology. If you have the right people, those problems get easier. If you have the wrong people, none of those things save you. 2. Build your company on undiscovered talent. The only way to scale an organization against incumbents with infinite budgets is to find talent that large companies’ hiring machines will misprocess. In practice, this often means skewing younger—not because young people are inherently better but because they have fewer data points, which means typical evaluation systems can’t categorize them accurately. This is where the alpha often is. 3. Hire more “barrels,” not “ammunition.” A “barrel” is someone who can take an idea from zero to outcome without hand-holding. Most companies have only a handful of these people. Hiring more people without expanding the number of barrels doesn’t increase output; it increases coordination tax and creates drag. The ratio of barrels to ammunition is what determines the number of important things a company can pursue simultaneously. 4. CMOs are becoming the #1 consumer of AI tokens. At a few of Keith’s top portfolio companies, the heaviest user of AI is the chief marketing officer. These CMOs are running analytics, shipping campaigns, and generating insights that previously required entire teams of deputies. 5. The three signs a company will win: operating tempo, internal talent development, and “the relentless application of force” from the top. Keith identifies a consistent pattern across his best portfolio companies. First, operating tempo: Ramp shipped physical cards in three months when the industry standard was 9 to 12. Second, talent development through internal promotion rather than senior external hires; the CMO at one of his top companies was the previous chief of staff. Third, the CEO’s willingness to push harder as things improve, not less. Mike Moritz told a friend of Keith’s that the most common trait of the best CEOs is “the relentless application of force.” Complacency is the natural by-product of success, and the CEO’s job is to offset it. 6. For consumer products, talking to customers is not just unhelpful; it’s actively harmful. Keith refuses to let companies he advises conduct consumer research. His argument: Consumer decisions are subconscious. Ask any Porsche owner why they bought the car, and 99% will cite every reason except the real one. Once misleading customer feedback enters the organization, it locks into people’s brains and distorts every subsequent decision. 7. Keith believes the PM role may not survive the AI era. Taking customer inputs, building a sequential year-long roadmap, and coordinating between teams are structurally incoherent when AI capabilities change weekly. The skill that matters now across all three roles—PM, designer, engineer—is business acumen: understanding the company’s equation and knowing what to build next. 8. Great hiring comes from great referencing. Run at least 20 references, and keep going until you hit negative feedback. Ask specific, forward-looking questions (e.g. “Would you start a company with them?”). If every reference is positive, you haven’t gone deep enough. 9. Use a 30-day feedback loop to sharpen your hiring instinct. Thirty days after every hire, ask: would I hire this person again? This is as predictive as waiting years, and dramatically faster for improving your judgment. Make this a habit, and your hiring quality will compound. 10. Criticize in public, not private—it optimizes for the system. Keith endorses a management practice that most people find confrontational: delivering negative feedback in front of the team, not behind closed doors. Private criticism optimizes for the individual, but the rest of the company doesn’t know the issue is being addressed, which breeds anxiety and suspicion. Public criticism lets colleagues see that leadership is aware, creates opportunities for others to volunteer help, and turns feedback into a team-building exercise. Full conversation: youtube.com/watch?v=xCd9yk…

English
0
0
4
84
Ryan
Ryan@ryanstp_·
@zackkanter this resonates. the opportunity cost of not working feels so high now, especially for the top people
English
0
0
2
673
Ryan
Ryan@ryanstp_·
@simonw strong agree. seeing the agents even better than humans at finding all the places a change touches (wide dependency search, cross-file reasoning) which is half the battle in a large system
English
0
0
0
1.6K
Simon Willison
Simon Willison@simonw·
Is there still a widespread belief that LLMs and coding agents are good for greenfield development but don't help for maintaining large existing codebases? I don't think that idea holds up any more
English
235
33
1K
151.6K
Ryan
Ryan@ryanstp_·
late to the party, but feel like the "S3 Files" update flew under the radar a bit. makes agent pipelines & remote dev work way simpler when everything just reads, writes the same filesystem
English
0
0
4
50
Ryan
Ryan@ryanstp_·
Had a colleague tell me ~3 months ago they didn’t use their IDE at all anymore. At the time I kind of rolled my eyes. Now, I haven't touched my IDE in 2 weeks. For me, the last remaining problem was “verification” and now I just have claude run the code and give my HTML reports verifying the output. Wild how fast we’re going from “yeah right” to “of course”
English
1
0
6
194
Ryan
Ryan@ryanstp_·
@cursor_ai computer use has changed the game. finding lot of helpful use cases on large prod system. I'm hitting ERR_INSUFFICIENT_RESOURCES on chrome like 50% of time. Sometimes the agent restarts the dev server and it fixes it, sometimes not. Any suggestions? plz help
English
1
0
2
42