This week I get started on a new, massive project. I can't wait.
I'm not sure there's a coherent way to explain the buzz of something like this. We've been in discovery for a while now. I could see the tickets sitting in our Jira backlog, we've been talking about it forever, and now I'm the first one who gets to write a line of code. I'm laying the first brick, and it feels great.
Every new feature carries a bit of that emotion. It's a step into the unknown, a shift away from whatever's been your primary focus for weeks or months toward something entirely new. It feels like a fresh start, with its own set of challenges and hurdles to navigate. But that's the beauty of it. That's where the spark that made me fall in love with this job actually lives.
This one is going to be both challenging and genuinely interesting.
We're moving a legacy part of our product to a properly thought-out React implementation. It lets us sunset software that's been powering that area since long before anyone on the team joined, save a significant amount of money, and give users a far better experience. Much better.
But it isn't purely a cost decision. This feature involves aspects of frontend work I'm not particularly familiar with, and after enough years where the core concepts start to feel the same, biting into something genuinely new like data visualisation is exciting. Sure, I've built charts and graphs before. But this needs to be different. Better thought out. Not "let's match the design," but let's build meaningful visualisations sitting on top of a genuinely complex data infrastructure.
And it doesn't stop there. After a first, fairly static iteration, we'll add two more dimensions. Deep customisation of the section, resizing, drag and drop, custom visualisations and presets, and an AI layer that makes it as simple as telling the agent what you want to see and what you're trying to learn from it.
That's a whole extra layer of complexity, one that will push me to think longer-term, to consider system design and evolution in a way I never really have. For most of my career I built websites and web apps, and once they were signed off and delivered, that was largely the end of them. Here, we're trying to build a foundation sound enough to carry everything that comes after. That challenge is enormously motivating.
For the first time, this feels like a project I need to own properly, top to bottom. I'm not just the new joiner doing his best with whatever tickets land on him. I need to be in real sync with this feature, shape it from every angle, get my hands dirty across the whole stack. This is the step up I've been feeling was due, and I have no intention of slowing down or shrinking from it.
Some of it is still a little foreign to me. But throughout discovery I did my best to follow closely, think through the concepts, and dig into the things I didn't know. There will be areas where I struggle and areas where my experience lets me shine. Either way, this is the moment to gather everything I've worked on this year into a genuine level-up, something I can look back on and feel proud of, both the work and myself.
The time for good intentions and self-motivation is over. Now it's about facts, and delivering work of the highest quality. Now it's time to move that first ticket into progress. To watch our automation drop a message in Slack announcing that a new epic has just been started, by me. To stare at the blank page and start filling it.