Wim Godden (CTO / Principal Consultant, Cu.be Solutions) has been working with PHP and open source technologies since 1996. He is the creator of phpAdsNew (now OpenX) and the PHPCompatibility library, and has worked across database clusters, Internet backbone infrastructure, and high-scalability projects. He is currently CTO at a European locker company focused on luggage storage and events. This talk has also been given at PHP UK Conference 2026.
These notes are thin: this was a career/soft-skills talk with limited technical detail to capture. The notes below reflect what was said and the broader themes Wim has described in the conference abstract.
The non-linear junior-to-senior route
The conventional mental model of a developer career is a ladder: junior, mid-level, senior, lead, architect, CTO. Wim's point is that this model is inaccurate. The journey is not linear and not one-directional.
Developers move between individual contributor and leadership roles, sometimes voluntarily and sometimes due to circumstance. Some return to hands-on coding after time in management or architecture roles. Some skip levels entirely. Some reach a senior title via a different domain altogether. The path is closer to a climbing wall than a ladder: lateral moves, backwards steps, and unexpected routes up are all part of it.
This matters because treating the path as linear creates false expectations: that progression only ever moves upward, that seniority is purely time-based, and that any move that does not feel like "up" is a failure.
Seniors are built on reflex, not just knowledge
The second observation from the talk: what makes a senior developer is not primarily knowledge of syntax, frameworks, or tools. It is the accumulation of pattern-matched experience that produces fast, reliable instinct.
When a senior developer sees a problem, they often know roughly what category of issue it is before they have done any analysis. This is not magic or intelligence
- it is pattern recognition built from encountering hundreds of similar situations. The reflexes are trained, not innate.
This is also why the feeling of "falling behind" that developers experience when they move into lead or CTO roles is not imposter syndrome, as Wim explicitly notes in the talk description. Imposter syndrome is doubting whether you deserve your position. This is something different: it is the experience of having accumulated reflexes in a domain you are no longer practising daily. The knowledge does not disappear, but the speed and confidence of retrieval fades without regular use.
The implication: senior judgment cannot be shortcut. It comes from exposure over time to real problems, failures, and recovery.
The journey is not a one-way street
Wim's talk is framed around the transition from coder to lead to architect to CTO, but the key point is that this does not have to be permanent or directional. Developers who have moved into management or architecture roles can return to hands-on coding. The reverse is equally valid.
How you approach this journey matters more than which direction you move. Treating each stage as something to extract value from rather than a title to achieve shapes both your own experience and your effectiveness in the roles you hold.
Notes from Laravel Live UK 2026.