Coupling vs. Cost
Previous post: Media Types, Plumbing and Democracy
Next post: Banff in Winter
HTTP, REST and some Cycling
-
Recent Posts
-
Recent Comments
- Mike Pearce on Another REST Anti-Pattern
- Facebook BigPipe in an Async Servlet on BigPipe Done in Node.js
- Subbu Allamaraju on Using PATCH
- Michael Hausenblas on Using PATCH
- Simon Occoner on JSON as a General Purpose Alternative?
- Simon Occoner on JSON as a General Purpose Alternative?
- Subbu Allamaraju on RESTful Web Services Cookbook Released
- Colin Jack on Media Types, Plumbing and Democracy
- Colin Jack on Media Types, Plumbing and Democracy
- Emmanuel Bastien on RESTful Web Services Cookbook Released
Get smart with the Thesis WordPress Theme from DIYthemes.
{ 5 comments… read them below or add one }
why it takes more cost to reduce coupling ?
You may be right if you only consider initial development costs. However, the longer the project, the more this graph starts to reverse over time.
True. After looking at some debates on "let's build completely decoupled" systems, I had to make a point :)
I think you’re missing a critical dimension.
http://blog.kevburnsjr.com/coupling-vs-cost-vs-time
That’s a good picture.
{ 1 trackback }