At the very least you were strongly playing to that crowd.
-
-
.
@onlydole OO vs. FP hasn't been a real "war" in decades. But new programmer philosophers keep feeling the need to re-fight it. -
As a whole and tear down the real problems we’re seeing, or educate on a better “proper” way of doing things too.
-
the problem is that the blog era gave way to the Twitter era, where nobody is ever rewarded for thoughtfulness.
-
this gives a great advantage to faux-simplicity.
-
And we can forget the shoulders of giants that we stand upon in some cases too…I feel that is a commonly forgotten reflection.
-
The perpetual sin of the programming world is to not only forget what our elders taught us, but to forget they existed.
-
Amen to that…it’s seriously obscene. The best advice I’ve ever gotten is to study the history of our craft.
End of conversation
New conversation -
-
-
this is right where the crux of the issue is, I think. We all want simplicity but don't agree on what it means
-
a strong divide I see is between those who work on many projects for a short term vs. few projects, long term.
-
so I think Rails leadership would benefit equally from learning what makes Rails so unproductive for many orgs
-
The leadership is pretty representative. A lot of us work on large legacy apps.
-
"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
-
and believe me I'm not nitpicking out of being pedantic :) I really think it's in Rails best interest to understand
-
I'm just not sure what you think we aren't understanding?
- 8 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.
I'd prefer to see no one ever truly happy with an OSS project and for things to always be changing