I'm a web developer with a strong focus on frontend development, and React has been at the center of my professional work for most of my career. I enjoy building interfaces that are not only functional and visually polished, but also accessible, responsive, and pleasant to use.

I originally became interested in Computer Science because of my interest in graphic design and the visual side of creating things for the web. I quickly discovered that a Computer Science degree involves a lot more code than I had anticipated, so I learned to embrace the programming side of it, and eventually found that it gave me the tools to build the things I was interested in in the first place.

That's probably also why CSS has such a special place in my toolkit. My original interest in Computer Science came from an interest in graphic design and the visual side of creating things for the web, so CSS ended up being a natural meeting point between the visual and technical sides of web development. I genuinely enjoy taking an idea or design and figuring out how to turn it into a polished, responsive interface.

If you look at the CSS documentation on MDN, you might think there isn't all that much to it. But believe me, things get considerably more interesting once different properties start interacting with and cascading over one another. It's one of those technologies that looks simple at first, but has a surprising amount of depth once you start digging into it | and that depth is a big part of what makes it so enjoyable to work with.

Web accessibility is another area I'm particularly passionate about and consider one of my areas of expertise. I believe a well-built interface should work for as many people as possible, regardless of how they interact with the web. Accessibility is something I try to consider as part of the development process rather than something to address after a product has already been built.

I'm also a big believer in TypeScript and use it whenever possible. I appreciate the structure it brings to a project, especially as applications grow and become more complex. I've worked extensively with Next.js and have also explored Gatsby and GraphQL through some of my own projects. I'm particularly interested in the idea of combining dynamic data with static generation to build websites that are both flexible and fast.

More recently, many of my projects have been in the Web3 space, which has given me hands-on experience working with technologies such as Ethers, Wagmi, and Viem. I've enjoyed learning how these libraries fit into the frontend development workflow, from interacting with smart contracts and blockchain networks to handling wallet connections and on-chain data. This experience has also given me a better understanding of the challenges involved in building responsive and accessible interfaces for decentralized applications, while still allowing me to work primarily from the perspective of a frontend developer.

I also care about writing reliable, well-tested code and have experience writing end-to-end tests with Cypress. For me, good frontend development isn't just about making something look right | it's about making sure it works well, remains maintainable, and provides a good experience for the people using it.

While frontend is where most of my professional experience lies, I'm also interested in understanding more of what happens beyond the browser. I've experimented with backend development using Node.js, Express, MongoDB, and GraphQL, but I consider this an area where I'm still learning and growing rather than my primary area of expertise. I'm particularly interested in getting more hands-on experience with backend systems and databases such as PostgreSQL.

I'm also currently learning more about DevOps and the processes involved in taking an application from development to production. I've had the opportunity to work with tools such as Grafana and Prometheus, giving me some hands-on exposure to monitoring and observability. I enjoy understanding how the different pieces of a project fit together | from writing the code and managing infrastructure to monitoring, deploying, and maintaining the finished application.

At the end of the day, I care about writing code that is clean, readable, maintainable, and capable of growing with the project. I enjoy learning by building, exploring technologies that interest me, and gradually expanding the range of things I can work on.

If you have a project in mind and think I might be a good fit, feel free to get in touch. I'd be happy to hear what you're working on.