Omer Bahari

CTO @ampfitness

[Omer Bahari @omerbahari]

GREAT EPISODE - https://t.co/wqowLXhbyO

[Omer Bahari @omerbahari]

@Nerdi_Yogi's episode with @lennysan runs through the unsolved problems of building software this way- context-switching, culture, and the one I keep thinking about: how do you actually measure AI efficiency for developers? Tokens? Lines of code? Value?

[Omer Bahari @omerbahari]

The tension worth watching: what AI lets you build vs. what it costs to run.
Most teams are only looking at the first half

[Omer Bahari @omerbahari]

Full breakdown- three stories from inside amp, including one that didn't work: https://t.co/rfBAts1hfG

[Omer Bahari @omerbahari]

Telling people to use more AI is like telling them to be more creative.

Real AI-first mindset. Five steps. Most companies skip step 1- then blame the team when nothing happens.

[Omer Bahari @omerbahari]

No tool purchase. No mandate. No "AI Center of Excellence." If your AI strategy has a maturity model, you don't have a strategy. You have a slide. The hard part was never the AI. It's the discipline to not roll anything out until step 4 is real

[Ryo Lu @ryolu_]

the old way of scaling teams is dead:

we used to hire specialists – designers, engineers, PMs – each in their lane, scaling by adding more people. but when Cursor can take you from idea to code in minutes, execution isn't the bottleneck anymore. taste and judgment are.

what matters now: people who can see the full stack, move between layers, but specialize deeply in something AI can't replicate yet. T-shaped but way wider – conversant across domains, expert in one thing.

AI doesn't just make you faster. it ties teams together differently. no more waterfall – designer codes the prototype, engineer extends it, both work in the same medium. the gap between disciplines disappears.

this raises individual ceilings. i'm a designer who built ryOS entirely in Cursor – couldn't have done that before. but i'm not replacing engineers, i'm just removing execution barriers while keeping my design taste and systems thinking.

you're not hiring for roles anymore. you're hiring for breadth + depth, taste, systems thinking, learning velocity. 5 people who can work across code/design/product beat 20 specialists coordinating handoffs.

the new bottlenecks are deeply human: taste, vision, judgment, context. AI explores options, but can't tell you which is right. that's where specialization matters now – in judgment, not execution.

small teams, fluid boundaries, everyone working in the same tools. roles still matter but as overlapping concerns with different depths, not separate silos. tools handle execution, you handle vision.

this is what we're building at Cursor – closing the gap between idea and reality. so your taste becomes the main thing, and teams have more freedom to explore crazy ideas.

[Omer Bahari @omerbahari]

just the tip of the iceberg for leveraging Claude Code. Anthropic’s internal write‑up (for inspiration): https://t.co/DEvhhKMON2
Bonus read: https://t.co/rTSbYrzaM6
If this helped, share your own setups & tips. ❤️

[Omer Bahari @omerbahari]

Sharing a thread of messages I wrote to my team a few months ago—A friend convinced me it might be useful to more people here and still relevant. If you use Claude Code, this is for you. 🧵👇

[Omer Bahari @omerbahari]

10/11
For the brave: YOLO mode with --dangerously-skip-permissions runs without asking for confirmations. Use at your own risk—I’m not responsible.