5 ms·
The older I get the more I realize how these old curmudgeons were often right. They've been there to witness the cycles of technology and aren't impressed with
by flukus 10y ago
The older I get the more I realize how these old curmudgeons were often right. They've been there to witness the cycles of technology and aren't impressed with the shiny new ones that are often worse than the old ones. They aren't interested in the cloud because it's modern day mainframes for instance.
Lately I've been taking a look at a lot of older tools and being pleasantly surprised by how capable they are compared to modern ones. I started coding professionally in a world of virtual machines and xml files, now where moving back to native compilations and json. Eventually we'll rediscover ini files and how there even simpler than json and we can avoid the curly bracket tax. I've used every build tool under the sun but recently discovered that make was simpler and better than anything else I've used. We've gone full circle on ORM's and now writing sql is in vogue again.
I wish I'd learned more from those guys much earlier.
- PhasmaFelis 10y agoWe're so eager to justify arbitrary technical fads. Use something until you have enough experience to start seeing its flaws, move on to something shiny and new and perfect until you've used it long enough to see its flaws, repeat.
- flukus 10y ago> Use something until you have enough experience to start seeing its flaws I think we've been completely skipping this step for the last few years.
- gaius 10y agoYou can very easily find yourself in a situation where every project is either your first in technology X, or trying to maintain something that was someone else's first attempt at using it. "Legacy" means "proven in production and making the company money" but too often these days it is seen as a dirty word.
- lsc 10y ago> The older I get the more I realize how these old curmudgeons were often right. They've been there to witness the cycles of technology and aren't impressed with the shiny new ones that are often worse than the old ones. They aren't interested in the cloud because it's modern day mainframes for instance. This is actually one of my biggest career problems. I mean, it's an advantage, too... I can pretty quickly understand new things, because they are similar to old things, but... on an emotional level part of me rebels from the new cool thing simply because the old thing worked, often more reliably, and this new thing? this new thing has a bunch of little subtle differences and bugs that I have to learn and deal with and fix, just like the old thing had a decade ago, so my natural reaction to the latest fad is usually a negative emotional response, and pointing out that it's essentially the same thing as the old thing. This causes obvious problems, of course, with the people who got promoted for "demonstrating complexity" when they wrote or implemented the new system. I need to learn to point out the similarities to the thing I know, but to do so without the negativity, because, uh, cultural fit. (so bitter!) >They aren't interested in the cloud because it's modern day mainframes for instance. This is the opposite of true. Mainframes were all about complete reliability; you can always rely on the hardware, or at least that's what you are paying for. "The cloud" is all about the chaos monkey, about writing your application to deal with any server failing (or returning nonsense) at any time. The disillusionment with "the cloud" comes from having to deal with managers who think that "the cloud" means reliability, when it really means "write your applications so they can deal with hardware that is significantly less reliable than hardware managed by in-house sysadmins"
- marcus_holmes 10y agore: Chaos Monkey. I love this, and I'm 48. 99.999% uptime meant that once a year your program did something completely disastrous because the server flunked. Assuming our hardware was reliable was a mistake. Writing code so that it's chaos-monkey-proof is a great step forward. As for the generational thing... meh, we're ugly. People like hiring the beautiful folks. Startup folks think they're immortal, having some greying old fart in the corner wheezing away reminds them that they're not.
- 10y ago
- redditmigrant 10y agoIts likely that someone who says "NO" all the time is right some of the time and its fair that they get credit for being right. At the same time, they need to be held accountable when something they said "NO" to turns out to be a really big deal. Im sure someone said Java is a fad when it was launched or that python was useless and so on.
- flukus 10y agoA lot of people were saying no to java, at least on the consumer desktop which was one of it's first big aims. That's one of the thing's that young, naïve me put down to old farts being out of touch. Two decades on their C/C++ win32/x apps are running and no one has java installed in their desktop to run mine. They have every reason to be smug.
- Asooka 10y agoExcept everyone has .Net installed, or at worst you have to install the runtime once yourself, which you still need to do with C++ anyway. Java's failure wasn't technological, but marketing.
- guelo 10y ago.Net is pretty much Java. So after all the legal and marketing turmoil young you was basically right.
- flukus 10y agoThey hype around java was being cross platform and making the OS choice irrelevant, .net had the opposite effect. When I look at all the apps installed in my computer, very few are .net apps.
- redditmigrant 10y agoObviously Java didn't succeed as a desktop application development language, but the JVM and the java eco system has succeeded by any objective measure. I see your point that what matters is what does a person say "NO" to.
- pmiller2 10y ago>Eventually we'll rediscover ini files We kind of have. They're called YAML files now.