Tagged Questions
0
votes
0answers
133 views
DRY on API specifcations?
When developing a new RESTful application, I generally:
Define tests
Define routes [ e.g.: RESTful CRUD; namespaced on /api/users ]
Define models [ e.g.: "Users" ]
Define forms [ e.g.: in ...
1
vote
1answer
146 views
Further decoupling using static libraries
I've been thinking for a while about reasons that prevent a lot of programmers — myself first of all — from writing clean, modular and expressive code while developing, for example, CocoaTouch apps.
...
4
votes
3answers
191 views
Where should I place my interface?
I have an interface to communicate with a DB (actually it is not a database, but this is to give a concrete example):
interface DbInterface{
Result sendQuery(Query q);
}
And I am trying to ...
5
votes
4answers
516 views
Architecture suggestions on a multi-project multi-database 'intranet'
Here is the situation I have inherited:
We have approximately 10 websites (Asp.net web forms) that each have their own database.
Each of these databases houses some site specific data, and each has ...
0
votes
3answers
348 views
Reuse the data CRUD methods in data access layer, but they are updated too quickly
I agree that we should put CRUD methods in a data access layer， However, in my current project I have some issues.
It is a legacy system, and there are quite a lot CRUD methods in some concrete ...
7
votes
4answers
2k views
Abstract methods vs instance variables for reusable objects
I have quite a bit of Java code that I'm re-working to be re-used. The problem is that there are many pieces that are project specific so there are ends up being a higher level of coupling between ...
10
votes
7answers
881 views
Rule of thumb for cost vs. savings for code re-use [duplicate]
Is it a good rule of thumb to always write code for the intent of re-using it somewhere down the road? Or, depending on the size of the component you are writing, is it better practice to design it ...
