Code needs boundaries, but not too manyhttp://therealadam.com/2015/08/15/code-needs-boundaries-but-not-too-many/ …
-
-
Replying to @therealadam
@therealadam frameworks are all about coming to a consensus about some useful boundaries so you don't have to think about it all the time1 reply 2 retweets 5 likes -
Replying to @wycats
@therealadam and when the framework gives you the boundaries, it's a lot easier to color inside the lines.1 reply 0 retweets 1 like -
Replying to @therealadam
@therealadam@wycats teams that "gem install" boundaries via frameworks have a head start, since drawing boundaries is very time expensive.1 reply 0 retweets 0 likes -
Replying to @realntl
@therealadam@wycats but OTOH orgs that fail to establish boundaries around application components tend to slow down eventually.2 replies 0 retweets 0 likes
@realntl @therealadam agreed. Treating framework boundaries as the only boundaries eventually will screw you.
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.