Bijdrage van Marcos Feijó Felipe

Yesterday, I was talking with a colleague about a skill that is incredibly rare but absolutely critical in our industry: knowing how to advocate for your ideas. Engineers are full of brilliant insights. We don't just see bugs; we see product opportunities. We see architectural changes that could save the department thousands of dollars, or workflows that could make our entire team’s life easier. But where do those ideas usually stay? Blocked in our minds, or buried in casual chats near the coffee machine. Let's face it: communication and soft skills aren't always the default settings in a developer’s skill set. We think in a highly structured, "code-oriented" way. It’s a superpower for building robust systems, but it’s definitely not the best interface for pitching a vision to a non-technical stakeholder. What usually happens? We try to express our idea once. We get a quick "no" or a blank stare, and we immediately dig that idea as deep into the ground as possible, never to mention it again. We treat a single rejection like a fatal system crash. If you truly believe in an idea, you owe it to yourself—and your company—to fight for it. But like any good strategy, you have to fight smart: 1. Choose Your Battles: You shouldn't go to war over every minor architectural preference. Like maintaining focus on a fast motorcycle ride, you need to look down the road and pick the specific lanes that will genuinely move the needle for your team, your department, or the product. 2. Know Your Audience: A Product Manager or a Director doesn’t care about the elegance of your database indexing; they care about impact, user experience, and velocity. Translate your technical passion into tangible business value. 3. Build an Alliance: You don't have to carry the flag alone. Find a colleague, a friendly product manager, or someone you trust, and bounce the idea off them first. Pair-program the pitch before presenting it to the wider room. 4. Use AI as Your Translation Layer: If your brain naturally formats things like a rigid pull request, use an AI agent to refactor that "code-logic" into a product-focused, high-signal proposal that resonates with business leaders. Let it handle the API translation between engineering and business. Every day is an opportunity to learn and improve. Learning how to navigate the human "pain of change" is just as important as writing clean code. Don't let a great idea die just because the first pitch didn't land. Bring structure, find your allies, and learn the discipline of advocacy. Winning those fights is exactly how you grow—and how your team and company grow right alongside you. To my fellow engineers and technical leaders: Have you ever buried a great architectural or product idea because it was too difficult to explain to the business side? How did you learn to bridge that gap? Let's talk in the comments.