rockerest’s avatarrockerest’s Twitter Archive—№ 19,253

    1. Use components as late as possible. Use as few of them as possible. Almost everything else is a more important concern than componentization. Setting a component library as the first principle will destroy your software. Data design and architecture first!
      Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 5 Favorites 2022 Mar 22 Mood -1 🙁
  1. …in reply to @rockerest
    More and more, I'm starting to believe that major UI component frameworks took a package of individually catastrophe-level mistakes of software design, packages them all up in one think piece and got everybody to buy in. Any one idea destroys good software, but all together? OOF.
    On twitter.com Twitter logo rockerest’s avatar ❤️ 2 Favorites 2022 Mar 22 Mood -2 🙁
    1. …in reply to @rockerest
      I'm _also_ mulling the idea that even repeated identical (or near identical) UI should not be componentized unless it's used for the exact same purpose. E.g. use-case trumps de-duplication. Is your navbar profile avatar the same as your comment author header avatar? I'm not sure.
      Permalink On twitter.com Twitter logo rockerest’s avatar ❤️ 1 Favorite 2022 Mar 22 Mood 0