Software Engineer
A software engineer who builds systems that scale, modernizes platforms that matter and ships code that holds up long after the project ends.
Based in Dublin, Ireland, with a presence across Bristol, Groningen and Kathmandu, the work spans FinTech platforms, SaaS products and open source contributions, collaborating with engineering teams across Nepal, Ireland, the Netherlands, New Zealand and the United States.
From leading legacy modernization for global banking clients to architecting microservices in Go, Java and Python, the focus has always been the same. Understand the problem deeply, build it right and make sure the people depending on it never have to think about it failing.
Noticias
(13)
Filtrar: Category Todas las noticias Tutorials Packages Packages Tutorials Packages Tutorials Blogs Packages Tutorials Tutorials Blogs Blogs Blogs
-
Tutorials 13 min
How to Modernize a Legacy Monolith Step by Step Without Taking the Whole System Down
Nben M. 25 May, 2026
Modernizing a legacy monolith doesn’t require a full rewrite or big-bang cutover—just a phased extraction strategy that keeps production running smoothly.
-
Packages 13 min
Why We Chose GORM Over Raw SQL for Data Management in a FinTech Backend
Nben M. 07 Apr, 2026
GORM is not the obvious FinTech backend choice. Here is the reasoning, tradeoffs, and patterns that made it work in production.
-
Packages 6 min
How We Used Chi Router to Structure Clean and Scalable Go Microservices in Production
Nben M. 08 Mar, 2026
Chi gave us idiomatic routing, composable middleware and a structure that held up as our microservices grew. Here is the pattern we settled on and why it works.
-
Tutorials 13 min
How to Structure a Django Service Inside a Go Based Microservices Architecture
Nben M. 06 Feb, 2026
Django and Go are not natural partners, but used deliberately, Django fills gaps that Go services handle poorly.
-
Packages 10 min
How Laravel Sanctum Handles Authentication Cleanly in a Multi-Tenant SaaS Product
Nben M. 08 Jan, 2026
Sanctum works well for single-tenant APIs. Multi-tenant SaaS needs proper token scoping, tenant resolution, and guard setup for production.
-
Tutorials 10 min
How to Design Microservice Boundaries That Do Not Come Back to Haunt You
Nben M. 03 Dec, 2025
Bad microservice boundaries feel fine at the start and catastrophic at scale. Here is how to draw them correctly before the cost of being wrong.
-
Blogs 11 min
What FinTech Engineering Taught Me About Writing Code That Cannot Fail
Nben M. 04 Nov, 2025
Building software where failures cost real money forces you to develop instincts about reliability that general software engineering never demands.
-
Packages 13 min
Why Gin Became Our Go-To HTTP Framework for High Performance Go Microservices
Nben M. 06 Oct, 2025
Gin is not the most idiomatic Go framework, but its performance and developer speed made it a strong fit for our microservices stack.
-
Tutorials 11 min
How to Migrate a Laravel Monolith to Microservices Without Breaking Everything
Nben M. 05 Sep, 2025
Migrating a Laravel monolith to microservices is not a rewrite. It is a controlled extraction process that requires more discipline than ambition to get right.
-
Tutorials 4 min
Building a REST API with Go and Deploying It to Production from Scratch
Nben M. 10 Aug, 2025
A practical walkthrough of building a production-ready REST API in Go, covering project structure, middleware, error handling, database access and deployment.
-
Blogs 9 min
The Real Cost of Technical Debt in Financial Systems
Nben M. 08 Jul, 2025
Technical debt in FinTech is not just a code quality problem. It is a risk management problem with compounding costs that most engineering teams underestimate.
-
Blogs 9 min
What Working Across Five Countries Taught Me About Engineering Collaboration
Nben M. 20 Jun, 2025
Engineering across Ireland, the Netherland and the UK exposed the assumptions that make distributed teams fail and the habits that make them work.
-
Blogs 7 min
What Legacy Codebases Teach You That Greenfield Projects Never Will
Nben M. 02 May, 2025
Working inside a legacy codebase forces you to develop instincts that clean-slate projects cannot replicate, no matter how well-architected they are.
