Slashdot Mirror
Tech Geezers vs. Young Bloods
Lam1969 writes "Robert Mitchell talks about how technology is dividing him from younger generations: "The technologies I've watched grow have shaped an entire culture of which I am not a part." Adds Dinosaur: "Ask them [members of the younger generation] HOW the things work, and they have no idea. They are really riding on the backs of the 'old folks' like us that built the goodies they enjoy.""
Aside from that, anyone who is actually surprised that people who grew up using a given piece of tech will have different attitudes towards it than the people who've had to adapt to it needs to be locked up someplace where they won't pose a threat to their own well-being. It should be obvious to anyone who hasn't spent their entire life in a coma that this is just how it works.
I'm not trying to post flamebait here, but honestly I can't even concieve of another reaction to this...
Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
Eventually the knowledge will be passed along to the younger generations. They'll pick up where us oldies have left off. Indeed, it is often said that it is more difficult for them. We have left them with systems that are far more complex than were left to us when we all started. I trust in our younger generations. They'll be able to advance our technological knowledge. And the best thing is that we're now drawing from the most creative and brilliant minds of India, China, Korea and many other nations. We're bound to make tremendous discoveries just because we now have so many talented people working in the technology field.
Cyric Zndovzny at your service.
"Ask them [members of the younger generation] HOW the things work, and they have no idea. They are really riding on the backs of the 'old folks' like us that built the goodies they enjoy.""
Do the same thing to the old folks. They dont know either. Of course some punk ass kid on a skateboard doesnt know how stuff works, hes retarded. A generation does not invent, select individuals do. Remember, people are stupid.
-Bill
How many people can produce a fire out of just sticks?
Fact is, our society is becoming increasingly specialized, and it's no surprise that some people won't understand the technology behind it even though they use it frequently. They're just specialized in other things, that's all.
As long as *somebody* knows how the technology works (engineers and scientists), there isn't a need to worry.
You always get this kind of attitude when a technology reaches a divergent point. I would hazard that many people know how to build CPUs and how the internal workings of a system function as ever, it's just that the hardware and the software have slowly diverged over the past twenty years. No longer do you need to know the particulars of a video card to communicate with it, etc. It isn't necessary for software people to know hardware, and visa versa. Both fields have become complex enough to function independently.
Thanks to standardization of system design and function, this isn't really a problem. And I'm certain that AMD and Intel take very careful consideration of the software demands their hardware will face (as do Crucial, ASUS, et al).
There may be a few remaining niches where the software and the hardware remain inextricably intertwined, such as small consumer devices, (iPod Nano, palmtop computers, etc).
It's the modern dilemma: there is too much to know. Two or three hundred years ago, you could read every book ever written. Now you can't even read every book ever written about computing.
It's the old joke: How many software engineers does it take to change a light bulb?
That's a hardware problem.
When you're afraid to download music illegally in your own home, then the terrorists have won!
Let's take your example of assembly versus C++ versus some other language. Consider the software that was written in assembly back in the 1950s and 1960s. Sure, there were some pretty impressive pieces of work. Various compilers, OS/360, and whatnot. But compared to software today, such items are of a level of complexity often expected from first or second year undergraduate Comp. Sci. students.
.NET runtime. Those are fairly complex motherfuckers. Far more complex than anything that was even conceived a few decades back.
Sure, we're not using assembly today, but even some of the more minor systems implemented in C++ are far more complex than anything that was written in pure assembly several decade ago. I mean, look at something like an optimizing JIT Java virtual machine or a
Cyric Zndovzny at your service.
After all, SciFi writers have been predicting this for many years, haven't they?
I have read many stories where there are generations of knowledge passed down to an elite class of society that are revered by the rest as demigods for their knowledge of how to keep machines running that provide the world with food, air, heating and all the comforts of life.
Do not meddle in the affairs of geeks for they are subtle and quick to anger
Seriously, how is it stupidity to simply be ignorant of things that you don't need to know? I don't know how my digital camera works beyond a few of the basics (light shines on CCD, then... er... picture ends up on my flash card), that doesn't stop me from being a reasonably good photographer. I know how to use my camera, how to manipulate the aperture and the shutter time and the ISO to get the picture that I want. Isn't that what counts?
No person can be an expert on everything, and in my experience the people who try tend to be the real useless ones...
Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
And this older generation, they did everything themselves, from scratch! They started out by learning how to mine and refine metals, to create copper wire. Then they discovered electricity. They invented the resistor and the capacitor. They learned how to machine parts....
Standing on the shoulders of those who came before is the definition of progress. So, please, unless you make your own wiring and screws and capacitors and what have you, shut up and stop whining.
.. most people still don't know how a flushing toilet works. It's something most everyone uses every single day. It's a very simple machine. But apparently I was some sort of female plumber superhero in college because I knew how to fix it.
Some people will just never become curious about the things they use from day to day. Others will. That's the difference.
You say you got a real solution
Well, you know
We'd all love to see the plan
(The Beatles)
More then that, it is now impossible to completely understand a computer. I used to program in assembly, and I understood how every chip on the motherboard worked, and all of their little quirks. That is now impossible, and programms must rely on the makers of the chips to make them accessable through drivers.
Religion is a gateway psychosis. -- Dave Foley
GOOD!
I'm a smart, technically savvy individual, who generally knows how ALL of his technology works. In fact, I make it a point to do so most of the time.
And as long as that's the case, that means that I WANT the younger generation to be ignorant, so I can reap the rewards of their ignorance.
As long as they're still ignorant, I'm still getting paid.
Ah, the joys of an object oriented universe. Nah, you don't need to understand the internals of *how* it works, you just need the API docs.
Do programming courses in college still teach actual algorithms (prime number sieve, sorting, searching, etc.) or just how to program to APIs? I know OOP makes development easier precisely because you don't have to understand the object internals, but it's like a pocket calculator -- there are real lessons to be learned from putting it away and doing the work manually.
Also, I realize that I'm picking on programmers here, but the truth is that IT mindshare eventually follows them, so the disinterested attitude that found its way into the ranks of the developers eventually got around to everyone else.
I am also somewhat alarmed at how many IT people I have met who do not program, never have programmed and never plan to program.
BTW, present company (probably) excepted, of course.
"Lawyers are for sucks."
- Doug McKenzie
This isn't anything new. 20 years ago teenage girls would spend all night on their families landline. They would also make radio mix tapes. The only difference is they can now take all of this stuff out where you can see them doing it. How many minutes you spend on your cell phone doesn't equate to tech culture. I don't use many minutes on my cell phone either, but it isn't because I am old school. It is because it is a tool for me, not a social outlet.
One thing I have noticed over time, is that fewer people (I'll leave age out of the equation) seem to understand how to tune a system or how to identify where the bottlenecks are. More frequently, I see sysadmin-types say that we need a new computer computer when what we need is more memory or faster I/O.
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
After racism and sexism die out, maybe we can go after ageism. Making arbitrary distinctions based on age is just as bad as doing so based on race or sex.
It's the modern dilemma: there is too much to know. Two or three hundred years ago, you could read every book ever written.
But committing to memory all of the oral tradition even in one culture would have a similar education to what we have today. I think it was Pliny who said that the Druids had something like 20 years of training. And it doesn't take a professional Linguist to read something like "How to Kill a Dragon" and realize the depth of these traditions. Or how easily can one commit the entire Rig Veda to memory (it was originally memorized, you know).
In other words, the required knowledge in specialized fields really isn't a new phenominon.
The second issue is that most of this stuff isn't really that conceptually complex. It can easily be explained in Contemporary Standard American English without using jargon. The problem is that people have so much ego invested in broken analogies (OSI model used to "explain" how TCP works, for example, with few people even remembering that OSI was supposed to be a competitor to TCP and built along fundamentally different assumptions).
In short it is not that there is too much to know, but that it is hard to winnow it down so that you know what information to consume. The problem is compounded by broken requirements like knowing the OSI model which is not only dead but broken.
(I always tell people to memorize the OSI model for exams and then don't ever worry about using it after.)
LedgerSMB: Open source Accounting/ERP
It's simply not necessary for people to know how everything they use works. I know how to series-wind an AC motor, but there's no reason why everyone who wants to vacuum their floor should have to. It's called the social division of labor. I don't really know how to make clothes, operate a bottling plant, or weave a carpet, but there are people who do.
Back in the days when most people lived on farms and made most of the things they used by themselves, we all lived in rather squalid conditions. Let's hear it for specialization!
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
... of some of the fantastic conversations I've had with my stepson. At first I was a little put off. But now I'm kinda fascinated by his generations' point of view.
... uh you can make one of those with a linux box, it's a computer that saves video data to a hard disk, and that disk only has so much capacity. When the Nintendo DS came out, he was thrilled about this new "802.11 technology from Broadcom" ... I said ... like the Linux based Linksys router we have, the one I've customized firmware for? At that point we've had the router for a few years.
... or who knows what and who knows "HOW" things work. But we can learn from each other.
... look, you can compile this on linux by changing one line!
He grew up on nintendo. I grew up on Commodore 64. He thinks AIM is a killer communication app, for me it's IRC (for customers where I work it's email). We had interesting conversations about several things... we had a disagreement on how a Tivo works. I basically said
The point shouldn't be who's right and who's wrong
At some point, I had to stop and realize... wait, he's just growing up in a different world than I did. So now, it's really cool. Our individual experiences compliment each other. He brought home some C++ homework, and I said
I'm an admin for a local internet provider and we do some connections for local colleges. I don't talk to the students there all that often, but when I do, I find it easier now.
You're not better than a younger generation because you understand different things than they do. When you start to understand them, you're better than you were.
FLR
Also, in the Corporate IT field at least, there is strong selection for specialization. Most of our network guys are clueless about operating systems, and most of our O/S people are clueless about low level networking. Hell, most of them wouldn't even know how to do subnet math.
And the corporate environment encourages that. Naturally, nobody not in the network group is allowed to touch the networking equipment, so they'll likely never learn much beyond what they need to know for O/S support, etc etc. This silo-ing extends throughout much of Corporate IT in my experience. It discourages cross-training and encourages specialization to what imo is an excessive degree.
I sort of miss the old days sometimes. As a kid doing assembly (and machine!) code on my C64 I felt like I knew almost every little detail of how it worked. I felt like a god in total control of my little universe.
With modern programming its more like being a CEO barking out orders to my minions (makers, compilers, assemblers, linkers and such). I haven't really a f*ing clue what is really going on anymore. I suspect they do a lot of slacking off but I can't see it from my office.
It reminds me of what Richard Feynman said about the advantages of growing up with vacuum tube based radios, how you could much more easily see how they worked. Now it's just a few black boxes connected by hard to see wires, and there as so many bells and whistles, it is harder to get a feel for what is going on.
Perhaps it isn't essential to know all the details, but it is fun to learn anyway. If I had a geeky kid, I'd encourage him to play with my Atmel microcontrollers and developer board. Its good clean fun and maybe it would come in handy some day.
In emergency situations is interesting what dumb mistakes people make because they are so used to being far removed from the details of how things work. After a hurricane several people will always bring their generator indoors and die of carbon monoxide poisoning. Several will make obvious errors cutting up fallen trees and end up crushed. Many don't even seem to know how to cook without electricity or start a fire without matches or a lighter. I know of one person who couldn't even figure out how to eat from plants full of string beans, only knew how to warm them from a can. This is mostly stuff our ancestors dealt with daily.
http://www.marxist.com/