Things I learn working for big company

Big companies teach a different things than startups. Less about the code, more about everything around it especially culture, people. To me the lessons is very valuable and i want to share this hopefully you can get some insights

The user problem comes first

The best engineers I met were obsessed with the user's problem, not the interesting one. A clever system that solves the wrong problem is still the wrong system.

Do, then improve

Debate creates opinions. Shipping creates information. I prefer a small, safe move that touches reality over another round of arguing in a meeting room: first do it, then do it right, then do it better.

That is not permission to ignore quality. It is sequence: prove the direction is useful, make it correct for the context, then improve where evidence/trend says improvement matters.

The same instinct applies to what you choose not to build. A feature that never ships has no bugs and no maintenance bill. And new technology behaves like a loan: the repayments arrive later as incidents, on-call pages, and hiring problems. Boring is a strong default because boring fails in ways everyone already understands.

Slow teams are usually misaligned teams

When a project drags, the instinct is to blame execution: people are not working hard enough, there are not enough engineers. Not all but usually that is wrong. People are working hard against different assumptions about priorities, ownership, and interfaces.

At scale, coordination is the engineering work. The senior move is almost always to make things clearer, not cleverer.

Your code does not speak for itself

Code sits silently in a repository. People advocate: a manager mentions your work in a meeting, or not. A peer recommends you for a project, or recommends someone else.

A warning sign: if you win every debate, something is wrong. People have not been convinced. They have given up, and they will express the disagreement in execution instead of in meetings.

Writing is debugging your own thinking

When I explain something simply, in a doc, a review comment, or even a chat with AI, I find the exact places where my understanding is shallow. Teaching is how I test whether I actually understand a thing.

Protect what you can control

Reorgs, pivots, and market shifts sit outside your control. The quality of your work, how you respond, and what you learn sit inside it. Worrying about the reorg does not improve the work in front of you.

And eventually time becomes worth more than money. I watched senior people learn that one too late, chasing one more level and wondering afterward if it was worth what it cost.

The summary is be very clear on purpose: stay curious, stay humble, and remember the work is always about people. The users you build for, and the teammates you build with

cheer