4 ms·
I believe you have agreed with me in your points especially regarding talent and turnover. The shiny tech today will be a legacy 6 months later or a year if you
by Oras 6y ago
I believe you have agreed with me in your points especially regarding talent and turnover. The shiny tech today will be a legacy 6 months later or a year if you’re lucky. Then the talent pool will change and you can’t attract the devs who religiously follow new trends. You’ll end up hiring people to deal with your {legacy} system or as you pointed out .. substantial changing it.
- bstar77 6y agoReact/Redux/Angular all have staying power so I don't understand your point. I don't know what you mean by "shiny" tech. Other than specific libs that go unmaintained, most popular tech has some staying power.
- rapind 6y agoThat’s not a universal truth. Java was shiny once upon a time. Rails was shiny once, even C was shiny once. This stuff is still being used (not legacy). I’m sure when rails first showed up, people were calling it a fad. In JS land there’s a ton of churn though for sure if that’s what you were thinking about. Not all of it though.
- Oras 6y agoBeing used does not mean it is not legacy. Do you consider a system running in Java 6 up to date? But if it is stable, serving customers requirements then there is no need to replace it. The point I am making is, using the current {shiny} tools might not be the correct answer (it could be though depending on the use case). Just use whatever gets the job done faster and then iterate. Some developers will start solutionising based on technology instead of focusing what is the purpose of the system and how it will help users. AKA: CV driven development :)