"legacy" is an important word. I aim to work on software that is 3+ years old but isn't "legacy."
-
-
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 -
I'm just not sure what you think we aren't understanding?
2 replies 0 retweets 0 likes -
I also work on a long-term app that started four years ago :)
1 reply 0 retweets 1 like -
can you relate when someone says, "we have a huge rails app and aren't productive anymore?"
1 reply 0 retweets 0 likes -
I have experienced that, yes.
1 reply 0 retweets 0 likes -
I believe that Rails would benefit from its leadership taking on the task of understanding how that happens.
1 reply 0 retweets 1 like -
that was really my original point; that learning from Rails cuts both ways. And I don't see that understanding ...
1 reply 0 retweets 2 likes -
... in the "magnificent monolith." Or when folks wanting a different arch style are dubbed "peddlers of complexity"
5 replies 0 retweets 2 likes
if you want to propose something, it's important to try to tackle both sides at the same time.
-
-
the args you're referring to are in response to years of people who refuse to grapple with convention over configuration.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.