The mistake that changed my programming career

I had been working in frontend development and wanted new projects. The offer seemed to fit that ambition, but the work changed in practice and team support was lower than expected. In the recording, I explain how I experienced that situation.

It is a personal experience, not a conclusion about every consultancy or job move. My takeaway is to ask about everyday work: responsibilities, technology, available support and how decisions are made.

There was then a break, personal projects and new jobs, including a small team with much more direct communication. Some periods ended because of business circumstances. That journey overlapped with personal responsibilities and changes.

Telling it in sequence can make it sound like an organised strategy, but many decisions responded to unfolding events. That is why I do not present the path as a perfect sequence. Some attempts did not work.

Working on projects of different sizes taught me different ways of connecting interfaces, services and client needs. In a small team, I could see more of the complete journey; larger organisations brought other forms of coordination.

That variety broadened my experience, even when periods were difficult. When reviewing a previous job, it can help to separate technical learning from changes you need in how people collaborate. Those conclusions are related but not identical.

The video closes with the idea that a decision experienced as failure can take on another meaning over time. That does not require celebrating everything that happened. It allows you to recognise the information it gave you and how it influenced later decisions.

If you are considering a change, write down what you want and what you need to check before accepting. If you have already had a difficult experience, review it using the information you had then. The aim is to decide better from your current position, not demand that you should have known the future.