Pages

▼
Showing posts with label di. Show all posts
Showing posts with label di. Show all posts
2016-09-15

Go for C# developers: Where to define interfaces

›
When writing Go code the general guideline is not to create interfaces unless it is really needed. A good example would be an interface with...
2 comments:
2016-09-08

Another example on ways to to make your code testable

›
Before you go crazy on me screaming that making code testable for the sake of testability is bad I'd like to agree. However testable cod...
2016-02-04

Books, Mocks and Open Source

›
So time to look back again and update some old opinions from May 2008 . This time I'd like to talk about three old articles.
2015-06-18

Timetravel in C# done right

›
Testing things where you need to fake time is not hard given the right abstractions . That is why when I read this article I felt really sa...
5 comments:
2015-01-08

The I have no idea what I'm testing anti-pattern.

›
It is no secret that I'm not a big fan of service locators in general, but even if you are a fan of those there is a pattern I really do...
2014-08-21

IoC - good, bad and ugly

›
I was reading this article that is doing a pretty good job at explaining in what situations an IoC container saves the day. And even though...
8 comments:
2013-12-05

Abstracting time

›
Probably one of the most common tight couplings I see is a dependency on system time, i.e. using DateTime.Now or DateTime.UtcNow directly in...
2013-10-17

Dependency injection with IObservable

›
Just when I started working on my little toolbox I read this series on dependency injection for events which was great inspiration.