The change
After a lot of research and trying out multiple content management systems using various programming languages, we ultimately selected Umbraco. Since I was unfamiliar with the language, the company brought in an Umbraco MVP to develop our own Umbraco sites. During this time, I observed, learned, and finished up our PHP projects. For just over a year, I split my time—spending four days a week on PHP and one day learning .NET and Umbraco.
This period of splitting time was rough, because I quickly ran into a roadblock when doing self-study on .NET. The beginner courses I found were too easy. I had over a decade of experience in programming, I knew what a string was, I knew what classes and interfaces were, I just didn’t know the correct C# syntax to actually use them. On the other hand, advanced courses were too complex because I was missing basic syntax knowledge. It was extremely frustrating to be able to map applications out in my mind perfectly, but being unable to actually put them into writing - or, in this case, coding.
Eventually, I completed the old projects and transitioned to working as a full-time Umbraco developer, and that’s when it clicked that learning a coding language was no different from learning a regular language. Of course I wasn’t going to learn C# or .NET from dabbling in it for a few hours a week, if I wanted to learn I needed to do full immersion. So I no longer did anything but Umbraco projects, figuring things out and asking my colleagues if needed, but never giving in and saying I couldn’t do it.
I admit that it was a challenging period where I often doubted my decision, at one point even requesting a conversation with my manager to ask if he thought there was still a place for me within the company; going from a senior developer who could tackle any problem to someone needing to look up how to create an array in .NET felt like starting over as a junior and was tough on my confidence (and pride).
However, this experience also introduced me to something I hadn't really encountered online before: a genuine sense of community. I had my Umbraco MVPs within the company, who were always willing to help me and explained things with patience and understanding instead of making me feel like I was dumb and wasting their time. When I had questions, I could also post them online and would receive answers even from developers at competing firms. If I reported a bug to Umbraco, I actually got responses directly from their developers. This welcoming environment was refreshing and inspiring, and helped keep me motivated to push through.
In 2025, I attended Codegarden with my colleagues for the first time, and it further confirmed my views. We travelled together, spent time socialising, and enjoyed drinks and dinner alongside developers from other companies. While we were there, our company affiliations didn’t matter; we were simply developers connecting over shared interests and exchanging ideas.