Beyond Coding

Patrick Akil
  • 0.0（0）
  • テクノロジー
  • アップデート：毎週

For software engineers ready to level up. Learn from CTOs, principal engineers, and tech leaders about the skills beyond coding: from technical mastery to product thinking and career growth. Created by Patrick Akil

  1. 5日前

    AWS Veteran: The New Software Development Life Cycle

    "I need to stop using Opus. This doesn't work." That was Heitor Lessa's conclusion after a refactor cost him 200 million tokens, and it forced him to rebuild the entire agent workflow now used across 1,400 engineers. Heitor spent 11 years at AWS, built Lambda Powertools to 230 billion API calls a week, and in this episode he walks through the full SDLC workflow on screen, from discovery to merge check. In this episode, we cover: The product loop: discovery, whiteboarding, and the /roadmap commandSpec-driven development with Open Spec and why vanilla setups failThree model tiers: SOTA for planning, mid-tier for implementation, cheap models for reviewsMerge checks with adversarial reviewers and attestations that catch agents fabricating test resultsThe /retro command: using the Socratic method to make your workflow more deterministicIf you're an engineer figuring out how to work with agents at team scale without losing trust in your codebase, this is the workflow to steal. This is also the first Beyond Coding episode with visuals on screen, so let me know what you think of the format. Timestamps: 00:00:00 - The Math Doesn't Add Up 00:00:43 - Amazon Hypergrowth: 11 Years, 8 Different Roles 00:03:29 - Learning From the Trenches as a Technical Account Manager 00:08:38 - Developer Identity and the Birth of Lambda Powertools 00:10:20 - The Hard Parts of Working in Public 00:13:12 - How Powertools Hit 230 Billion API Calls a Week 00:16:42 - Career Advice: Learn Adjacent Roles, Not More Tech 00:19:37 - When Leadership Decisions Don't Make Sense to You 00:23:21 - The Product Loop Starts With Discovery 00:25:22 - From Whiteboard to /roadmap 00:27:37 - Why Humans Plan First and Agents Come Second 00:30:33 - Commands vs Skills Across 32 Different Models 00:33:38 - Adversarial Reviewers on Every Plan 00:36:07 - The Socratic Method, Explained 00:40:29 - Why He Only Takes Paper Notes 00:44:43 - The Five-Line Paper Trick for High-Stakes Meetings 00:48:18 - /new-work: Capturing Scope Creep Without Derailing 00:54:03 - The Dev Loop Begins: Open Spec Explore 00:56:34 - Three Model Tiers: SOTA, Mid, Cheap 00:57:43 - The $5,000/Month Per Engineer Question 00:58:57 - Guardrails vs Autonomy for 1,400 Engineers 01:04:22 - Auto-Sizer: Does This Task Even Need a Spec? 01:07:26 - Decision Fatigue and Why Frameworks Win 01:09:10 - The Plan Phase: Specs, Design, Formal Verification 01:13:07 - The Refactor That Cost 200 Million Tokens 01:15:11 - When Agents Forge Evidence They Ran Your Tests 01:17:27 - Local-First Architecture Explained 01:23:04 - The Apply Phase: Fully Autonomous Loops 01:24:30 - Coding Was Never the Bottleneck 01:26:39 - Why This Workflow Is an Investment 01:27:39 - Decision Logs and the /onboarding Command 01:29:06 - Running Agents Locally With Enterprise Governance 01:32:42 - Hooks: Making Quality Gates Deterministic 01:36:02 - Merge Checks: 15 Adversarial Reviewers Per Change 01:38:30 - /retro: Interviewing Yourself to Improve the Loop 01:43:12 - Trust, Loss of Trust, and Recovery With Agents 01:48:02 - Experience, Scars, and Critical Thinking 01:49:32 - Why Right Now Is the Time to Experiment 01:52:04 - Conviction Comes From Being in the Loop #softwareengineering #aiagents #aws

    AWS Veteran: The New Software Development Life Cycle

  2. 7月15日

    What Senior Engineers do Differently (Vercel VP)

    What senior engineers do differently has less to do with output than most career ladders suggest, and Lindsey Simon, VP of Engineering at Vercel, has watched the distinction sharpen as everyone in the valley becomes a "member of technical staff." From why new grads with hackathon years might out-prepare engineers with six years on the job, to what happens when PR throughput stops being your lever, this is a conversation about what earns seniority now. In this episode, we cover: Why engineering roles are consolidating into "member of technical staff"How to ask agents first and frame better questions to humansThe scope-of-impact ladder and what the best engineers systematizeLearning how to learn: closing gaps to 100% understandingWhy writing is the skill that scalesIf you're wondering whether your years of experience still compound, or you're early-career and tired of the "woe is the juniors" narrative, this one reframes both. TIMESTAMPS 00:00:00 - Impact the Business 00:00:31 - FOMO all the time: The 2006 Google Interview 00:01:52 - Engineering Roles Are Consolidating 00:02:52 - The "Member of Technical Staff" trend in SF 00:03:33 - Interns Demo to the CTO 00:04:33 - How New Grads Out-Prepare Senior Engineers 00:06:10 - Ask Your Agent Before You Ask a Human 00:08:01 - Digging Backwards Into Fundamental Understanding 00:09:22 - "We're All Junior Engineers Again" 00:10:22 - Management Is Not Leadership 00:12:04 - Losing PR Throughput as Your #1 Lever 00:13:11 - Fulfillment Beyond Shipping Features 00:14:32 - Building for Fickle Engineers: Telemetry Beats Opinions 00:16:11 - Watching Users Struggle With Your Product 00:18:12 - Have Expectations for Seniors Actually Changed? 00:19:57 - Claude Says a Month, It Takes Two Hours 00:20:33 - What the Best Engineers Do Differently 00:21:30 - How Vercel React Skill Came to Be 00:22:23 - Why Conference Conversations Hit Different 00:23:35 - Learning How to Learn: Close Gaps to 100% 00:25:41 - The Case for Liberal Arts in Tech 00:27:03 - Get Feedback Early, Don't Hide in the Cave Guest - Lindsey Simon, VP of Engineering at Vercel: https://www.linkedin.com/in/lindseysimon #softwareengineering #ai #careergrowth

    What Senior Engineers do Differently (Vercel VP)

  3. 7月9日

    Why the Fastest Engineers Are Falling Behind

    The fastest engineers are falling behind, and Kitze was one of them. He built his reputation on raw coding speed, then realized his coding wasn't competing with anyone's coding anymore, it was competing with their setups. Wake-up call for developers: Kitze now runs 140 projects solo with agent loops, and in this episode he breaks down what separates the engineers pulling ahead from the ones getting left behind. In this episode, we cover: Vibe coding vs vibe engineering, and how to get better results from your agentsPolice files: Self-correcting loops that end every agent turn with zero errorsWhy teams of 10 are collapsing into teams of 2, and who survivesThe rude awakening coming for engineers who refuse to adaptThe number one advice to stay on track and fight FOMOFor individual contributors, tech leads, and principal engineers who don't plan on falling behind TIMESTAMPS: 00:00:00 - Intro 00:00:40 - Vibe Coding vs Vibe Engineering: The Real Difference 00:02:16 - Police Files: The Self-Correcting Loop on Every Turn 00:05:23 - Capture Every Frustration as a Rule 00:06:53 - Why Being the Fastest Coder Stopped Mattering 00:09:45 - Problem Solver vs Problem Lover: Pick One 00:10:43 - The Rude Awakening Engineers Don't Want 00:12:05 - Why Teams of 10 Become Teams of 2 00:13:09 - Loop Engineering: The Edge Anyone Can Build 00:16:08 - Why No Agent Orchestrator Works Yet 00:17:07 - Starting a Fresh Codebase: What Kitze Transfers 00:19:14 - No Sidebars: Inventing an Agentic OS 00:21:07 - How Kitze Shipped 300 Changes Across 200 Repos 00:23:40 - We Are Becoming the Bottleneck 00:24:25 - Why Leadership Must Give Engineers Room to Experiment 00:26:16 - The Token Divide: Not Everyone Can Compete 00:27:41 - Learn Now or Lose Access Later 00:29:33 - The Culling: Coasting Is Going Away 00:30:45 - Why LLM Code Reviews Beat Tired Seniors 00:33:21 - Solo Engineers With Agent Swarms vs Teams 00:34:53 - Agents Climbing the Org Chart to CEO 00:36:03 - What Distinguishes the Best Engineers: Unblocking 00:36:50 - Ego Is the Real Bottleneck 00:37:55 - Kitze's #1 Advice: Stick to One Model

    Why the Fastest Engineers Are Falling Behind

  4. 7月1日

    AI Cloud CTO: Which Engineering Skills Are Most In-Demand Right Now

    Danila Shtan runs engineering at Nebius, one of the biggest AI clouds in the world, and he told me exactly which engineers he hires on the spot. There are only hundreds of people on the planet with the skill he wants most, and it is not the one you are grinding on. We get into which engineering skills are actually scarce and well paid today, and which ones are quietly on the way out. In this episode we cover: The engineering skills in highest demand right now and which ones are on the way outWhy an AI cloud CTO restricts Claude Code inside his own companyDan's rule for merging any AI-written code into productionWhy working with an agent is like managing a junior engineerThe interview question that surfaces top tier engineer qualitiesWhy he still runs algorithm interviews todayIf you are an engineer trying to work out where the value sits now that agents write the easy code, this is a straight answer from the person building the infrastructure underneath all of it. Timestamps:00:00:00 - AI Agents doing everything is a lie00:00:44 - What Nebius Actually Does00:04:31 - The Engineers In Highest Demand Right Now00:06:58 - Inside the Hiring Process00:08:12 - The Bootcamp: You Join the Company, Not a Team00:10:51 - Why You Can't Use AI in Their Interviews00:16:31 - Why He Banned the Word "Headcount"00:22:25 - Why a CTO Is Not a Technical Role00:24:49 - The One Skill Every Manager Needs00:25:48 - Why Smart People Fail at This00:28:17 - "The Promise of Agents Is Bullshit"00:31:39 - How AI Multiplies Your Baseline Skill00:35:32 - Why an AI Agent Is Just a Junior Engineer00:36:57 - Why He Won't Let His Team Use Claude Code00:37:46 - His Rule for Merging AI-Written Code00:40:28 - The Interview That Predicts Great Engineers00:42:32 - From T-Shaped to Round-Shaped Engineers00:44:30 - Is There Still a Path for Juniors?00:45:28 - Why Hard Skills No Longer Matter00:47:11 - The Engineers Who Will Become Obsolete00:50:04 - The Real Reason People Stay at Banks00:52:26 - Where AI Agents Actually Help00:54:40 - Why He Still Uses Algorithm Interviews00:56:05 - Tech Enthusiasts vs. Real Engineers #AIEngineering #TechCareers #SoftwareEngineering

    AI Cloud CTO: Which Engineering Skills Are Most In-Demand Right Now

  5. 6月24日

    Career Expert: Why Applying to Jobs No Longer Works

    120,000 tech workers have been laid off in 2026, yet there are 60,000 open roles. Engineers applying are sending out 100 applications for zero replies. Former Reddit, Uber and Disney Plus recruiter Keki Mwaba breaks down why the market broke, why every resume now looks identical, and what gets you hired when yours looks like everyone else's. In this video, we cover: Why 120,000 layoffs and 60,000 open roles don't add upWhy CVs have become too good and it's no longer enoughHow to treat LinkedIn as a platformGetting into companies like OpenAI and AnthropicHow to reach out to people without seeming fakeIf you're a software engineer trying to stand out in the most competitive tech market in years, this is the playbook. Timestamps: 00:00:00 - Intro 00:00:35 - How bad is the tech job market in 2026? 00:02:38 - 120,000 laid off, 60,000 jobs open: the math is not mathing 00:04:05 - LinkedIn isn't a CV, it's a platform 00:08:30 - The underrated move: comment your way into a job 00:10:48 - Is AI ruining LinkedIn? 00:13:50 - Never feel safe: how to prepare before a layoff 00:15:34 - What layoffs do to the people who stay 00:17:03 - "Did I just automate myself out of a job?" 00:18:48 - Why every resume now looks the same 00:20:11 - Why referrals beat applications 00:22:13 - Do software engineers still have a future? 00:23:32 - The staff engineer who wants to quit for plumbing 00:26:16 - Patrick on his own job security 00:30:21 - 70% of job descriptions now demand AI skills 00:31:34 - Is middle management disappearing? 00:33:53 - The impossible ask: stay current, deliver, and not burn out 00:37:02 - How to get hired at OpenAI or Anthropic 00:39:18 - How to message someone without seeming fake 00:41:42 - Build a portfolio that shows your thinking 00:45:12 - Your personal branding plan for the next few weeks Guest: Keki Mwaba, career and recruitment expert: https://www.linkedin.com/in/keki-mwaba #techjobs #softwareengineering #careeradvice

    Career Expert: Why Applying to Jobs No Longer Works

  6. 6月17日

    Why the Frontrunners Say Coding Is Solved BUT Engineering is Not

    Jeroen Gordijn and Jeroen Dee: two frontrunners who stopped writing code months ago and say software development is already solved. Typing code is no longer necessary, but what matters more now? If you're an engineer that loves coding, you're in a tougher spot than you might realize. In this video, we cover: - Why writing code is "solved" but engineering isn't - Spec-driven development and how to get it started in your team - The "Dark Factory" and why code review is a huge bottleneck - Model vs harness: what matters more, and why - The unhealthy side of agentic coding If you write software for a living and you're trying to work out what your job becomes next, start here. Timestamps: 00:00:00 - Coding Is No Longer Necessary 00:00:43 - Why "Software Development Is Already Solved" 00:02:57 - Should You Even Read the AI's Code? 00:05:05 - What Is a "Dark Factory"? 00:06:52 - If You Can Regenerate It, Why Care About Quality? 00:07:49 - Spec-Driven Development Explained 00:11:32 - Adopting Specs Without Starting From Scratch 00:13:23 - Model vs Harness: What Matters More? 00:17:27 - Is Your Harness the New IDE? 00:20:18 - Why Everyone Plateaus (and the Innovation Token) 00:22:50 - Where to Actually Spend Your Time 00:24:57 - The Unhealthy Side: "It's Free Cocaine" 00:28:00 - Is This Sustainable, or Just Subsidized? 00:30:33 - Should You Run Models Locally? 00:34:31 - Looping, Scale, and Automating Review 00:37:53 - What's Left for Engineers to Do? 00:39:13 - If You Love Writing Code, You're in Trouble 00:41:18 - Why Teams Are Getting Smaller 00:43:03 - What an "Agentic Company" Looks Like 00:46:25 - How to Start: Find Your Spark 00:50:13 - The One Habit That Keeps You Ahead Guests: Jeroen Gordijn: https://www.linkedin.com/in/jeroengordijn Jeroen Dee: https://www.linkedin.com/in/jeroendee #AgenticEngineering #SoftwareEngineering #Agents

    Why the Frontrunners Say Coding Is Solved BUT Engineering is Not

  7. 6月10日

    Why The Best Software Engineers Are Solving Code Review Bottlenecks Now

    AI generates 10x more code, but your senior engineers still review it by hand and it's burning them out. Even Google admits code review is now the bottleneck nobody knows how to solve. Florian Buetow, AI engineer at Xebia, has been running experiments to eliminate the human from the review loop entirely, and what he found changes where engineers should focus their effort. In this episode, we cover: Why "stop doing code reviews" is a serious answer (and what replaces them)The guardrails that gave the most value: Semgrep rules, architectural unit tests, and stop hooksWhy your harness matters more than the modelHow Amazon and Google police AI-generated code with policiesAI burnout, cognitive debt, and "cognitive surrender": what stays your responsibilityStep one for adopting agentic software engineering in your team this weekWhether you're an individual developer drowning in AI-generated PRs or driving AI adoption across a large engineering org, you'll leave with concrete experiments to run. More from Florian: https://cracking-ai-engineering.com Timestamps: 00:00:00 - Intro 00:00:40 - Code Review Is Software Engineering's Biggest Bottleneck 00:01:57 - How Amazon and Big Tech Police AI-Generated Code 00:02:55 - Horizontal vs Vertical Scaling of AI Engineering 00:04:37 - Why "No Code Reviews" Might Be the Answer 00:05:22 - Engineering Environments That Give Agents Feedback 00:06:46 - Why the Harness Matters More Than the Model 00:07:21 - When Spec-Driven Development Failed and TDD Worked 00:10:06 - Stop Hooks, Ralph Loops, and Automated Feedback 00:11:30 - The Guardrails That Gave the Most Value 00:14:00 - Architectural Constraints That Keep AI Code Sane 00:15:07 - What Remains a Human Responsibility 00:17:33 - Why All the Hard Work Moves Upfront Now 00:18:47 - The Incredible Skill Junior Engineers Should Learn 00:20:26 - AI Burnout: Why Engineers Are Exhausted 00:22:42 - Cognitive Surrender: Letting the Agent Take Over 00:23:25 - The Hand Grenade Problem with AI at Work 00:24:08 - Outsourcing Code Review to AI Itself 00:26:39 - Teams That Fully Adopted Spec-Driven Development 00:29:01 - Can You Rebuild Software From Tests Alone? 00:30:27 - How to Experiment and Stay Ahead 00:33:15 - Spying on What Subagents Tell Each Other 00:33:59 - Step One: How to Start with Guardrails 00:36:08 - Data Mining Your Session Logs for Patterns 00:37:00 - Stuck With One Harness? Here's What to Do 00:38:28 - The One Experiment to Run This Week #softwareengineering #aicoding #codereview

    Why The Best Software Engineers Are Solving Code Review Bottlenecks Now

  8. 6月3日

    Google DeepMind Lead: The New Rules of Software Engineering

    Are you ready to adapt to the rapidly evolving rules of software development? In this deep dive, Logan Kilpatrick, Director and Engineer at Google DeepMind, breaks down how AI agents, advanced model-product symbiosis, and tools like Gemini 3.5 Flash are fundamentally shifting the engineering bottleneck. Learn how to maintain your competitive advantage by moving beyond the keyboard to focus on problem-solving, architectural taste, and system understanding. In this video, we cover: The changing role of the IDE and the rise of agent managers in code generation.Overcoming team bottlenecks in code review and CI/CD test execution execution loops.Why "agent coverage" and context integration are the next big tech stack metrics.Building a bulletproof software portfolio through permissionless open-source contributions.The critical difference between outsourcing intelligence versus outsourcing understanding.This episode is for software engineers, tech leads, and computer science students looking to future-proof their careers and reset their ambitions in the era of autonomous engineering agents. Timestamps:00:00:00 - Intro00:00:40 - Code Review Is Software Engineering's Biggest Bottleneck00:01:57 - How Amazon and Big Tech Police AI-Generated Code00:02:55 - Horizontal vs Vertical Scaling of AI Engineering00:04:37 - Why "No Code Reviews" Might Be the Answer00:05:22 - Engineering Environments That Give Agents Feedback00:06:46 - Why the Harness Matters More Than the Model00:07:21 - When Spec-Driven Development Failed and TDD Worked00:10:06 - Stop Hooks, Ralph Loops, and Automated Feedback00:11:30 - The Guardrails That Gave the Most Value00:14:00 - Architectural Constraints That Keep AI Code Sane00:15:07 - What Remains a Human Responsibility00:17:33 - Why All the Hard Work Moves Upfront Now00:18:47 - The Incredible Skill Junior Engineers Should Learn00:20:26 - AI Burnout: Why Engineers Are Exhausted00:22:42 - Cognitive Surrender: Letting the Agent Take Over00:23:25 - The Hand Grenade Problem with AI at Work00:24:08 - Outsourcing Code Review to AI Itself00:26:39 - Teams That Fully Adopted Spec-Driven Development00:29:01 - Can You Rebuild Software From Tests Alone?00:30:27 - How to Experiment and Stay Ahead00:33:15 - Spying on What Subagents Tell Each Other00:33:59 - Step One: How to Start with Guardrails00:36:08 - Data Mining Your Session Logs for Patterns00:37:00 - Stuck With One Harness? Here's What to Do00:38:28 - The One Experiment to Run This Week #SoftwareEngineering #AIAgents #GoogleDeepMind

    Google DeepMind Lead: The New Rules of Software Engineering
すべて見る（260）

番組について

For software engineers ready to level up. Learn from CTOs, principal engineers, and tech leaders about the skills beyond coding: from technical mastery to product thinking and career growth. Created by Patrick Akil

情報

  • クリエイター
    Patrick Akil
  • 配信期間
    21年 - 26年
  • エピソード
    260
  • 制限指定
    不適切な内容を含む
  • Copyright
    © Patrick Akil
  • 番組のWebサイト
    Beyond Coding

その他のおすすめ