Is it bad to have classes as properties of all other classes?
I’ve been making MVC programs for work (I’m an intern) and I feel like I’m doing a pretty good job at abstraction, single responsibility, etc. But I have this feeling about how I keep making objects properties of other objects and I’m not sure if it’s a bad thing.
Validating objects with each other – Design Pattern needed
I am running a zoo application.
Validating objects with each other – Design Pattern needed
I am running a zoo application.
Empty virtual method on base class VS abstract methods
I couldn’t find a question that was not too specific to some case, so I’ll try to make this very generic.
In Android can we let a fragment know other fragments?
I think I have found contradictory design guidance within the Google Android documentation on fragmentation.
In Android can we let a fragment know other fragments?
I think I have found contradictory design guidance within the Google Android documentation on fragmentation.
Which relationship is more natural?
Have a quick question on how to best structure something for my Java project:
In which step of a software development life cycle I should design my computing algorithm?
In software design, we usually take care of UML diagrams and architecture design.
In which step of a software development life cycle I should design my computing algorithm?
In software design, we usually take care of UML diagrams and architecture design.
In which step of a software development life cycle I should design my computing algorithm?
In software design, we usually take care of UML diagrams and architecture design.