What My Career Taught Me (So Far)

Twenty years of lessons, in one post.

Twenty years in front-end development is long enough to see several best practices become warnings and then best practices again. The lasting lessons have less to do with particular tools and more to do with people, judgement and keeping complexity under control.

The useful question behind “What My Career Taught Me (So Far)” is what changes in the work afterwards. A sound idea should improve a real decision, not only give us a neat phrase for describing it.

The answer is rarely a universal rule. It is a way of looking at the decision clearly enough to choose on purpose.

Make the work easier to do well

The leadership part is rarely the grand speech. It is the ordinary environment around the work: whether people can ask an awkward question, whether priorities stay still long enough to act on them, and whether useful effort is noticed.

My practical test is simple: after a conversation, does the other person have more clarity and more agency? Good leadership should not make the leader look essential. It should help the team make sound decisions without waiting for permission at every turn.

Leadership is not having every answer. It is making better answers possible.

Trust is built in small, repeatable moments. Say what matters, make space for challenge, and follow through when somebody takes the risk of being honest.

I do not always manage it perfectly. The aim is to make the better choice easier to recognise the next time it appears.