Search Results

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 …

No it not a great idea. You have some very specific requirements and if this fits your needs then great. But generally making a class called SomethingHelper and putting a bunch of static methods in i …

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 …

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 …

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. …

No. Using Age instead of int for age makes sense because you want to have extra stuff on your age object that can be useful eg. public class Age { TimeSpan AgeAsTimeSpan() ... Validate() ... / …

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 …

Lets coin some terms. If you put your methods on the same object as your data then you are doing classic Object Orientated Programming (OOP). If you have no methods on your data objects and instead p …

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 …

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 would remove the Dependency of IUserPublishedInfoInitializer on IDbRepository. Instead inject this as a construction parameter into the concrete UserPublishedInfoInitializer. your dependency graph …

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 …

Security is a "Cross Cutting" requirement. You shouldn't code it into your classes with the rest of the business logic. Map out your data model create services with the methods you need for your bus …

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 …