Yes, exactly! This is a strategy you could use in the context of creating a layered architecture.
It's a tactical way to implement the layered architecture in a way that's truly decoupled.
A lot of folks could think that just because they have three distinct projects for UI, Biz logic, and Data, that they have implemented proper layering, not realizing that the literal dependencies between classes is quite important.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, exactly! This is a strategy you could use in the context of creating a layered architecture.
It's a tactical way to implement the layered architecture in a way that's truly decoupled.
A lot of folks could think that just because they have three distinct projects for UI, Biz logic, and Data, that they have implemented proper layering, not realizing that the literal dependencies between classes is quite important.