What the work taught me

I’ve always cared about becoming a good engineer.

For me, being a good engineer has never meant knowing every framework or having an answer ready for every problem. It means understanding what I’m building, asking better questions, making decisions I can explain, and learning from the ones I get wrong.

I didn’t learn most of that from tutorials. I learned it through real projects. The requirements changed, systems became more complicated than expected, solutions looked right until they weren’t, and small decisions ended up mattering.

These are some of the stories that shaped me as an engineer.