Search Results

I think you are missing the point. Its not saying you should rename the setter and getter, but to have methods which add and remove items from the fridge. ie public class Fridge { private int num …

I would side with your enemy on this one. The 'create a database and table logic' is clearly technically a separate responsibility from the 'get data from database' logic. You can imagine the creati …

Just did some googling and it seems the terms were invented by Ole-Johan Dahl and Kristen Nygaard for their Simula programming language We chose the terms “class” and “objects” of classes for our …

No I think it's fairly common for events to pass the object raising the event and the event arguments to a handler. I've seen it said that this is so events can be bubbled up through several handlers …

Don't try to make objects that simulate real world equivalents Make objects that hold data that goes with their methods In your materials example, you don't actually say what the data is used for. …

It's unusual for a single object to have 50 variables that wouldn't be better grouped into sub objects. For example a UK address has 14 fields. You could imagine that an address class that covered ad …

I think you have two options here. Best practice. Create objects which match the json returned by/sent to the API and serialize/deserialze these objects when you make calls or receive responses. Hid …

First create an employee struct containing the properties of the conceptual employee. Then create a database with matching table structure, say for example mssql Then create a employee repository Fo …

I think you are just going in circles here. You can either use an ADM approach with one or more services and objects with no logic ie Service { StartEngine(Engine e) PressPedal(Pedal p) ... } …

Normally I would say your "Backing class" is a "Repository" and should follow that pattern. For which i would normally recommend one per database UserDataRepository { GetUserById(id) GetAllRol …

I would remove the Dependency of IUserPublishedInfoInitializer on IDbRepository. Instead inject this as a construction parameter into the concrete UserPublishedInfoInitializer. your dependency graph …

2 is the mediator pattern. You can get around the tight coupling by: Injecting a IMediator interface with just 'publish' and 'listen' By using a factory method to create the buttons and wire up th …

OK so once you have the data in memory its trivial to convert stops to legs and vice-versa. Your problem will come when you are searching you database for particular sets of routes. For example, I am …

This looks like the repository pattern, which is generally considered to be a good thing, separation of concerns between your business and data layer. The reason to put all these methods together in a …

I think the answer will depend on what you are trying to achieve other than writing files. Lets leave out the POJOs for the moment, you read data from a DB and write it out to a specific file format …