Powered by RND
PodcastsTechnologysnackableCast – About Software Development, Leadership & Engineering Culture

snackableCast – About Software Development, Leadership & Engineering Culture

Adrian Stanek
snackableCast – About Software Development, Leadership & Engineering Culture
Latest episode

Available Episodes

5 of 49
  • Pressure, Purpose, and the Price of Building Something Real
    🚀 From Developer to Entrepreneur: My 15-Year Journey. In this episode, I share my personal journey from being a software developer to becoming an entrepreneur responsible for multiple software products over the past 15 years. I'll discuss the challenges and realizations that come with this transformation, the critical need for business skills beyond development, and the importance of planning and experience to avoid burnout. You'll also hear my reflections on the pitfalls of early entrepreneurship, the process of building sustainable products, and the balance between technology and business strategy. Ultimately, this episode aims to offer valuable insights and cautionary advice for anyone considering a similar path. 00:00 Introduction and Personal Story 00:41 Transitioning from Developer to Entrepreneur 03:30 Challenges of Self-Employment 06:01 Lessons Learned from 15 Years of Experience 09:27 Building and Selling Products 12:54 Final Thoughts and Advice This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit blog.snackablecto.coach/subscribe
    --------  
    16:25
  • What I Have Learned After $300 With Agentic Coding
    🎁 BONUS: 14 Tips to Save Money with Claude Code! After spending over $300 working with Claude Code in production, I’ve learned what really works — and what’s just expensive noise. In this video, I share my personal lessons, what I wish I had known before, and how you can save time, tokens, and sanity. 👇 Chapters: 00:00 Intro 00:37 What We Want, Why, and How 01:56 Clean Codebase = Better AI 02:51 How Good Is Claude Code Really? 05:14 Claude & The Senior Developer 06:17 Flow vs Vibe Coding 07:06 The Economic Shift 09:14 Why Vibe Coding Suits Juniors 10:13 Why AI Isn’t Everywhere (Yet) 10:48 The Future of Coding 11:59 Vibe Coding Is Coming 🎯 14 Money-Saving Tips 13:28 Bonus Starts 13:41 Tip 1: Choose a Strict Language (e.g. TypeScript) 14:03 Tip 2: Clean React Structures 14:27 Tip 3: Use Context Files 15:01 Tip 4: Tests Are Key 16:32 Tip 5: Let AI Fix Its Own Errors 16:52 Tip 6: Work in Small Batches 17:48 Tip 7: Don’t Expect Perfection 19:12 Tip 8: No Multitasking 19:55 Tip 9: Manage Context Tokens 20:37 Tip 10: Comments Are Back 21:51 Tip 11: Let Go of Style Wars 22:54 Tip 12: Plan with the AI 23:30 Tip 13: Flow over Vibe (for now) 24:39 Tip 14: Split Big Tasks 25:45 Outro This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit blog.snackablecto.coach/subscribe
    --------  
    26:42
  • Quality ≠ Perfection
    In this episode, we explore why quality is not the same as perfection—and why striving for the latter too early can derail your product, your team, and your goals.Adrian shares insights from over two decades in software development, highlighting the common trap of aiming for an undefined version of “perfect” rather than defining and hitting achievable quality goals. Through personal anecdotes and thought-provoking observations, he explains how teams fall into overengineering or underengineering when quality isn’t clearly defined from the start. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit blog.snackablecto.coach/subscribe
    --------  
    1:41
  • Vibe & Flow Coding Will Change A Lot
    I see Flow Coding as the reasonable middle ground which will become mature in no-time.We hear about Vibe Coding everywhere. This is so different from what we have done for decades now. So, it might take too much attention right now, and things like Flow Coding aren’t in focus. I see Flow Coding as the reasonable middle ground, that will mature quickly.Staying in the flow of coding is great in many ways, but not being in the flow of coding would be rather nasty.We are not alone anymoreInterestingly, we aren’t doing this alone as humans but with AI coding tools. While we heard many bad things about the quality last year, things have shifted towards keeping quality rapidly overnight. So rapidly even that many Software Engineers still keep telling the old phrases:* AI Codes for you in 1 hour your app you and you debug it for the years to come.* AI creates garbage code.* AI degrades your own skills and makes you dumb.To mention some of the general ideas. But are those still viable? I don’t think so. AI moves faster than the human being can grasp right now.I have been using Claude Code in production for over a week, which totally changed my mind."After 32 years of writing code, I sat there, watching Claude Code do my job while I just pressed Enter. And the scary part? It did it well."When I Realized the Shift Had Already StartedThere are moments in your career that feel like turning points.Mine happened while testing a migration on a large-scale Next.js frontend. I wasn’t exploring AI for fun or toying with prompts; I was doing real work on real code and letting Claude Code take the lead.I’ve built software since the 1990s, from BASIC on C64 to web stacks and massive SaaS platforms. I know how migrations go: Messy, slow, and painful.But this time was different. The AI understood the task, handled edge cases, adjusted to patterns, and even debugged problems it encountered. I was no longer writing code. I was reviewing someone else’s—except that someone wasn’t a person.And that’s when it hit me: the future of coding isn’t about typing anymore. It’s about thinking, guiding, and reviewing. The execution? That can be handled by machines.What Makes Coding AI Actually WorkThe magic doesn’t happen automatically. You need a foundation.Here are the essential requirements if you want to work effectively with tools like Claude Code:* Good ArchitectureA clean, modular codebase allows the AI to reason across files. Spaghetti code? Forget it. Claude can only help if your code is already structured well.* A Strong Typing SystemTypeScript strict mode isn’t just good for you—it’s critical for AI. It provides guardrails that help the model understand constraints, infer intentions, and validate changes.* Project GuidelinesClaude Code reads your claude.md (or equivalent) and adheres to project conventions. Folder structure, import order, naming patterns—it all matters. Define the rules, and the AI will follow.* Testing StrategyIf you don’t have automated tests, you’re flying blind. TDD, component-level testing, and end-to-end checks let you trust what AI changes.* Experience Still MattersAI is powerful, but it isn’t intuitive. You need to catch subtle issues, architectural misalignments, or overconfident shortcuts. Your judgment is still the safety net.Key Takeaways* Claude Code isn’t just a prompt-based tool. It acts like a junior developer who learns fast and works with context.* Flow Coding is the future. Let AI handle the typing and jumping between files while you stay in flow, guiding strategy and verifying.* This changes energy dynamics. You don’t end a session mentally drained. You end with more creative bandwidth left.* Tooling is catching up. With editors like Cursor and assistants like Claude, we’re seeing the rise of AI-native development environments.* We’re still needed, just in a different role. Review, design, and decision-making are the new primary skills.My Personal ConclusionIf you're a podcast listener like me, here’s the takeaway: We’re moving from coders to curators. And the sooner we adapt, the more we can lead this shift—rather than get run over by it.The next generation of developers will grow up with Claude in their terminal, not VS Code alone.Are you ready for that?👉 Let me know what you think. Would you trust AI with your codebase?Adrian This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit blog.snackablecto.coach/subscribe
    --------  
    51:10
  • AI Took Over My Next.js Migration – Am I Still Needed?
    "So there is a machine, right now, substituting me after 32 years of coding. It’s just doing what I’ve done—so much faster. Can I go home now?" — from my video.The Moment I Realized AI is Coming for My JobI’ve been coding for over thirty years, writing, refactoring, and maintaining more code than I can count. Started with BASIC on C64 and transitioned into the web world. Yet here I was, sitting in front of my computer, watching Claude Code migrate my 90,000-line Next.js 14 codebase to Next.js 15 while I just pressed Enter.This was not just some gimmick. This was real. The AI wasn’t just suggesting code; it was executing migrations, fixing errors, even reasoning through problems. It wasn’t perfect, but damn—was it fast.For the first time, I questioned: If AI can do this now, where does that leave us, the engineers?The Challenge – Why I Even Tried This"I put Claude Code to the test—can it really migrate my 90K LOC Next.js 14 codebase to Next.js 15 without breaking everything?"We run a B2B SaaS platform with a large frontend built in Next.js 14. Migrating to Next.js 15 meant switching from Page Router to App Router, updating use client directives, fixing TypeScript compatibility, and running tests.Doing this manually would take hours—if not days. It’s tedious, error-prone, and frankly, boring.So, I turned to AI. I let Claude Code do the heavy lifting.And the results? Well, let’s just say… I wasn’t ready.AI vs. Developer – Who Wins?1. Setup Was Easy—Too EasyInstalling Claude Code was straightforward. Within minutes, it was analyzing my entire codebase. It wasn’t just looking at files; it was understanding patterns, naming conventions, linting rules, and architecture.Then came the first real test:Me: “Update all my components and add the use client directive where necessary.”Claude: “Sure. Here’s a batch script to automate it.”Wait, what? Instead of manually modifying 900 files, Claude generated a script that did it in seconds. When I ran it, boom. It was done.2. AI Didn’t Just Follow Orders—It Thought AheadAt first, I expected Claude to simply follow instructions. But no—it started anticipating problems.* Type errors? It refactored props to remove deprecated defaults.* Import mismatches? It auto-fixed them and ran a build check.* Test failures? It debugged and reran failing Cypress tests.It wasn’t perfect, and sometimes, it overlooked nuances or applied brute-force solutions, but it worked at breakneck speed.3. I Became a Passive Observer"I just pressed Enter all day long. AI iterated, debugged, and even verified its own fixes. It felt… unsettling."The scariest moment was when I realized I was no longer coding. I was just approving changes, like a manager reviewing work rather than doing the work myself.Was I really needed?Key Takeaways – What I Learned* AI is no longer just an assistant; it’s an engineer-in-training. It doesn’t just suggest—it executes, iterates, and verifies.* The role of a developer is shifting. We’re moving from writing code to reviewing AI-written code.* AI won’t replace engineers, but it will replace hands-on programming. Engineers will remain valuable in architecture, decision-making, and deep problem-solving.* Trust AI, but verify. AI makes mistakes—sometimes big ones. But it also catches issues we might overlook. (Hint: Same as a human engineer)* Test coverage is more critical than ever. If you let AI refactor a large codebase, tests are your safety net.The Future of Software DevelopmentWe’re at the start of something huge. AI isn’t replacing us yet but fundamentally changing how we work.If you’re still skeptical, I get it. But I’ll leave you with this:If AI can migrate entire Next.js apps in minutes, what will it do in 3 years?Let me know in the comments: Would you trust AI to refactor your production code?Next Video: Migration Page to App Router in Next.js 15I will upload the second part of the video in my paid section. It’s about an hour of uncut material with more information than the free one.Find this video and article valuable? Please repost and share it with like-minded peers ❤️YouTube upload: This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit blog.snackablecto.coach/subscribe
    --------  
    50:56

More Technology podcasts

About snackableCast – About Software Development, Leadership & Engineering Culture

snackableCast is a podcast for CTOs, tech leaders, and senior developers interested in Cloud-Native, DevOps, Team Culture, and Leadership. Tune in for bite-sized insights, advice, and tips from a seasoned SMB CTO. Join us as we explore the world of technology leadership with special guests and actionable takeaways. Boost your knowledge and stay ahead in the industry with quick episodes that fit your busy schedule. Get ready to become a more effective tech professional and inspire your team. blog.snackablecto.coach
Podcast website

Listen to snackableCast – About Software Development, Leadership & Engineering Culture, All-In with Chamath, Jason, Sacks & Friedberg and many other podcasts from around the world with the radio.net app

Get the free radio.net app

  • Stations and podcasts to bookmark
  • Stream via Wi-Fi or Bluetooth
  • Supports Carplay & Android Auto
  • Many other app features
Social
v7.16.2 | © 2007-2025 radio.de GmbH
Generated: 4/24/2025 - 7:37:57 PM