Peter Daum

"Shift left” sounds good on paper. Faster feedback. Earlier testing. Cost savings. But here’s the uncomfortable truth: shifting left won’t save you if your culture stays stuck. You can throw tests into CI pipelines, automate early, and chant DevTestOps until the walls echo. But if your teams still treat testing as a phase, quality as someone else’s job, or feedback as a nuisance, all you’ve done is moved broken thinking upstream. I’ve seen companies install shiny new tooling with zero conversation about shared ownership. I’ve seen developers resist writing tests because “that’s not what we do.” I’ve seen testers struggle to add value early because they’re still expected to “verify the build” instead of shape the build. Shifting left without shifting culture is like moving the finish line but refusing to train differently. You don’t get better outcomes. You just get earlier dysfunction. If you’re serious about building quality in, here’s what needs to shift first: - The belief that quality is everyone’s job, not just the testers’. - The space for testers to be part of discovery, not just delivery. -The trust that cross-functional collaboration is not optional, it’s foundational. True shift left starts with mindset, not tooling. With conversations, not compliance. With people, not processes. If your culture still rewards speed over safety, delivery over discovery, and blame over learning, no amount of leftward motion will get you where you want to go. I help companies get this right not by selling buzzwords, but by rebuilding how teams think, act, and deliver together. If that’s the kind of change you’re ready for, I’d love to talk. #softwaretesting #softwareengineering #qualityleadership #teststrategy #brijeshsays

173

27 Kommentare

Most junior engineers think they’ll be rewarded if they: → close lots of tickets → stay late and jump on every bug → write clever code and push big PRs But you’re rewarded for being the person who: → ships predictable outcomes, not surprises → prevents incidents before they happen with tests, alerts, and runbooks → makes the team faster with clear docs, small PRs, and crisp reviews → understands the user and ties work to a metric the business cares about → reduces cost and risk: cleaner designs, fewer moving parts, simpler ops Hard fact: believing “more hours + more tickets = growth” is a recipe for burnout and stalled careers. You’ll feel busy, but you won’t be valuable. Do this instead: → Pick one metric to move this quarter: p95 latency, crash rate, signup conversion, cloud spend. → Own one thing end to end: read code paths, write a tiny RFC, add dashboards, add alerts, add tests. → Kill recurring pain: automate a flaky deploy step, fix a flaky test, script a one-click local setup. → Review like a pro: spot risk, ask for data, suggest simpler designs, add examples to docs. → Learn the domain: sit with PM, Support, or Data weekly; collect real user stories. → Teach one person: pair once a week, share your notes, leave the project better than you found it. Yes, work hard. Give it your all. But keep asking, “What action creates the most impact for my team and our users today?” It may not feel like much each day. Some days it is just one small improvement. Stack those improvements for 90 days and you become the person people rely on. Stack them for a year and you become the person they plan around. You’re not paid for sweating more. You’re paid for being hard to replace.

811

40 Kommentare

From Developer to CEO Part 03: 5 to 10 years of experience Congratulations, you’re now a senior developer. But you’re not a senior just because you’ve reached 5 years of experience. You’re a senior because you’ve seen more problems— and you know how to prevent them. At this stage, you should be able to build software from A to Z. But your main focus must now shift to business impact. Not just how to code, but how to solve real business problems. Code shouldn’t be your challenge. Code should be your tool—to deliver value. For that, start asking the right questions: • What’s the real problem the customer is trying to solve? • Why does the client need this feature? • What’s the expected benefit for their business? • Is there a better solution? You’re not just a developer anymore. You should become a technical partner to your clients, not just someone who takes orders. Your new mindset: 👉 How can I maximize my customer’s success? If you follow these tips, you’ll level up faster. ⸻ After 20+ years in web development, I’m sharing what I wish I had known when I was younger. This post is a follow-up to Julien Rajerison’s post. Tomorrow, we’ll talk about developers with 10+ years of experience. ⸻ You’ve got this. I’m Toky RABESON. I’m a seasoned web developer.

94

4 Kommentare

You know that one senior dev on your team; let's call her Sarah. She makes everything look effortless: - Debugs issues in minutes while you're still stuck after hours - Writes clean code that just works - Explains complex concepts so clearly even non-tech people get it - Stays calm when production breaks You watch Sarah and think:  “I want to code like her.” So you try copying what you see; her debugging approach, coding style, PR structure. But it doesn't work the same for you. Here's why:  You're copying her methods, not her system. What you see: - Sarah writes clean code on first try - Quick, methodical debugging  - Clear technical communication What you DON'T see: - 2 years building her debugging framework - Her collection of refined code snippets - Daily 15-min learning ritual - Mistake log she updates after every bug - Weekly reflection sessions analyzing what worked/didn't Sarah's invisible debugging system: 1. Always reproduce the bug first 2. Check the same 5 places every time 3. Set 20-min timer, if stuck, ask for help 4. Update her "common issues" doc after each fix Her calm confidence?  It comes from having systems she trusts. When production breaks, she's not stressed, she has a proven process. You get stressed because you're improvising every time. Start building YOUR system: Week 1: Start a debug log Week 2: Create a 15-min daily learning ritual  Week 3: Build your first checklist/template Don't copy Sarah's methods. Build the system that will create YOUR methods. The senior dev others want to emulate?  That's who you become when you stop copying outputs and start building systems. What system are you building this week? 👇

91

41 Kommentare

MediatR is powerful. But here's the truth: 👉 Using it for a simple project is like using a chainsaw to slice bread. Technically possible, but massively overkill. If your team and your app are small, chances are you don't need pipelines, handlers, and all the extra complexity. Stick to direct calls, filters, and middlewares — you'll ship faster with less cognitive load. 💡 The real flex? Choosing the simplest architecture that solves the actual problem.

35

3 Kommentare

🚨 More than 70% of frontend devs struggles with this follow-up question in interview about PWAs? When asked: “How does offline access work in a PWA?” Most confidently say: “Because of Service Workers!” ✅ Correct… but do you know 👇 💡 “What’s the difference between Service Workers and Web Workers?” This is where many candidates struggle but not anymore Here’s the breakdown you should never forget: ⚡ Web Workers 1️⃣ Run JS in a separate thread → avoid blocking the UI. 2️⃣ Die when the page closes. 3️⃣ Best for CPU-heavy tasks (e.g. image processing, data crunching). 🌐 Service Workers 1️⃣ Act as a proxy between your app & the network. 2️⃣ Can intercept requests, cache responses, & serve content offline. 3️⃣ Live beyond page lifecycle → even when the app is closed. 4️⃣ Backbone of offline PWAs, push notifications, & background sync. 🚀 Key takeaway: Web Workers = Performance Service Workers = Offline + Background capabilities 📌 Have you ever faced this question in your system design interview? #Frontend #Interview #frontendinterview #PWA #SystemDesign #WebWorkers #ServiceWorkers #javascript #reactjs #frontendgeek

40

6 Kommentare

You'll find this code smell in many production codebases. I see this far too often: magic numbers and strings. The problem with magic numbers (or strings) is that they carry no meaning. The code is harder to reason about and more error-prone. My preferred solution is introducing a config value or enum. This is just one thing you can do to make your code cleaner. It's clean code Saturday, so here are 5 C# refactoring tips: https://lnkd.in/eZQY4CgH Do you dedicate time each week to refactoring your code? --- Sign up for the .NET Weekly with 74K+ other engineers, and get a free Clean Architecture template: https://lnkd.in/eJSR2bmm

424

19 Kommentare