- Working hard and enjoying every minute of it.
- using the asp.net lego blocks to create a synchronized Kanban board.
- Tip to become a successful software engineer.
- ASP.Net Web Config Transform Console Utility released on nuget
- Are your unit tests still hard to read ? – Should Assertion Library
- Using sql compact for integration tests with entity framework.
Category Archives: Design
While plowing through some AutoMapper support issues this weekend, I got a rather troubling one, where a developer got a rather scary exception message: “Operation could destabilize the runtime” Well that’s disturbing. It all came about because they were trying … Continue reading
When is Poor Man’s Dependency Injection appropriate? Only in legacy code situations. That’s it. I was called out appropriately on forgetting this, but legacy code, where I have to apply dependency-breaking techniques, does not always afford the opportunity to apply … Continue reading
If you’ve ever asked, or been asked, for an example to illustrate a software design principle, you know how frustrating it can be to work with a contrived example. There is rarely any depth to the example, and it lines … Continue reading
One of the core XP practices that resonated with me quite early on was the concept of simple design. When I learned TDD, this practice was further refined with the concept of doing the “simplest thing that could possibly work”. … Continue reading
At last night’s ADNUG talk, Jeremy Miller talked about Convention over Configuration, and many of the principles the Rails community embraces. He showed a few examples of opinionated software, such as FubuMVC. One thing I would have liked more conversation … Continue reading
Here at Los Techies, we talk a lot about SOLID principles and design. Two of the principles that have always resonated with me are the Single Responsibility Principle and the Dependency Inversion Principle. With the two together, the need for … Continue reading
This has been discussed many times before on various mailing lists, and I’m sure there are blog posts about it that are eluding me currently, but I’ll put it out there anyway. Interfaces on entities are an anti-pattern (when … Continue reading
Lately my co-worker asked me to pair with him and make a code review with him of one of his projects. After having spent some hours on refactoring this legacy application together with my co-worker I want to share some … Continue reading
In the previous two posts I discussed the S of S.O.L.I.D. which is the Single Responsibility Principle (SRP) and the D of S.O.L.I.D. which corresponds to the Dependency Inversion Principle (DI). This time I want to continue this series with … Continue reading