The Value of Feeling Unready: What My First Year as a Developer Taught Me
One thing I’ve started noticing early in my career is that the projects that teach you the most are usually the ones you don’t feel completely ready for. They’re the tasks that initially make you question whether you have enough experience, enough technical knowledge or enough confidence to take them on properly. But they also force you to grow faster than anything else. Looking back, the moments where I’ve learned the most have almost always come from being pushed outside my comfort zone and having to figure things out as I go.
Where I felt this most was when I was assigned ownership of tasks that initially felt beyond my level as a junior developer. One of those was a large application rebrand that touched almost every part of the product and required much more than simply swapping colours or updating logos. Another was implementing real-time chat messaging functionality, which introduced a completely different set of technical challenges around state management, live updates and reliability. Both experiences forced me into unfamiliar territory very quickly and made me realise how much growth comes from taking on work you don’t yet feel fully prepared for.
The technical side of the work was challenging, but what stood out most to me was how much responsibility came with it. I had to think carefully about rollout strategy, user experience, maintainability and how changes in one area could unexpectedly affect another. It pushed me to become far more thoughtful and methodical in the way I approached development work.
This feeling (call it being thrown into the ’deep end’) is something I’ve experienced countless times in my first year at Sentia. And every time, it always begins with the same thing: some worries, some doubt, and a lot of planning. But I couldn’t be more appreciative of those experiences. Having to adapt, work through problems you didn’t even know existed the day before, understand a codebase that’s been touched by more people than I can count on both hands - that’s where I have experienced the most growth.
One crucial element that made these moments manageable, and ultimately successful, was the collaboration with my team. There were plenty of moments where I needed guidance, feedback or a second perspective, and I learned very quickly how valuable strong communication is within a development team. It allowed me to become more confident contributing my own ideas and proposing better solutions when I thought something could be improved. I gained experience speaking directly with clients, managing expectations and balancing what was ideal against what was realistically achievable within time and technical constraints. It becomes a positive feedback loop - the more you learn, the more you suggest. You feel confident to research and ask more questions, diagnose new issues and add those skills to your toolbelt to be implemented into future problems.
After working through experiences like these, I realised the biggest thing I had gained wasn’t just technical knowledge - it was confidence. Confidence in my ability to solve problems, adapt under pressure and take ownership of work that initially felt beyond my level. That feeling of finishing something difficult, hearing that the client is fully satisfied with the work, and recognising how much you’ve grown through it is probably one of the most rewarding parts of what I do.
Looking back, I think that’s what has made my first year as a developer so rewarding. Not necessarily the moments where things felt comfortable, but the moments where they didn’t - the projects that forced me to think differently, communicate better and trust my ability to work through uncertainty. Every difficult task leaves you with something valuable once it’s finished. In my case, these experiences left me with far more than completed projects. They left me with a stronger understanding of how good software is built, how important collaboration really is, and a lot more confidence in the developer I’m becoming.