Conversation

Notices

1. Embed this notice
   Alex Russell (slightlyoff@toot.cafe)'s status on Sunday, 24-Dec-2023 15:09:59 JST Alex Russell

   *"no one ever got fired for choosing React"* is, AFAICT, not true today, and never has been.

   I've witnessed entire teams get flushed and VPs get unceremoniously booted on the other side of grand React redesigns tanking revenue and conversions.

   None of those folks talk publicly about how it went down because doing so would simultaneously devalue the thing they've invested in and hurt their own employability within that world. And so we bumble on, omerta in tact.

   • Embed this notice
     Alex Russell (slightlyoff@toot.cafe)'s status on Sunday, 24-Dec-2023 15:09:57 JST Alex Russell

     in reply to

     • Gödel Escher Spock🦿

     @adamhill A cultural failure to value the marginal user and engineer to their constraints. This leads teams to assume that their own computing situation (fast devices/networks/etc.) are a fine substitute for the business' users.

     This has been growing ever-more-wrong as mobile devices proliferate, but PMs have not gotten wise to it yet. Some new metrics like INP are shining a light, and may cause a shift, but at this point we've grown a whole generation of "I've got mine, Jack"-ists

   • Embed this notice
     Gödel Escher Spock🦿 (adamhill@hachyderm.io)'s status on Sunday, 24-Dec-2023 15:09:58 JST Gödel Escher Spock🦿

     in reply to

     @slightlyoff Genuinely curious - What's the primary failure mode of React projects?

     Institutional or software architectural?

     Matthew Lyon repeated this.