- Do you spend hours playing your game to verify your changes?
- Are you spending more and more time in the debugger?
- Are you forever chasing unassigned references and broken prefabs?
- Does changing your codebase feel like moving mountains?
- Are you sinking into spaghetti?
- Are you wondering what happened to your productivity?
If so, Uniject might be able help you - even if you never write a single test!
I’ve posted before about Uniject, which I introduced as a way to take the pain out of unit testing.
But by structuring your code using dependency injection, and delegating object construction to an inversion of control framework, you will be adopting patterns that are de facto elsewhere in the software industry, and have been endlessly proven to improve the structure of your codebase.
I have written a new post that explores one of the example projects that comes with Uniject, and I would love to know if it makes any sense to anyone!
Uniject is free and its on Github