What's the longest you've ever been stuck on something, and how did you push through?

The multi-agency architecture for Tiny Steps.

Four different home health agencies needed to use the same platform, but each had different PDF templates, different credential rules, different workflows, different compliance requirements. Building four separate instances wasn't sustainable. Building one rigid system wouldn't fit anyone properly.

I spent over a week trying different approaches. Hard-coded agency switches. Feature flags per organization. Separate config files. Every approach either created maintenance nightmares or couldn't handle the polymorphism in the business rules.

The breakthrough came when I stopped thinking about it as a software problem and started thinking about it as a design problem. The question wasn't "how do I code four different behaviors." The question was "what's the abstraction that makes four different behaviors feel like one."

The answer was config-driven polymorphism. Every agency-specific behavior, PDF templates, credential rules, visibility scopes, routing logic, is driven by configuration, not code branches. Adding a new agency takes configuration, not development. 42 users across four agencies on one platform. Each sees only their data and their templates.

What pushed me through was refusing to accept the first solution that worked. It would have been easy to ship agency-specific if-statements. It would have worked. But it would have meant that every new agency doubled my maintenance burden. I chose the harder solution because I was maintaining this alone, and I knew I'd be the one paying for the shortcut later.