Jérémy Dagorn 👨🏻‍💻

@KyleAsay_ Could not ring more true. Any leaders using sentences like: “make it easy for me”, “don’t create more work for me” while they pretend to know everything about “the agentic revolution” is not to be taken seriously.

If you can’t share honest feedback with your “skip-level” then your skip is a terrible leader If you ever work in an org led by someone that thinks “I don’t want to listen to people if it creates more work for me” do everything you can to get away from that org. And if the company doesn’t fire that VP within a few months do all you can to get away from that company - it’s full of politicians masquerading as managers and will certainly fail while every VP points at someone else

The @claude code Pro limit are so low. If I have Codex and Claude already, Codex is definitely better for longer usage.

2021: I have 2 years of experience and I demand to be an VP Engineering. I am invincible. 2026: I have 20 years of experience and would like to be demoted from principal engineer to junior engineer. I just want to be the most over performing person in my role. I just want to blend in.

my agents when I hit build after a 40 minute plan mode

AMEN x10

Someone at CashApp saw their friends get laid off and they didnt and she screamed fuck that...and she let the choppa sing on Linkedin. More of this.

That rings true.

24% of execs are firing people based on AI they don't even understand The other 76% are lying about understanding it These are the same geniuses who thought the metaverse was the future Now they're axing entire teams because ChatGPT wrote them a haiku Meanwhile the laid-off developers are updating LinkedIn with "Open to Work" frames Like anyone's hiring overpaid code monkeys who got replaced by a chatbot "But I have 8 years of React experience!" Cool story bro, GPT learned it in 8 seconds Amazon and Meta cleaning house while their remaining employees panic-learn prompt engineering Nothing funnier than watching tech bros realize they're not the main character Just expensive NPCs in someone else's automation story

@nurijanian This rings so true. If you want real collaboration, work on the how and what together with Eng. don’t try to do too much.

5/ The reality is: good PRDs are conversation starters, not specification documents I learned this after 6 months of writing 20-page specs that no one read (If you want to see examples of good PRDs, I collected 25+ ready-made PRDs at tiny.cc/prd-world)

Confession: I spent my first 6 months as a PM writing PRDs like I was still in engineering school. The team smiled in meetings and ignored everything I wrote. Then I learned the one shift that got my docs read and features shipped. It took me 6 months. You’ll learn it in 3…

Software engineers: Context switching kills productivity. Also software engineers: I'm now managing 19 AI agents and doing 1800 commits a day. We’ve spent years complaining that managers who expect a quick 5-minute chat ruin our focus for the next hour. But a ping from an agent every few minutes, that’s ok? We celebrated Paul Graham’s essay “Maker’s Schedule, Manager’s Schedule” in which he argued: “When you're operating on the maker's schedule, meetings are a disaster. A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in.” Now we see software engineers claiming huge productivity gains from hordes of AI agents, celebrating thousands of commits per day from their 19 agents. Either context switching was never really the problem, and we oversold our need for deep focus. Or we're not actually reviewing 1800 commits a day. If we couldn't context switch before, we're not managing 19 agents. We're blindly trusting them. That’s not engineering, it’s gambling.

Of course that's your contention. You're a first-time SaaS bear. You just got finished listening to some podcast, Dario on Dwarkesh, probably. Now you think it’s the end of white collar work and seat-based pricing is screwed. You're gonna be convinced of that til tomorrow when you get to “Something Big is Happening”. Then you’ll install ClawdBot on a Mac Mini, vibe code a dashboard on top of a postgres database and say we’re all just a couple ralph loops away from building a Salesforce competitor. That’s gonna last until next week when you discover context graphs, and then you're gonna be talking about how the systems of record will be disintermediated by an agentic layer and reposting OAI marketing graphics. “Well, as a matter of fact, I won't, because ultimately the application layer is just ….” The application layer is just business logic on top a CRUD database. You got that from Satya’s appearance on the BG2 pod, December 2024, right? Yeah, I saw that too. Were you gonna plagiarize the whole thing for us? Do you have any thoughts of your own on this matter? Or...is that your thing? You get into the replies of anyone posting a SaaS ticker. You watch some podcast and then pawn it off as your own idea just to impress some VCs and embarrass some anon who’s long SaaS? See the sad thing about a guy like you is in a couple years you're gonna start doing some thinking on your own and you're gonna come up with the fact that there are two certainties in life. One: don't do that. And two: you dropped thirty grand on Mac Minis and LLM API calls to come to the same conclusion you could’ve got for free by following a handful of VC accounts.

One thing that is clear when using an agent to code is that it will choose the wrong tool or library by default: react-test-renderer? Enzyme? Come on.

@thdxr I see people spending 5k a day on tokens.

if you manage a team how would you feel in a scenario where the weakest member is spending the most on LLMs like they're spending $2k a month or something

The AI spend per employee isn’t going to be sustainable Something has to give, either 1. Models get drastically cheaper 2. Companies start asking for results to justify the spend, so not everybody gets full access 3. Or they reduce their headcount

everyone's talking about their teams like they were at the peak of efficiency and bottlenecked by ability to produce code here's what things actually look like - your org rarely has good ideas. ideas being expensive to implement was actually helping - majority of workers have no reason to be super motivated, they want to do their 9-5 and get back to their life - they're not using AI to be 10x more effective they're using it to churn out their tasks with less energy spend - the 2 people on your team that actually tried are now flattened by the slop code everyone is producing, they will quit soon - even when you produce work faster you're still bottlenecked by bureaucracy and the dozen other realities of shipping something real - your CFO is like what do you mean each engineer now costs $2000 extra per month in LLM bills

Tech Twitter is now just AI every hour of the day I’m so fucking bored

DING DING DING

I installed Claude code this morning and I am now a billionaire.

Ouch.

Every freaking year. Go join Broncos but man it’s heartbreaking. I lost 5 dollars on my first sport bet too. I even wore my Bills beanie!