There is only one corner of this universe you can be sure of improving, and that is your own self. ~Aldous Huxley
I'm a Software Engineer & Consultant at Mantel Group, where I specialise in crafting robust solutions using a wide range of technologies. With a penchant for both the intricacies of software development and the broad strokes of platform & infrastructure, I navigate the tech landscape with a cloud-first approach.
I am very passionate about software, and I almost always have a personal/collaborative/open-source project that I'm working on. Outside of work, I also do a wide range of activities. Bouldering 🧗, reading 📚, Muay Thai 🥋, motorcyles 🏍️, hiking 🥾, and horticulture 🌵 are just a few of my hobbies!
Eventurely, a Nuxt web app for personal event management. In the background this is using a Dotnet API and Golang auth server (powered by Supertokens). I'm planning to host it all using Azure infrastructure, which will be built with the Pulumi.
Nuxt, authn/authz, Pulumi, and more about Azure services.
Anything and everything! A few of my favourite focus points are:
- Projects focused on creating developer tools that improve productivity & code quality.
- Contributions to open-source projects making a difference in the tech community, especially those related to DevOps tools.
- Educational content creation, such as tutorials or blog posts, to share knowledge on C#, Go, cloud technologies, etc. Feel free to reach out with any ideas!
Finding a good auth provider for Nuxt & Dotnet that allows custom UIs in its free tier. Currently, my project uses a separate Golang API for Supertokens auth, but this requires extra hosting and a reverse proxy. Here are other options currently on my radar and my reasons for not (yet) using them:
- Auth0: Allows "custom branding" on one of their templates, but (to my understanding) does not allow creating your UI from scratch and adding auth using an SDK.
- Kinde: Same reason as Auth0.
- Lucia-Auth: Requires setting up a database to be used by the frontend server (ie. Nuxt). I would rather store the auth/session data in the same database as my backend server (ie. Dotnet) is using for all other data.
If you think one of these is incorrect, please reach out! I'd love to hear that it's easier than I thought :)
Something you think I can help with. Here are some ideas:
- Transitioning from monolithic architectures to microservices (or the opposite): strategies, challenges, and lessons learned.
- Tips for effective remote collaboration within development teams, especially in a distributed, global setup.
- My experience with platform/DevOps and how I balance it with software engineering roles.
As a consultant, I get exposure to a broad range of tools. For an up-to-date list of my top skills, please see my CV
For a more comprehensive list of the tools I've worked with, see the badges at the bottom of this page.
- LinkedIn: broderick-westrope
- Email: [email protected]
A more comprehensive list of tech, tools, and languages I've worked with. This list is not exhaustive, but it's a good start!