Comment by Filip Milovanović on Repository and Service Interfaces in an...
@SamuelObisesan Thank you for taking the time to improve the answer. I've accepted most of your edits, but I elected to rephrase some parts of the answer for clarity. There was one edit that didn't...
View ArticleComment by Filip Milovanović on Why is a test coverage type called "code...
Seems like the source of the confusion is simply a quirk of the language: "X coverage" doesn't have to imply "coverage (of something) by X", it can also mean "coverage of X (by something)". In either...
View ArticleComment by Filip Milovanović on Code reusability/inheritance introduces...
Declare those internals as separate classes. You can then either inherit them or compose them into your object. Then write tests for those classes once (if you're using inheritance and the base class...
View ArticleComment by Filip Milovanović on Do I need to create an interface for every...
"which I think means I should create an interface for each service" - it does not mean that. The first point to keep in mind is: this shouldn't be done mechanistically - you actually have to think...
View ArticleComment by Filip Milovanović on DDD - When a single physical entity in the...
"My question is ..." - the whole point of BCs is that building it all as one big application would result in a complicated mess. Instead, after your analysis of the way the business operates, you...
View ArticleComment by Filip Milovanović on Is it better to pass a specific “context”...
Generally, it's a good idea to minimize what each chunk of code with a well defined purpose depends on, but you also don't want to pay for that with a high maintenance cost, if you can avoid it. Now,...
View ArticleComment by Filip Milovanović on When DI goes too deep - what is another...
Game developers today mostly prefer an approach called Entity-Component-System (ECS), so look that up. Many will say that this is a completely different paradigm compared to OO, but I'm not convinced,...
View Article