but instead, we are re-litigating the "complexity wars" over and over again.
-
-
this is right where the crux of the issue is, I think. We all want simplicity but don't agree on what it means
3 replies 0 retweets 1 like -
a strong divide I see is between those who work on many projects for a short term vs. few projects, long term.
1 reply 0 retweets 2 likes -
so I think Rails leadership would benefit equally from learning what makes Rails so unproductive for many orgs
2 replies 1 retweet 2 likes -
The leadership is pretty representative. A lot of us work on large legacy apps.
2 replies 0 retweets 2 likes -
"legacy" is an important word. I aim to work on software that is 3+ years old but isn't "legacy."
2 replies 0 retweets 1 like -
I'm using it to refer to a large codebase that has been touched by many people. Poor choice of word, sorry
1 reply 0 retweets 0 likes -
and believe me I'm not nitpicking out of being pedantic :) I really think it's in Rails best interest to understand
4 replies 0 retweets 1 like -
how rails and its integration with ActiveRecord can constrain many projects long term. The point in time when...
1 reply 0 retweets 0 likes -
... ORM coupling is irreversible comes before productivity stalls. Many folks attribute the slowdown to "legacy."
4 replies 0 retweets 0 likes
Trust me, I understand this problem (and some of its roots) better than just about anybody.
8:23 AM - 26 May 2016
0 replies
0 retweets
0 likes
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.