There are a million ways to make a website or app, but ultimately, what matters is how well the needs of clients and users are met.
If you're making a personal project, or want to focus on learning or experimenting, it makes sense to choose your technology stack based on personal preference or current interests. But when there's stakeholders other than yourself, their needs are paramount.
There's no shame in using well-established technologies that get the job done. And there should be no inherent pride in using something exciting or new.
For example, WordPress remains a great option for many websites, particularly customer-facing ones focused on marketing and conveying information. Its ease of use for non-coders is still a hugely valuable asset. Developers can set up the site with any custom code needed for design and functionality, and the site's owners can then update the content very easily. It's a winning combo.
Every technology has trade-offs. But just remember, "hipness" has nothing to do with how well the needs of clients and users are met. Do what's best for them, not what's fun for you - unless, of course, the two overlap, which certainly happens sometimes.
Top comments (1)
This is such a refreshing take! 🙌 So many developers get caught up in the 'newest is best' mentality and forget that clients just want something that works. I've seen teams over-engineer simple brochure sites with Next.js + GraphQL + Tailwind when WordPress would've been perfect. The point about 'no shame in established tech' needs to be heard by more devs. Great insights, Talia! 👏