Why we choose the right tool for the job, not the trendy one
From PHP to Python, C# to Go, every project gets the language and framework that fits. A look at how we make that decision and why "stack agnostic" is more than a buzzword.
— Category
Engineering
Software development, architecture decisions, and technical deep-dives.
Engineering
Engineering
Why we standardized our entire MSP stack on Laravel
From ticketing to quoting to client portals, every piece of internal tooling now runs on one framework. What worked, what did not, and why we will not regret it.
Engineering
Building an internal tool with Laravel and HTMX
A walkthrough of building a small internal tool with Laravel and HTMX. Why HTMX often beats a full SPA for line-of-business apps.
Engineering
Migrating off legacy line-of-business apps without a forklift
The 1998 line-of-business app still works. The vendor is gone. The hardware is dying. How to migrate without a high-risk forklift project.
Engineering
Federated identity for organizations that have never had it
A primer on federated identity for organizations still managing accounts in 12 different systems. What changes and why it matters.
Engineering
Designing internal tools that people will actually use
Internal software lives or dies on adoption. Most of it dies. Lessons from building tools that people actually use.
Engineering
What we look for in a software project before we say yes
Not every software project should be built. Here is the discovery conversation we have before we agree to build something.