Hands-On Dependency Injection in Go

When to compromise

Having a great user experience is a desirable goal, but is not a necessity. There are always going to be situations where the UX needs to be compromised. The first and perhaps most common situation is team evolution.

As the team evolves and becomes more experienced with Go, it will inevitably find that some early software patterns no longer seem as effective. These might include things such as the use of global, panic, and loading configurations from environment variables, or even when to use functions rather than objects. As the team evolves, so does their definition of both good software and what is standard or intuitive.

The second, and in many cases, an overused excuse for poor UX, is performance. As we saw in an early ...