No time spent wondering if we'd have been better off with another fwk. No time planning and executing total rewrites.
-
Show this thread
-
We still upgrade Ember every six weeks, and have added significant new UI features and UI refreshes. Tech debt is decent 5 years on.
1 reply 0 retweets 5 likesShow this thread -
(we try to upgrade every six weeks and are only ever behind because we didn't get to it yet, not because of incredible difficulties)
1 reply 0 retweets 4 likesShow this thread -
I'm pretty happy that we've maintained a culture focused on user value rather than adding value by abandoning and rewriting.
2 replies 1 retweet 33 likesShow this thread -
Replying to @wycats
The greatest fallacy of front end development is "We'll be so much better suited to deliver value if we flush all existing value, first"
1 reply 10 retweets 27 likes -
Definitely think it's a bit more nuanced than that. In some cases it is 100% untenable to progress from the current state of things.
1 reply 0 retweets 1 like -
Replying to @maxdeviant @landongn and
But I guess the goal is to never reach the point where a full-rewrite is the best option (because let's face it, sometimes it is)
1 reply 0 retweets 1 like -
To me it's all cost/value if it's easier and more cost effective to gain back value by shipping less debt, the effing do it.
2 replies 0 retweets 4 likes -
fixing what got your team into the mire of leveraged hacks that ran up your debt is step one. rewriting won't help unless you address roots
2 replies 1 retweet 5 likes -
Replying to @landongn @TheLarkInn and
_so very many times_ a rewrite is pitched as fixing the team issues, rather than making the harder commitment
1 reply 1 retweet 3 likes
BOOM.
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.