Early in my career, I thought being a good developer meant writing clean code, closing tickets, fixing bugs, and delivering features on time.

And to be fair, those things are important.

But after working on real products, collaborating with different teams, and seeing how projects succeed or fail, I realized something:

The engineers who had the biggest impact weren't always the ones writing the most code.

They were the ones taking ownership.