It’s hard to write articles and posts about “actually it’s fine how you develop software, you probably don’t need to change anything” when you compete with the hundredth post about some shiny new library or some new made-up best practice
Conversation
Notices
-
Embed this notice
Thomas 🔭🕹️ (thomasfuchs@hachyderm.io)'s status on Wednesday, 10-Apr-2024 23:29:09 JST Thomas 🔭🕹️ - pettter repeated this.
-
Embed this notice
Joe Cooper 💾 (swelljoe@mas.to)'s status on Wednesday, 10-Apr-2024 23:49:55 JST Joe Cooper 💾 @thomasfuchs A few years back, I sort of imposed a new rule: I won't start using anything that's not directly in my area of expertise until it's survived ~five years. I figure the shine will have worn off by then, and I'll be able to make an assessment of its worth based on sentiment among its users. If I know enough to judge it myself, I may use something new and shiny, but only if I can pick it apart and understand all the pieces. This rule protected me from React (and a lot of other JS hell).
-
Embed this notice
Thomas 🔭🕹️ (thomasfuchs@hachyderm.io)'s status on Wednesday, 10-Apr-2024 23:50:07 JST Thomas 🔭🕹️ @swelljoe very good rule