Conversation

Notices

1. Embed this notice
   Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 19-Jun-2024 19:36:58 JST Marco Rogers

   in reply to

   Product teams that are smart are getting off the treadmill. Whatever framework you currently have, start investing in getting to know it deeply. Learn the tools until they are not an impediment to your progress. That's the only option. Replacing it with a shiny new tool is a trap.

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 19-Jun-2024 19:36:59 JST Marco Rogers

     in reply to

     If your product is still around in 5 years, you're doing great and you should feel successful. But guess what? Whatever framework you choose will be obsolete in 5 years. That's just how the frontend community has been operating, and I don't expect it to change soon. Even the popular frameworks that are still around are completely different. Because change is the name of the game. So they're gonna rewrite their shit too and just give it a new version number.

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 19-Jun-2024 19:37:00 JST Marco Rogers

     A lot of frontend teams are very convinced that rewriting their frontend will lead to the promised land. And I am the bearer of bad tidings.

     If you are building a product that you hope has longevity, your frontend framework is the least interesting technical decision for you to make. And all of the time you spend arguing about it is wasted energy.

     I will die on this hill.