Does decoupling trump DRY in REST?
I am building a REST API to expose most of functionality of an existing Java API. Both APIs are for internal use within my organization; I do not have to design for external use. I have influence over both APIs but am implementing the REST one. The Java API will continue to be used for local applications (it’s not being “retired”), but the REST API will be used for significant new development.
Many small classes vs. logical (but) intricate inheritance
I’m wondering what is better in terms of good OOP desing, clean code, flexibility and avoiding code smells in the future. Image situation, where you have a lot of very similar objects you need to represent as classes. These classes are without any specific functionality, just data classes and are different just by name (and context) Example:
Validation of the input parameter in caller: code duplication?
Where is the best place to validate input parameters of function: in caller or in function itself?
Better OOP in Javascript – multiple methods or methods with options?
Let’s say I have an object like this:
Best practices for sharing tiny snippets of code across projects
I always try to follow the DRY principle strictly at work; every time I’ve repeated code out of laziness it bites back later when I need to maintain that code in two places.
Reasoning to wait until third time in the Rule of Three?
I just came across the article “Rule of Three” in wikipedia
How to avoid code duplication across unrelated projects [duplicate]
This question already has answers here: Best practices for sharing tiny snippets of code across projects (12 answers) Closed 11 years ago. I’m a contractor at a large Telco where I’m usually working on several different projects at once. The VCSs I use (mainly git and mercurial) tend to make me keep the code bases […]
project with 2 types of interfaces performing different jobs, should they use the same BLL and DAL?
I am working on a project that has two interface (web and desktop), they are not performing the same tasks but they use the same BLL and DAL, the web part using 100% of the BLL and DAL, while the desktop only needs to know about 20% of the BLL and DAL.
Practices for domain models in Javascript (with frameworks)
This is a question I’ve to-and-fro’d with for a while, and searched for and found nothing on: what’re the accepted practices surrounding duplicating domain models in Javascript for a web application, when using a framework like Backbone or Knockout?
Practices for domain models in Javascript (with frameworks)
This is a question I’ve to-and-fro’d with for a while, and searched for and found nothing on: what’re the accepted practices surrounding duplicating domain models in Javascript for a web application, when using a framework like Backbone or Knockout?