KolA
  • Member for 7 years, 2 months
  • Last seen more than a month ago
  • New Zealand
Pitfalls of Domain Driven Design with Entity Framework
9 votes

Treat EF for what it is i.e. data access library which is only slightly more strongly-typed than raw ADO.NET. I wouldn't recommend to model your domain using EF entity classes just like I wouldn't ...

View answer
Efficient techniques to make a clean rename of a Ubiquitous Language term (DDD) throughout codebase
Accepted answer
5 votes

In the absence of any better out-of-the-box tools just keep using global "Find and Replace" and standard IDE refactorings plus practice some discipline to minimize risk of false positives and misses. ...

View answer
Interface/Contracts in separate assembly?
Accepted answer
3 votes

I feel whole purpose of DI is defeated. Why ? Because if MyProj.MiddleTier has hard dependency reference of MyProj.DAL then I cannot simply switch to another persistence technology tomorrow without ...

View answer
How to avoid duplication of types in MVVM
2 votes

DRY principle prescribes to avoid duplication of different pieces of knowledge, not just repeatable blocks of code. Two identical blocks of code can correspond to very different rules and that's ...

View answer
How to combine strict TDD and DDD?
2 votes

Should I strictly let design emerge from tests No. (Domain Driven) Design by definition should emerge from domain requirements. This is bad idea to let anything else to drive your design, whether it ...

View answer
Keep it simple now, or program with the future in mind?
1 votes

It depends. There's a good old-fashioned rule: treat other people like you want to be treated yourself. What would you do if it was your own project and you knew all the priorities? If v2 is ...

View answer
balance between UI responsiveness and avoiding race conditions
1 votes

I'll describe my hand-made approach, I'm not 100% happy with it but it covers many cases and gives some choice between all or nothing. (projects were in XAML and I used Nito Calcualted Properties and ...

View answer
Is DDD only good for batch processing?
1 votes

His example was ... very much an uninterrupted pipeline. Not sure what you mean by "uninterrupted". If you mean "happy path scenario" then this is not true. Primary focus of the book is explicit ...

View answer
How do you keep your unit tests working when refactoring?
1 votes

keeping the testing suite in sync with the codebase during and after refactoring What makes it difficult is coupling. Any tests come with some degree of coupling to implementation details but unit ...

View answer
When is optimization not premature and therefore not evil?
0 votes

"Premature optimization is root of all evil" is something almost all of us have heard/read True. Unfortunately it is also one of the most (maliciously) misused programming quotes of all times. ...

View answer
Where to call OnPropertyChanged
0 votes

I never call PropertyChanged directly, I use this very simple but extremely useful library: https://github.com/StephenCleary/CalculatedProperties/blob/master/README.md It is really a "formula engine"...

View answer
Is using getters in XAML view-models a bad thing?
0 votes

The colleague is wrong. Mutable state should be kept at minimum/normalized and what can be readonly/calculated should be calculated i.e. fewer setters is better. The only good excuse for denormalizing ...

View answer
Why does TDD work?
0 votes

Why does TDD work? It doesn't. Clarification: automated tests are better than no tests. However I personally think that most of unit tests are waste because they usually tautological (i.e. says ...

View answer