PierreHenry.Dev Tech Show

🎡 Pierre-Henry Soria 🌴

Writing about software engineering, AI, success, happiness, and positive time management 🚀 www.pierrehenry.dev

  1. 1d ago

    How to Become a Software Engineer Who SOLVES REAL-WORLD Problems

    What separates engineers who ship things fast from those who get stuck when problems get messy often comes down to thinking, habits, and how they approach unclear situations. This video breaks down how to build that way of working so you can handle issues with more calm, consistency, and steady progress even when nothing is fully defined. Key Lessons 1. Slow down before you touch anything Most people rush. Strong problem solvers pause, read the error, inspect the context, and understand what is actually failing. This gives clarity before any action. 2. Break the problem into tiny parts Take a messy issue and split it into small checks. What works? What does not? Where does the behaviour change? This lets you isolate the real cause instead of guessing. 3. Always reproduce the issue first If you can trigger the bug on demand, you are already halfway to a fix. Engineers who skip this step stay stuck longer. 4. Write down everything you test Keep a short log while debugging. It prevents going in circles, and it helps you reason like an investigator. 5. Learn one tool at a time, deeply Debuggers, profilers, logs, CLI tools. Being able to inspect a system properly is more valuable than memorising syntax. 6. Stay calm even when things look bad Good engineers do not panic when a system fails. They follow a method. Calm thinking is a competitive edge. Thanks for reading The Healthy Scientist: Build Using AI With Healthy Habits 🔥 I’ve been building several projects on my GitHub over the years that might interest you. Feel free to check them out for inspiration or jump in with contributions! There are so much more to come on my LinkedIn as well! Don’t forget to follow and stay tuned! 🔥 This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.pierrehenry.dev

    10 min
  2. May 29

    How Creative Thinking Helps You Solve Problems Faster (And Actually Better)

    I break down why solving problems the same way as everyone else keeps you stuck. And look, this is something I see all the time. Engineers hit a problem, Google it, find the first Stack Overflow answer, and ship it. Rinse and repeat. But here’s the thing: that approach only gets you so far. Creative thinking helps you spot patterns others miss, tackle challenges with fresh ideas, and ship solutions that are both faster and more effective. It’s not about being “artistic” or thinking outside the box for the sake of it. It’s about questioning assumptions, exploring alternatives, and asking “wait, what if we approached this completely differently?” In this video, you’ll learn how to build a mindset that makes your work sharper and more original. I’ll show you practical techniques to break out of default thinking patterns, how to reframe problems so solutions become obvious, and why the best engineering breakthroughs often come from challenging the “obvious” approach. Because let’s face it: the engineers who stand out aren’t the ones who memorize the most frameworks or write the most lines of code. They’re the ones who see problems differently and come up with solutions that make everyone else think “why didn’t I think of that?” So, let’s talk about how to become “that engineer” ⚡️ I’ve built tons of projects on my GitHub over the years. Check them out for inspiration or jump in to contribute! I’ve got more content coming your way on my LinkedIn! Hit that follow button so you don’t miss out! This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.pierrehenry.dev

    5 min
  3. May 26

    Ship Any Feature in Record Time Without Breaking Anything

    Learn how to move from idea to production quickly without losing quality. This video shows the exact steps engineers use to plan, release, and monitor features fast whilst avoiding common pitfalls. Perfect for anyone who wants to deliver faster and smarter. Look, shipping fast doesn’t mean shipping rubbish. Too many engineers think speed and quality are opposites, but that’s not true. The best engineers I know ship quickly because they’ve got systems in place that let them move fast without breaking things. Here’s the thing: moving from idea to production quickly is all about reducing friction at each step. You need a clear process that gets you from “we should build this” to “it’s live and working” without endless meetings, unclear requirements, or last-minute disasters. First, clarify what you’re building. I can’t stress this enough. Write down the feature in one sentence. What problem does it solve? Who’s it for? If you can’t explain it simply, you’ll waste time building the wrong thing. Next, break it down into small, shippable chunks. Don’t try to build everything at once. Identify the absolute minimum version that solves the core problem. Ship that first. Then iterate. This approach means you get feedback early, catch issues before they become disasters, and actually deliver value faster than trying to perfect everything upfront. Plan just enough. Not 50-page specs. Just enough to know what you’re building, what could go wrong, and how you’ll test it. I usually spend 30 minutes sketching out the approach, identifying potential problems, and writing down the main tasks. That’s it. Release carefully, but don’t overthink it. Use feature flags (AKA Feature toggle) if you can. Deploy to staging first. Test the critical paths. But don’t wait for “perfect conditions” to ship. Perfect conditions don’t exist. Ship when it works, monitor it closely, and fix issues as they come up. And here’s the crucial bit: monitoring. Once it’s live, you need to know if something breaks. Set up basic alerts, check error logs, watch key metrics. Too many engineers ship features and forget about them. The best ones stay vigilant for the first few days after release. I’ve built tons of product-centric projects on my GitHub over the years. Feel free to check them out for inspiration or jump in to contribute! I’ve got more content coming your way on my LinkedIn. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit www.pierrehenry.dev

    5 min

About

Writing about software engineering, AI, success, happiness, and positive time management 🚀 www.pierrehenry.dev