Using a DAO to abstract our ORM from the rest of the application
We’re using MySQL with Sequelize.js as the ORM.
Is this over-abstraction? (And is there a name for it?)
I work on a large Django application that uses CouchDB as a database and couchdbkit for mapping CouchDB documents to objects in Python, similar to Django’s default ORM. It has dozens of model classes and a hundred or two CouchDB views.
Refactoring an existing abstract class and its parameters
I have an abstract class A which declares an abstract method doStuff. Currently there are many classes that inherit from A and implement doStuff.
Does learning to play an instrument improve programming ability? [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
Adding explicit interfaces to Legacy managed C++ code
I have a bit of a challenge and I am not sure how to approach this.
We have a very very large project (that is about 5 years old).
The code base is HUGE so a full refactor is out of the question.
Can too much abstraction be bad?
As programmers I feel that our goal is to provide good abstractions on the given domain model and business logic. But where should this abstraction stop? How to make the trade-off between abstraction and all it’s benefits (flexibility, ease of changing etc.) and ease of understanding the code and all it’s benefits.
Can too much abstraction be bad?
As programmers I feel that our goal is to provide good abstractions on the given domain model and business logic. But where should this abstraction stop? How to make the trade-off between abstraction and all it’s benefits (flexibility, ease of changing etc.) and ease of understanding the code and all it’s benefits.
Can too much abstraction be bad?
As programmers I feel that our goal is to provide good abstractions on the given domain model and business logic. But where should this abstraction stop? How to make the trade-off between abstraction and all it’s benefits (flexibility, ease of changing etc.) and ease of understanding the code and all it’s benefits.
Can too much abstraction be bad?
As programmers I feel that our goal is to provide good abstractions on the given domain model and business logic. But where should this abstraction stop? How to make the trade-off between abstraction and all it’s benefits (flexibility, ease of changing etc.) and ease of understanding the code and all it’s benefits.
Can too much abstraction be bad?
As programmers I feel that our goal is to provide good abstractions on the given domain model and business logic. But where should this abstraction stop? How to make the trade-off between abstraction and all it’s benefits (flexibility, ease of changing etc.) and ease of understanding the code and all it’s benefits.