3 ms·

Funnily I find that the new and the shiny is a rebranding of the old and the stable. The difference is a new language + name + platform. I think this is an endl

Funnily I find that the new and the shiny is a rebranding of the old and the stable. The difference is a new language + name + platform. I think this is an endless cycle as we see new developers come in and discover old concepts in new frameworks. Once you've been through a few of these cycles it's easy to get jaded and burnt out, which is when older Devs may push back on the new. I don't think it's because they're changed adverse, just that they doubt the benefit of doing something they already know in the flavour of the month framework/language. I'm guilty of all of this and have been through several burn outs. Nowadays I accept that everything will always be changing, and to keep an open mind to avoid dismissing things that are truly revolutionary.

mrweasel 6y ago
One of the realizations I think comes with age, or experience, is that what most of us do isn't that special. When you're young, or new to the world of IT, it's easy to look to Google, Netflix, Twitter and other tech giants and be fascinated by the challenges they face and the tools they develop of cope with those challenges. While I continued to be fascinated by new solution, new frameworks and whatnot, I also try to set it into the context for which is was developed. For instance, I had a customer who had chosen Cassandra as their database, but the total size of the dataset was never going to be more than a few hundred MB. It's not that Cassandra is bad or even wrong, it was just developed for something different and was only picked because it was new and exciting. Ops team are in my experience better at rejecting the new shiny, because it's often not really ready to be properly managed. The operations side of are often takes years to mature and no one wants to get up a 3AM to debug some bonkers system that was picked only because some developer thought it would be interesting.

mrweasel 6y ago

One of the realizations I think comes with age, or experience, is that what most of us do isn't that special. When you're young, or new to the world of IT, it's easy to look to Google, Netflix, Twitter and other tech giants and be fascinated by the challenges they face and the tools they develop of cope with those challenges. While I continued to be fascinated by new solution, new frameworks and whatnot, I also try to set it into the context for which is was developed. For instance, I had a customer who had chosen Cassandra as their database, but the total size of the dataset was never going to be more than a few hundred MB. It's not that Cassandra is bad or even wrong, it was just developed for something different and was only picked because it was new and exciting. Ops team are in my experience better at rejecting the new shiny, because it's often not really ready to be properly managed. The operations side of are often takes years to mature and no one wants to get up a 3AM to debug some bonkers system that was picked only because some developer thought it would be interesting.