5 ms·

So how old does the tech need to be?

grugagag 3y ago
It doesn’t matter as long as it is consistent and maintained.
falcolas 3y ago
I’d say at least 5 years since it’s debut. Long enough for the rough edges to be softened, to show that people are willing to maintain it, for detractors to have pointed out legitimate issues, for the tech to become stable. I’d prefer 10 years personally, but I value stability more than most. I dislike revisiting problems I’ve already solved.
6510 3y ago
The hype train never stops! The golden ticket is for the front cabin but ideally you are driving it.
dusted 3y ago
The older the better. The better understood, both in capability and limitation. The better chance no new updates will break it. The better chance no new updates. The better you get to know it. The better you get to integrate it. The better the chance it will be there tomorrow too. The better the investment learning it becomes.
- mablopoule 3y ago
  On the opposite end of the spectrum, if your stack is too old (and niche enough) then you won't get to know it very well once every bit of documentation was hosted on expired domain name, and you can only find bits of online discussion about it are Internet Archives snapshots of a forum long since dead. And also you don't get to integrate it very well if everything around it isn't maintained, and compatible on old version of a library (with said documentation not existing anymore). Also, while resume-driven development is not a good thing either, it's certainly not a good investment to pigeonhole your career into working with something you hate working with.
- noisy_boy 3y ago
  > The older the better. But remember to use the right tool for the right job - older isn't always better. E.g. there is a set of people who use stored procedures for everything and it does make sense when you are doing data-heavy processing on database-side. But using that for everything, even when the volume is absurdly low, is a bad idea - using a language like Java would be a million time more flexible, composable, testable (unit tests, anyone?) and allow making changes with greater confidence.
datavirtue 3y ago
PHP old

It doesn’t matter as long as it is consistent and maintained.

I’d say at least 5 years since it’s debut. Long enough for the rough edges to be softened, to show that people are willing to maintain it, for detractors to have pointed out legitimate issues, for the tech to become stable. I’d prefer 10 years personally, but I value stability more than most. I dislike revisiting problems I’ve already solved.

6510 3y ago

The hype train never stops! The golden ticket is for the front cabin but ideally you are driving it.

dusted 3y ago

The older the better. The better understood, both in capability and limitation. The better chance no new updates will break it. The better chance no new updates. The better you get to know it. The better you get to integrate it. The better the chance it will be there tomorrow too. The better the investment learning it becomes.

mablopoule 3y ago
On the opposite end of the spectrum, if your stack is too old (and niche enough) then you won't get to know it very well once every bit of documentation was hosted on expired domain name, and you can only find bits of online discussion about it are Internet Archives snapshots of a forum long since dead. And also you don't get to integrate it very well if everything around it isn't maintained, and compatible on old version of a library (with said documentation not existing anymore). Also, while resume-driven development is not a good thing either, it's certainly not a good investment to pigeonhole your career into working with something you hate working with.
noisy_boy 3y ago
> The older the better. But remember to use the right tool for the right job - older isn't always better. E.g. there is a set of people who use stored procedures for everything and it does make sense when you are doing data-heavy processing on database-side. But using that for everything, even when the volume is absurdly low, is a bad idea - using a language like Java would be a million time more flexible, composable, testable (unit tests, anyone?) and allow making changes with greater confidence.

datavirtue 3y ago

PHP old