Rethinking Good Engineering: Beyond Just Making it Work

I used to think writing code = being a good engineer. Honestly… that’s how I judged myself too. If my code worked, I felt confident. If it didn’t, I felt like I wasn’t good enough. But things changed when I started working on real codebases. I saw code that worked… but was impossible to understand. I wrote features that worked… but broke something else later. I fixed bugs… but didn’t know why they happened in the first place. That’s when it hit me 👇 Good engineering isn’t about just making things work. It’s about: Writing code someone else can pick up in 6 months Understanding the “why”, not just the “how” Thinking about edge cases before they break things Asking better questions, not just giving quick solutions Now, I spend more time reading code, thinking, and debugging than just writing new lines. Still learning. Still improving. But definitely thinking differently now. What changed your perspective about software engineering? 👇 #softwareengineering #developers #programming #learninpublic #coding #careergrowth

  • No alternative text description for this image

"I spend more time reading code, thinking, and debugging than writing new lines." You've unlocked the part of the job that was always the job, just nobody put it in the tutorial :)

After a few years in the industry, I’ve realized making code work is just the beginning. Now I focus more on writing maintainable code and truly understanding the “why” behind every solution.Amazing post btw 👍

True 100% that's why Developer ≠ Engineer

yes understand the problem that will make a good engineer

See more comments

To view or add a comment, sign in

Explore content categories