➡️Founder and engineering leader ➡️25+ years in every part of the industry ➡️Sharing what I know to help you take control of your part Subscribe ⬇️

Joined November 2024
Thriving In Engineering retweeted
Milla Jovovich just shipped an open-source AI memory system that got 35k GitHub stars in days. github.com/milla-jovovich/me… She built it with Claude Code. "Everyone's a developer now" is not theoretical anymore
6
1
1
81
Thriving In Engineering retweeted
My biggest takeaways from @sherwinwu: 1. AI is writing virtually all code at OpenAI. 95% of the engineers use Codex, and engineers who embrace these tools open 70% more pull requests than their peers, and that gap is widening over time. 2. The role of a software engineer is shifting from writing code to managing fleets of AI agents. Many engineers now run 10 to 20 parallel Codex threads, steering and reviewing rather than writing code themselves. 3. The average PR code review time has dropped from 10-15 minutes per PR to 2-3 minutes. Every pull request at OpenAI is now reviewed by Codex before human eyes see it, and Codex surfaces suggestions and catches issues up front. This allows engineers to focus on more creative and strategic work while dramatically increasing productivity. 4. The models will eat your scaffolding for breakfast. When building AI products, don’t optimize for today’s model capabilities. The field is evolving so rapidly that the scaffolding (vector stores, agent frameworks, etc.) that seems essential today may be obsolete tomorrow as models improve. 5. Build for where the models are going, not where they are today. The most successful AI startups build products that work at 80% capability now, knowing the next model release will push them over the line. 6. Top performers become disproportionately more productive with AI tools. AI tools amplify the productivity of high-agency individuals, so the gap between top performers and everyone else is widening. The ROI on unblocking and empowering your best people compounds faster than ever in an AI-augmented environment. 7. Most enterprise AI deployments have negative ROI because they’re top-down mandates without bottom-up adoption. Success requires both executive buy-in and grassroots enthusiasm. Sherwin recommends creating a “tiger team” of technically-minded enthusiasts (often not engineers) who can explore capabilities, apply AI to specific workflows, and create excitement throughout the organization. 8. The one-person billion-dollar startup is coming, but with unexpected second-order effects. As AI makes individuals more productive, we’ll see not just billion-dollar solo founders but an explosion of small businesses: hundreds of $100M startups and tens of thousands of $10M startups. This will transform the startup ecosystem and venture capital landscape. 9. Business process automation is an underrated AI opportunity. While Silicon Valley focuses on knowledge work, most of the economy runs on repeatable business processes with standard operating procedures. There’s massive potential to apply AI to these workflows, which are often overlooked by the tech community. 10. The next two to three years will be the most exciting in tech history. After a relatively quiet period from 2015 to 2020, we’re now in an unprecedented era of innovation. Sherwin encourages everyone to engage with AI tools and not take this moment for granted, as the pace of change will eventually slow. 11. AI models will soon handle multi-hour tasks coherently. Today’s models are optimized for tasks that take minutes, but within 12 to 18 months we’ll see models that can work on complex tasks for upward of six hours. This will enable entirely new categories of products and workflows. 12. Audio is the next frontier for multimodal AI. While coding and text get most of the attention, audio is hugely underrated in business settings. Improvements in speech-to-speech models over the next 6 to 12 months will unlock significant new capabilities for business communication and operations.
"Engineers are becoming sorcerers" @SherwinWu leads engineering for @OpenAI’s API platform, which gives him a unique view into what’s going, where things are heading, and what the future of software engineering looks like. Over 95% of engineers at OpenAI use Codex daily, each works with a fleet of 10-20 parallel AI agents, and he's seeing the productivity gap between AI power users and everyone else widening. In our conversation, discuss: 🔸 Why the next 12-24 months are a rare window of opportunity 🔸 Why “models will eat your scaffolding for breakfast” 🔸 What OpenAI did to cut code review times from 10mins to 2mins 🔸 How AI is starting to change the role of managers 🔸 Why most enterprise AI deployments have negative ROI Watch below and find it on YouTube here 👇 youtu.be/B26CwKm5C1k
85
239
47
1,774
440,022
Thriving In Engineering retweeted
I'm telling you: GitHub's biggest competitor will soon be Cursor Cursor playing chess, everyone else busy with checkers (disclaimer: I am [was?] an investor in Graphite. Clearly the best AI code review + stacked diffs + PR workflow team and amazing team!)
Graphite is joining Cursor. We started Graphite to reimagine collaborative software development. Partnering with Cursor brings that future into focus faster than ever.
82
66
13
2,076
287,857
Thriving In Engineering retweeted
My top takeaways from executive coach @RNiederman: 1. The biggest skill gap in new leaders is knowing when to coach vs. when to tell people what to do. When you constantly provide answers, you train your team to bring you every problem instead of building their own problem-solving skills. The people you hire are experts in their domain—ask curious questions to help them reach their own solutions, which makes them more motivated and capable. Save direct advice for urgent situations or when someone genuinely lacks the necessary skills. 2. Use these four questions to coach someone to figure out the answer or themselves: When someone brings you a problem, use GROW: Goal, Reality, Options, and Way forward. Ask about their desired goal (what does success look like?), their current reality (where are you stuck?), possible options for a path forward (what could you do next?), and a concrete way forward (what will you actually do next?). These questions help people discover solutions they already have the context to find. You don’t need to follow this exact order; just use whichever type fits the moment. 3. In conflict, aim for mutual understanding, not proving you’re right. When you enter a difficult conversation trying to convince someone they’re wrong, they become defensive and armor up. Instead, focus on helping the other person understand your experience so they can empathize and see clearly what’s happening. This shift from convincing to connecting creates space for genuine dialogue where both people can be heard and find solutions together. 4. Burnout happens when you spend too much time outside your natural strengths, not just from working too hard. For two weeks, write down the five things each day that energized you most and the five that drained you most. Look for patterns. People burn out not just from working hard but from spending too much time doing things that deplete them—even if they’re good at those things. 5. Aim to spend 80% of your time in work that uses your natural gifts. Everyone will always have 20% of tasks they don’t enjoy, but this ratio creates sustainable energy. Design your role so that 80% plays to your strengths—this might mean delegating differently, hiring to complement your weaknesses, or even moving horizontally in your career rather than always climbing upward. It’s your responsibility to navigate your career toward your gifts, not your manager’s job to make your work interesting. 6. Co-founder relationships need scheduled maintenance time, like marriages. Sixty-five percent of startups fail because of co-founder conflict, not business problems. Set up regular check-ins—weekly touch-bases, monthly lunches, quarterly in-person reviews—to ask: How is this working for you? Are we aligned on vision and strategy? What am I doing that frustrates you? What’s gone unsaid? Without dedicated time, you’ll stay too busy to address problems before they become crises. 7. Use this four-step framework for difficult conversations: Observations, Feelings, Needs, Requests. Start with factual observations anyone could verify (not interpretations). Share your feelings without blame (I felt anxious, confused, disconnected—not “I feel like you. . .”). Name your underlying human needs (clarity, collaboration, connection). Make a small, achievable request the other person can actually fulfill. Stay on your side of the net—talk about your experience, not what you assume about them. This lets you be bold without triggering defensiveness. 8. Always ask yourself how you’re contributing to any conflict, even when the other person seems completely at fault. Leaders in conflict typically fall into three unhelpful patterns: playing victim (this is happening to me), blaming others (this is all their fault), or playing hero (I’ll just do it myself). Instead, ask yourself: How am I complicit in creating conditions I claim I don’t want? Taking responsibility for your part—while maintaining humility and curiosity—opens the door to actual resolution instead of endless frustration. 9. Ask yourself, “Would I enthusiastically rehire this person for the same role?” This binary question immediately reveals whether someone is right for their position. If the answer is no, you need to take action—whether that’s coaching, moving them to a different role, or helping them transition out. Your immediate gut reaction to this question tells you the truth you may be avoiding. If you wouldn’t enthusiastically rehire them, no amount of difficult conversations will likely fix the fundamental mismatch. 10. Active listening takes less than a minute to do but creates powerful change. Level 1 listening is internal listening: listening to your own thoughts. Level 2 is focused listening: you can repeat back what someone said. Level 3 is global listening: you notice body language, tone, and emotions beneath the words and can reflect back insights the person isn’t fully aware of. When you reflect back both what someone said and what you sensed they were feeling, they feel truly seen.
🎧 Watch me do a live coaching session with Rachel Lockett (@rniederman), executive coach and former leader at @Stripe and @Pinterest. We discuss: 🔸 When to coach and when to just tell people what to do 🔸 The GROW technique for helping people figure out a solution for themselves 🔸 Techniques for making difficult conversations less difficult 🔸 Avoiding burnout and designing a more energizing career 🔸 Building and sustaining a healthy co-founder relationship 🔸 Why you should ask, “Would I enthusiastically rehire this person?” to clarify talent decisions Listen now 👇 • YouTube: youtu.be/1GDVum5IarI • Spotify: open.spotify.com/episode/44N… • Apple: podcasts.apple.com/us/podcas… Thank you to our wonderful sponsors for supporting the podcast: 🏆 @stripe — Helping companies of all sizes grow revenue: stripe.com/ 🏆 @TrustVanta — Automate compliance. Simplify security: vanta.com/lenny 🏆 @withpersona — A global leader in digital identity verification: withpersona.com/lenny
13
38
1
323
48,926
Thriving In Engineering retweeted
Find the simplest thing that works.
88
368
45
2,645
178,856
Thriving In Engineering retweeted
Terrible leadership advice: "Hire great people and get out of their way." It’s doesn’t pass the Pro Sports Test. If this was a winning strategy, player-coaches would still be a thing. Some club would have saved millions on all those extra coaches and poured it into slightly better talent. But teams needs to be led. Even all star alpha dog athletes like Messi and Ronaldo have a coach. In fact, they have many. They need to be pushed, challenged to stretch beyond what’s comfortable. They need someone watching with a discerning eye and helping them see their blind spots. They need someone who’ll make things go around them so they can focus on what they’re best at. They need to be recruited into a system that uniquely leverages their strengths and coordinates the strengths of others around them into a winning competitive advantage. So no, you can’t just “get out of their way.” And now managers are under attack. Especially in big tech. But managers aren’t getting cut because they don’t play a vital role. They’re getting cut out because they forgot why their role exists. They got distracted - many times by enforcing the misguided policies created by the same company now firing them (but that's a different post) - and they stopped doing the hard work of elevating the performance of their team. That's the job: Make everyone better. They’re getting cut because they stopped leading. The leaders I work with, I want them to stay in the way. They do it intentionally. Here's how: 1. Set (and Hold) High Standards Great people don't want easy. They want to be pushed toward excellence. Your job isn't to accept their best work. It's to show them what their best could be. • Define what excellent looks like. • Make it vivid. Make it specific. • Then refuse to settle for anything less. The best performers don't resent high standards. They're attracted to them. 2. Co-Author Crystal Clear Expectations Vague goals lead average results. Clear goals define the "what" and the "how": • What does wining look like? • What's the timeline? • What resources do they have? • What constraints exist? • How can they exceed? • What would cause them to fall short? When you align on expectations upfront, you eliminate 75% of future conflicts. 3. Give Frequent (Helpful) Feedback Mediocre managers withhold feedback to be nice. The best coaches give real-time feedback: • When you see excellence, call it out immediately • When you see a miss, address it directly • Proximity increases potency Normalize feedback and you'll systemize excellence. 4. Proactively Remove Obstacles The best way to be in the way is using your position to clear the way. Your team shouldn't waste energy fighting bureaucracy, navigating politics, or sitting in useless meeting. • Ask them constantly: "What's in your way?" • Then move heaven and earth to clear the path Your people should spend 100% of their energy on work that matters, not working around the work 5. Amplify Their Strengths With Your System Random acts of heroics don't scale. Your job is to turn individual brilliance into repeatable systems. • When someone solves a hard problem, capture how they did it • When they deliver exceptional work, document the approach • Then ensure that knowledge reaches others This is why you can't get out of their way. It's not micromanagement. It's leadership. It's not controlling. It's clarifying. It's not limiting. It's leveraging. The managers who survive the next wave of cuts won't be the ones who "stay out of the way." They'll be the ones who made their teams undeniably better. Helpful? Please RT and follow me @dklineii for more.
13
22
2
163
19,228
Thriving In Engineering retweeted
Championship teams don’t happen by accident. They are built by leaders who set the tone, model the standard, and raise the bar for everyone around them. If you want to build a team that leads itself, start here: The 10 Commandments of Team Leaders 1. Lead Yourself First - True leadership always starts from within. Leaders manage their actions, discipline, and attitude before trying to guide and influence others. They have the “courage to lead.” Self-leadership is always the first step to leadership. 2. Be a Thermostat - Don't just gauge the temperature, set it. Leaders should set the mood and tone for the team each and every day! Leaders are responsible for creating an environment conducive to success and positivity. 3. Manage the Locker Room - The locker room's atmosphere can make or break a team. This is a space that the coach is rarely in. Leaders should create a space of respect, unity, and focus. Make the locker room a launch pad for victory. 4. Bring Positive Energy - Leaders lead in energy and engagement. Embrace the 5:1 ratio of positive interactions to criticisms. Make sure you are dishing out 5 positives for every negative you have to share with others. Be a source of motivation your team rallies around. Be a Spark Plug! 5. Be a Connector of All - Bridge gaps between team members. Leaders ensure everyone feels included and valued. They create a cohesive unit that operates seamlessly on and off the field. 6. Build Others' Confidence - Leaders instill and cultivate confidence in their teammates. They celebrate their teammates’ strengths and encourage them during challenges, boosting their self-belief and team contribution. 7. Give Reminders - Team leaders always keep the team's goals and values at the forefront. Regular reminders of what you're working towards can keep everyone aligned and focused. 8. Accept Responsibility - Leaders must own their actions and decisions, setting an example of accountability and maturity. Accepting responsibility is key to gaining respect. 9. Hold Your Teammates Accountable - Ensuring everyone meets the team's standards is one of the hardest jobs of a leader. A leader should tactfully enforce rules and expectations, maintaining discipline and focus. 10. Be a Servant Leader - Finally, leaders lead by serving. They prioritize the team's needs over personal glory. A servant leader inspires loyalty and drives the team toward collective success. _____ If you like this post, you will love my free newsletter. Great Teams Better Leaders Join 15,000+ others. gregberge.beehiiv.com/subscr…
1
25
3
132
16,901
Thriving In Engineering retweeted
Linear has a 30-minute weekly meeting called "Quality Wednesdays." I sat through one and WOW Devs show a quality or perf-related fix they did last week. It can be big, or small. We went through 17 issues, from massive backend performance wins, to this tiny one. Can you see it?
29
61
21
1,223
247,654
i turned this career advice from Marc Andreesen (2025 version) into a series of prompts that can change your life: ↓
1
2
50
7,375
Confession: I've never successfully "managed" a stakeholder. Not once. Not a single time in my career. Every time I tried to "manage" someone, they pushed back harder. Every framework I used made things worse. 🧵
3
11
1
70
16,175
Thriving In Engineering retweeted
Vibe-coding is not the same as AI-Assisted engineering. A recent Reddit post described how a FAANG team uses AI and it sparked an important conversation about semantics: "vibe coding" and professional "AI-assisted engineering". While the post was framed as an example of the former, the process it detailed - complete with technical design documents, stringent code reviews, and test-driven development - is a clear example of the latter imo. This distinction is critical because conflating the two risks both devaluing the discipline of engineering and giving newcomers a dangerously incomplete picture of what it takes to build robust, production-ready software. As a reminder: "vibe coding" is about fully giving in to the creative flow with an AI (high-level prompting), essentially forgetting the code exists. It involves accepting AI suggestions without deep review and focusing on rapid, iterative experimentation, making it ideal for prototypes, MVPs, learning, and what Karpathy calls "throwaway weekend projects." This approach is a powerful way for developers to build intuition and for beginners to flatten the steep learning curve of programming. It prioritizes speed and exploration over the correctness and maintainability required for professional applications. There is a spectrum between vibe coding and doing it with a little more planning, spec-driven development, including enough context etc and what is AI-assisted engineering across the software development lifecycle. In stark contrast to the post, the process described in the Reddit post is a methodical integration of AI into a mature software development lifecycle. This is "AI-assisted engineering," where AI acts as a powerful collaborator, not a replacement for engineering principles. In this model, developers use AI as a "force multiplier" to handle tasks like generating boilerplate code or writing initial test cases, but always within a structured framework. Crucially, the big difference here is the human engineer remains firmly in control, responsible for the architecture, reviewing and understanding every line of AI-generated code, and ensuring the final product is secure, scalable, and maintainable. The 30% increase in development speed mentioned in the post is a result of augmenting a solid process, not abandoning it. For engineers, labeling disciplined, AI-augmented workflows as "vibe coding" misrepresents the skill and rigor involved. For those new to the field, it creates the false and risky impression that one can simply prompt their way to a viable product without understanding the underlying code or engineering fundamentals. If you're looking to do this right, start with a solid design, subject everything to rigorous human review, and treat AI as an incredibly powerful tool in your engineering toolkit - not as a magic wand that replaces the craft itself.
56
215
46
1,329
167,894
Thriving In Engineering retweeted
Your team isn't fighting about the solution. They're fighting about everything that came before it. Most conflicts happen because teams jump straight to "how" without agreeing on "what" or "why." Here's how to resolve any disagreement:
6
24
1
195
24,283
Thriving In Engineering retweeted
The most common mistake young founders make is forcing everyone to work 24/7 or 996. Here's 5 reasons why: – Very talented people, paradoxically, will work hard mimetically when they see people around them doing it, without the burden of compulsion. They want a carrot, not a stick. – It alienates practically everyone >35 or with kids. Experienced people who can save you months of time in the future making good decisions in the present, not just blind velocity. The best engineers can get more done in 40hrs/wk than most in 80. – The cost of losing someone good and familiar with your stack to burnout is far greater than the +20% hours. Two quarters of missed revenue, and it will hit your retention numbers. – I get it. It takes hard work to will a startup into existence. Founders should put in the effort (you, after all, have 25-100x the equity of your employees) and set the bar for what's expected. Reward those who meet the bar, remove those who don't. – Freeing up the compulsion to work all the time allows the best people to have fantastic ideas. Ideas need time to breathe and blossom. There are always exceptions, but generally you don't build generational companies with a slave-driver mentality. Culture is important. You want your employees to love their job and tell their friends that. Early engineers at companies like Google, OpenAI and Anthropic worked because they wanted to, not because they were forced to. Build a culture where people want to work hard. Don't force them to.
87
127
37
1,993
318,222