I’ll admit it; I’ve become a bit of an architecture astronaut. Moving to a bigger set of problems, it’s just become a natural progression of my toolset. It’s not all the time, but it’s my default course now.

It didn’t always used to be this way. Plenty of my “sites” are basically a single file. Even one of the longest running internal frameworks I’ve written has myriad static calls. But now I shudder at the thought. How am I going to swap that provider out? Where can I mock an interface to avoid hitting the DB on each test case?

When I’ve reached too high, and the air starts to get thin, I come back down a bit. Not everything needs an interface, and an interface with no methods or a single implementation isn’t really an interface to begin with. And for the smaller tasks, the sites where I know it’s quick and it’s small, I’m still not afraid to throw together a few libraries to get the result needed.

So here’s to the astronauts. Bolting together three million parts to get to the moon when people question why a bigger firework wouldn’t work.