Explore >> Select a destination
|
You are here 
|
tech.trivago.com | ||
| | | | |
blog.martinig.ch
|
|
| | | | | Informations and opinions about software architecture, developers on call, holacracy, Scrum, continuous testing, product management, saying thank you, tech leadership, customer journey maps, code reviews, code sharing, good bugs, android testing and open source project management. | |
| | | | |
benoitpasquier.com
|
|
| | | | | To be sure new code won't break old one already implemented, it's best practice to write unit tests. When it comes to app architectures, it can be a challenge to write those tests. Following an MVVM pattern, how to unit test a view and its viewModel? That's what I would like to cover here using dependency injection. | |
| | | | |
sookocheff.com
|
|
| | | | | Inversion of Control (IoC), also known as Dependency Injection (DI), allows an object to define their dependencies as constructor arguments (strictly speaking, you can set these dependencies as properties, but the examples I will use today are constructor-based). This is the inverse of the object itself controlling the instantiation or location of its dependencies, hence the name Inversion of Control. Let's look at an example from Stackoverflow using a text editor with a spell checking component: | |
| | | | |
pragprog.com
|
|
| | | Use domain-driven design to effectively model your business domain, and implement that model with F#. | ||
