Click here to Skip to main content
15,923,083 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
GeneralRe: WSL can't properly mount USB drives Pin
RickZeeland16-Feb-24 20:02
mveRickZeeland16-Feb-24 20:02 
GeneralIntel and AMD updates for security vulnerabilities Pin
Richard Chambers16-Feb-24 10:33
Richard Chambers16-Feb-24 10:33 
GeneralRe: Intel and AMD updates for security vulnerabilities Pin
obermd17-Feb-24 7:15
obermd17-Feb-24 7:15 
GeneralRe: Intel and AMD updates for security vulnerabilities Pin
charlieg18-Feb-24 6:13
charlieg18-Feb-24 6:13 
GeneralRe: Intel and AMD updates for security vulnerabilities Pin
jochance22-Feb-24 5:49
jochance22-Feb-24 5:49 
QuestionAll high-level classes must depend only on Interfaces Pin
raddevus16-Feb-24 8:46
mvaraddevus16-Feb-24 8:46 
AnswerRe: All high-level classes must depend only on Interfaces Pin
honey the codewitch16-Feb-24 10:42
mvahoney the codewitch16-Feb-24 10:42 
GeneralRe: All high-level classes must depend only on Interfaces Pin
raddevus16-Feb-24 10:56
mvaraddevus16-Feb-24 10:56 
I appreciate the feedback. You're summary is a good one and related to one of the key points made by the MS Unity Application Block PDF that I read, right after my original post.

Quote:
When You Shouldn’t Use Dependency Injection
Dependency injection is not a silver bullet. There are reasons for not using it in
your application, some of which are summarized in this section.
• Dependency injection can be overkill in a small application, introducing
additional complexity and requirements that are not appropriate or useful.
• In a large application, it can make it harder to understand the code and
what is going on because things happen in other places that you can’t
immediately see, and yet they can fundamentally affect the bit of code you
are trying to read. There are also the practical difficulties of browsing code
like trying to find out what a typical implementation of the ITenantStore
interface actually does. This is particularly relevant to junior developers and
developers who are new to the code base or new to dependency injection.


It's interesting because "theoretically" I absolutely love the idea of DI, IoC and writing everything to an Interface.
But, if you like to look at code, it is quite terrible.
There's a project where this has been carried out that is a small(ish) project which has about 8 dependencies (all are Interfaces & the implementations are in separate DLL projects).
To look at the code or debug-step the code you need to create a VStudio solution with the 8 projects as included Projects and then you can step into the code of one or the other.
It's a lot of overhead.

And, yes, I agree with what you said about team size too. If you have nine different people working on each item (1 on the main service and 8 on each dependency) then breaking up is good.
GeneralRe: All high-level classes must depend only on Interfaces Pin
honey the codewitch16-Feb-24 11:50
mvahoney the codewitch16-Feb-24 11:50 
GeneralRe: All high-level classes must depend only on Interfaces Pin
jochance19-Feb-24 12:09
jochance19-Feb-24 12:09 
GeneralRe: All high-level classes must depend only on Interfaces Pin
raddevus20-Feb-24 2:44
mvaraddevus20-Feb-24 2:44 
GeneralRe: All high-level classes must depend only on Interfaces Pin
jochance22-Feb-24 5:59
jochance22-Feb-24 5:59 
GeneralRe: All high-level classes must depend only on Interfaces Pin
hpcoder224-Feb-24 20:49
hpcoder224-Feb-24 20:49 
AnswerRe: All high-level classes must depend only on Interfaces Pin
trønderen16-Feb-24 11:12
trønderen16-Feb-24 11:12 
GeneralRe: All high-level classes must depend only on Interfaces Pin
raddevus17-Feb-24 4:25
mvaraddevus17-Feb-24 4:25 
AnswerRe: All high-level classes must depend only on Interfaces Pin
PIEBALDconsult16-Feb-24 11:46
mvePIEBALDconsult16-Feb-24 11:46 
GeneralRe: All high-level classes must depend only on Interfaces Pin
raddevus17-Feb-24 4:30
mvaraddevus17-Feb-24 4:30 
GeneralRe: All high-level classes must depend only on Interfaces Pin
PIEBALDconsult17-Feb-24 5:48
mvePIEBALDconsult17-Feb-24 5:48 
AnswerRe: All high-level classes must depend only on Interfaces Pin
englebart16-Feb-24 13:51
professionalenglebart16-Feb-24 13:51 
GeneralRe: All high-level classes must depend only on Interfaces Pin
raddevus17-Feb-24 4:36
mvaraddevus17-Feb-24 4:36 
GeneralRe: All high-level classes must depend only on Interfaces Pin
englebart17-Feb-24 14:20
professionalenglebart17-Feb-24 14:20 
GeneralRe: All high-level classes must depend only on Interfaces Pin
jschell19-Feb-24 6:01
jschell19-Feb-24 6:01 
JokeRe: All high-level classes must depend only on Interfaces Pin
englebart19-Feb-24 6:25
professionalenglebart19-Feb-24 6:25 
AnswerRe: All high-level classes must depend only on Interfaces Pin
RickZeeland16-Feb-24 20:10
mveRickZeeland16-Feb-24 20:10 
AnswerRe: All high-level classes must depend only on Interfaces Pin
Sander Rossel17-Feb-24 0:33
professionalSander Rossel17-Feb-24 0:33 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.