Code needs boundaries, but not too manyhttp://therealadam.com/2015/08/15/code-needs-boundaries-but-not-too-many/ …
-
-
@therealadam and when the framework gives you the boundaries, it's a lot easier to color inside the lines. -
@wycats IMO coloring inside the lines is what developers like most about frameworks (besides devs offended by someone else’s lines) -
@therealadam "Boundary" doesn't really capture how hard it is to properly create them, which is why frameworks boost productivity. -
@therealadam Boundaries have to work hard to avoid leaking concerns by accident (especially in dynlangs), and ad-hoc boundaries leak hard -
@wycats location, permeability, and cost of change are so high analysis paralysis sometimes seems better than imposing the wrong boundary -
@therealadam you should only use frameworks if you're doing something that is similar to what others are doing. But that is very common. -
@therealadam that was@dhh's "special snowflake" message. You share boundaries more often than you think. -
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.