FYI just today I halted deployment to production because of frame-rate regression caused by JS code change. Fortunately, our test system caught this before deployment, and the offending commit was reverted.
-
-
I'm not saying that we're already where we want to be. But we are moving forward, while having safety nets (tools and processes) to prevent us from falling backwards
1 reply 0 retweets 1 like -
Replying to @DanShappir @brucel
That's so critical. Excited to hear about your progress. Is there a target budget you're trying to hit?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @brucel
In our context, talking about a target budget is challenging, because we're a fairly open-ended platform, where users have lots of freedom when building their own sites using our tooling. For example, they can put as much media, and now also scripts on their sites as they want
1 reply 0 retweets 0 likes -
Also, we have > 100M existing websites that need to continue to look and work exactly as they have before whenever we update our service
1 reply 0 retweets 1 like -
But yes, we do have budgets. Though we're currently focused more on time to FMP than to TTI. Hope that won't make you too angry with me ...
1 reply 0 retweets 1 like -
Replying to @DanShappir @brucel
Not angry! Everybody starts somewhere. TTI has only really come into focus with the shifting device landscape.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @brucel
And I found your post very thought-provoking. Though basically telling developers "you need to write less code!" is a challenging proposition. Managers, PMs, devs are all incentivised to add features and capabilities to products, not to trim them down.
1 reply 0 retweets 1 like -
Replying to @DanShappir @brucel
I think this perhaps confused. I'm saying ship less code, not write less code. They can be related, but don't need to be to the extent that i'm seeing today.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @brucel
Yeah, but shipping less code while writing more code is hard! And it's not something most devs are taught to do. It's a skill mostly required for web and embedded systems. And embedded system devs have years of practice in this, which web devs currently do not.
1 reply 0 retweets 0 likes
I think this is the role of good management. Management sets constraints and trusts engineers to sort out good solutions. We need to communicate the perf constraints better. I trust developers to do the right thing when they know what the goal is.
-
-
Replying to @slightlylate @DanShappir
Good. I thought you chaps should chat. (Fyi, my contract at Wix has finished. Just like to introduce good people.)
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.