Alejandro Nanez

"It’s just a small change. It won't affect anything." Famous last words, right? If you work in QA or Software Development, you know that "minor updates" right before launch are the ultimate jump scare. One minute you’re ready to hit 'deploy,' and the next, your screen looks like a bug convention. The 4 Stages of a Last-Minute Change: 1️⃣ Denial: "It’s just one line of code, how bad can it be?" 2️⃣ Panic: Opening the build and seeing 15 new red flags. 3️⃣ Negotiation: Call Dev for that "It worked on my machine" pep talk. 4️⃣ Acceptance: Realising that an extended "sick leave" is the only logical solution. (Just kidding... mostly.) At Kualitee, we’re building the future of Test Management so that "small changes" don't turn into big disasters. What’s the most "interesting" bug a last-minute change has ever gifted you? Share your horror stories below!

10

Bolt vs. Claude Code for a React Native build. The winner wasn't who I expected. My test was simple: Scaffold an Expo app using a detailed PRD. I expected Claude to do well, but it completely failed on the initial build. Despite the Context 7 MCP tool for access to latest docs on expo..😱 Bolt, surprisingly, got the entire structure right. In a SINGLE SHOT! But here's the discovery: Claude is incredible for iterative development. Once the main structure from Bolt was there, Claude was the best tool for debugging and refactoring. So the lesson isn't about which tool is "best," but when to use it: → Phase 1: Initial Scaffolding using a detailed PRD = Bolt → Phase 2: Debugging & Iteration = Claude Anyone else found a two-tool system that works for them? #AI #ReactNative #Expo #VibeCoding #Bolt #ClaudeCode

14

4 comentarios

Symfony over-engineers simple problems. And that's exactly why I use it. Three years ago, a junior dev on my team asked me why we needed a Service Container to do something that "two lines of code" could handle. He wasn't wrong. Two lines would work. For now. For one developer. On one feature. In one sprint. Six months later, that same "two lines" pattern was copy-pasted across 40 files. Different behaviours. Different assumptions. Zero consistency. That's the trap most PHP teams fall into: → They optimise for writing code fast → Instead of optimising for reading code at scale Symfony's "over-engineering" isn't overhead. It's future you being protected from past you. The DI Container forces you to think about dependencies. The EventDispatcher forces you to think about coupling. The Console Component forces you to think about separation. None of this feels necessary on day one. All of it feels essential on day 300. The best engineering decisions aren't the ones that make today faster. They're the ones that make next year survivable. Hot take: which framework or tool felt like overkill until it saved you? 👇 #PHP #Symfony #SoftwareEngineering #BackendDevelopment #TechLeadership #EngineeringCulture

4

2 comentarios