"Facebook is doing a bad thing with their license" "But it probably won't affect you" Perhaps not the strongest line of argument.
-
-
Replying to @wycats
Ember: license React: Code splitting that is easy and works. My users don't care about licenses. They care about perf.
3 replies 0 retweets 0 likes -
Replying to @lincolnnathan21 @wycats
And your users don't care about licenses the way they also don't care about code splitting. They care about what you ship
1 reply 0 retweets 2 likes -
Yes, and the fact that we ship our entire js bundle at once is bad for our users with slow internet (a lot of them!)
2 replies 0 retweets 0 likes -
Replying to @lincolnnathan21 @wycats
Displaying one less image in our application is more impactful from a latency and transfer perspective than splitting your JS into picos
1 reply 0 retweets 1 like -
Replying to @landongn @lincolnnathan21
It depends a lot on the app and users, but I've definitely seen ppl slow feature dev to get perf benefits their users care less about.
2 replies 0 retweets 2 likes -
Replying to @wycats @lincolnnathan21
It happens. Product and Engineering need to keep each other honest about if their goals and plan match what users actually care about. 1/
2 replies 0 retweets 0 likes -
when it happens because of personal 'feature greed' or when it happens with no data, no measurements, that's what drives me up the wall.
1 reply 0 retweets 1 like -
Replying to @landongn @lincolnnathan21
People lean on the flimsiest data to justify literally years (sometimes) of work to hit latency targets.
2 replies 0 retweets 1 like -
Engineers feel like they have a handle on how to improve latency, when stickiness is often driven by quality features.
1 reply 0 retweets 1 like
But that requires talking to users or Product, and it's so much easier to believe that if you hit a magic latency number you're ...
-
-
... delivering for your users and the company at the same time. Win/win right? Except you've now spent years ignoring your customers.
1 reply 0 retweets 1 like - 1 more reply
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.