Search Results

In my opinion, it makes no sense to make Document an abstraction but have it be used through a separate class. If you intend to make the implementation of Document private, then the Cursor is part of …

No matter how you design your code, there always exists a requirement that'll force you to alter the functionality. … If you keep your design modular, even if new additions require significant amounts of rework, you'll at least be fairly confident you're not inadvertently breaking completely unrelated functionality. …

doesn't support it; if that's the case, it's not so much a failing in your design as it is a shortcoming in your language of choice. …

Writing code is a process of discovery - just like no plan survives contact with the enemy, every design will have flaws that are only caught once you start implementing it. … Even if you miraculously get the design correct now, there's no guarantee it'll still be relevant later, as you said. In short, it's a slipperly slope. …

Parse the config file and create an object representing the config file's values. Then you can decide how to construct Foo, Bar, and Baz based on the the values of the object's fields.

In my opinion the former makes more sense if there's not much you can sensibly do without knowing whether you have an A or B. If you wanted to unconditionally get the string with the former declaratio …

A pure function could still be an implementation detail. Although the function may cause no harm (from the point of view of not breaking important invariants/contracts), by exposing it both the author …

What I don't understand is this: Abstractions can be superclasses or interfaces. If so, why are interfaces specifically praised for their ability to allow loose coupling? I don't see how it's differe …

An alternative to an iterator is to pass in whatever you want to do with the color as an argument to transformColor. void transformColor(Color original, Color target, int duration, int steps, Functio …

There's always a requirement your design can't accommodate. …

Result, or as it's known in functional languages, Either, is only marginally different from Optional, so your final design should have roughly the same API. …

There is a deeper issue here: the fact that C# and Java insist most/all types must be distinguishable by name rather than structure: e.g. class MyPoint2D and class YourPoint2D are separate types even …

Consider using delegates instead of abstract classes. The Template Method pattern is mostly a hack to work around a language's lack of first-class functions. So instead of overriding "execute", pass i …

//violates the ISP, because it has to implement it, but it's not using it, //just passes the operation public ITearResult tear() { return page.tear(); } This is not correct. The decorator is usi …

Consider this solution: interface IDevice { void PerformA(); int GetB(); } interface INewDevice : IDevice { bool CheckC(); } class DeviceModel1 : INewDevice { ... } class DeviceMo …