Sequential coupling in code
- by dotnetdev
Hi,
Is sequential coupling (http://en.wikipedia.org/wiki/Sequential_coupling) really a bad thing in code?
Although it's an anti-pattern, the only risk I see is calling methods in the wrong order but documentation of an API/class library with this anti-pattern should take care of that. What other problems are there from code which is sequential? Also, this pattern could easily be fixed by using a facade it seems.
Thanks