Ask HN: How to never reinvent the wheel in software ever again?
I keep reading (and feeling it myself) that in software always reinventing the wheel when it comes to software.
Of course, a lot of it is due to opinionated (design) decisions. Or profit. But if we all had to agree on things that are solved & done and not to be touched again and would at most create a few small personal frictions (as there are either way), but which we can live with so that we really only build new software, Frameworks etc. for new things.
Let's imagine the existence of our planet depended on it.
What would the stack be? What composition of languages, processes & tools that would work "for everyone"?
Or if there was a set of rules that everyone had to adhere to, in which it says what is not to be reinvented, what do you think would be included?
It's only theoretical, of course, but I'm interested to see if there are even a few common denominators to identify on HN and what these are to people here.
Of course, a lot of it is due to opinionated (design) decisions. Or profit. But if we all had to agree on things that are solved & done and not to be touched again and would at most create a few small personal frictions (as there are either way), but which we can live with so that we really only build new software, Frameworks etc. for new things. Let's imagine the existence of our planet depended on it.
What would the stack be? What composition of languages, processes & tools that would work "for everyone"? Or if there was a set of rules that everyone had to adhere to, in which it says what is not to be reinvented, what do you think would be included?
It's only theoretical, of course, but I'm interested to see if there are even a few common denominators to identify on HN and what these are to people here.