Hype vs. build – as a developer do you focus on the stack or on the user?

Question

I wrote something recently about how, as developers, it is easy to get caught up in the latest hyped up language, framework or design system that's touted to be the next best thing.

Given the hype, do you work with what you know and know well to build something quickly or learn the new thing to build something with?

Post here: https://morningfinds.substack.com/p/how-to-resist-the-hype-and-focus

Kenny Hawkins · Accepted Answer

If it's scalable, efficient, reliable, and secure, by all means, have the hype!

If an 'older' framework accomplishes this and allows for faster build, go that route.

Udipta Basumatari · Answer

Well written, at the end of the day, the average user doesn't really care what tools were used as long as the solution gets the job done well.

James Tedy · Answer

it depends on the goal, if the goal is to create something out of those hyped stack then I'll do that,

but if the goal is to create a good product or to solve problem then I'll work with the stack I'm most familiar with.

Answer

If the goal is to make a good product or solve a problem, I will use the stack I know best.

Uma Venugopal · Answer

User. If you're a developer, building features isn't exactly a hard task. So I focus more on the pain points of users. For me its about the quality of 2 great features over 100 useless ones that helps users engagement.

Hype vs. build – as a developer do you focus on the stack or on the user?

Replies