It's been almost a year since I last published anything here. I've had quite a few things I've wanted to write about, but somehow never got around to it. A lot has happened since then, so I figured it was time to share a few updates.

For starters, I've moved on from my previous role as a Product Engineer, where I worked on a platform for managing infrastructure and deployments across multiple cloud environments. I'm now at a data infrastructure company, where I work at the intersection of engineering, product, and design, helping shape and deliver features for an ETL data management platform.

It's been an interesting transition. While the domains differ, some problems overlap, especially around making complex, fragmented systems easier to work with.

I've also been working with Clojure and ClojureScript, which is quite a change from the JavaScript, TypeScript, and PHP/Laravel ecosystems I've spent most of my time in. There's been a learning curve, but it's been interesting to approach familiar problems from a different perspective. I hope to write more about my experience with the languages and ecosystem at some point.

Another big change has been how much my engineering workflow has evolved. It's almost impossible to talk about what's changed over the past year without mentioning AI. I use AI throughout the development process, from exploring implementation approaches and understanding unfamiliar code to debugging issues, reviewing changes, and spotting potential problems.

I've found these tools useful when working through problems that involve understanding how different parts of a system fit together. Being able to explore possible approaches, trace existing behaviour, and investigate issues with AI assistance has made certain parts of the development process much more efficient.

That said, it's not always straightforward. These tools can get things wrong, make incorrect assumptions, and suggest changes that don't quite fit the codebase. There's still real value in understanding the problem, reviewing suggestions, and knowing when something doesn't make sense. These tools are evolving rapidly, and I'm curious to see how they'll continue to shape the way we build software.

Outside of my regular work, I've also been exploring Kubernetes and a few other areas of platform and infrastructure engineering. I still have a lot to learn and experiment with, and I hope to share more about those experiences in the coming weeks.

More generally, I'd like to start writing regularly again. Not necessarily just technical posts, but also shorter posts about interesting problems I've encountered, things I'm learning, and observations from my day-to-day work.

I have a lot I'd like to write about, so hopefully I won't have to wait another year to publish something here.