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.""
____
~ |rip/\/\aster /\/\onkey
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.
Abe: I used to be with it, but then they changed what "it" was. Now, what I'm with isn't it, and what's "it" seems weird and scary to me. (Episode: 3F21 Homerpalooza)
It's only going to get worse as the pace of change continues to accelerate. In ten years a few engineers will be designing new classes of electronics based on quantum principles. Or totally new types of devices based on photons or magnetic spin vs. electron charge. Ten years later, that will be passé and maybe we'll be doing something with neutrinos. Who knows how things will work 30 years from now. It will all be magic by then.
The NSA: The only part of the US government that actually listens.
"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
I feel kind of odd watching flamewars about who is tougher and more hardcore, C++ or some other language group, and I think to myself, "maybe they should have to actually deal with assembly, logic, and bits for real before they start talking hardcore. I remember when we were putting together kits out of catalogs with hex pads and light up bulbs and calling it computing.
Oh well. I think all this excitement has gotten to me. I'm going to go take a nap now. Where's my cane?
If my grammar and spelling are off, I am [distracted/tired/careless] (take your pick)
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.
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.
"I'm oooooold! And I'm not happy! And I don't like things now compared to the way they used to be. All this progress -- phooey!"
:(
Dana Carvey, Grumpy Old Man
Sounds more like my wife...and you have no idea how much trouble I'm in for saying that (not to mention how depressing it is to discover that your wife is a grumpy old man)
A goal is a dream with a deadline
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)
Indeed, I'm nearing 70, and have worked in the computer industry for a very long time. There have been a number of times that I have envied the young.
One such time was at work, probably around 1995 or 1996. In order to increase the productivity at our firm we installed several Internet-enabled workstations for various managers, secretaries and workers.
After a while we noticed some rather work-unrelated web sites showing up as being accessed from a particular workstation, which happened to be in the office of one of the young guys in finance. They were rather peculiar fetish sites. In any case, some of us in IT thought that we should alert this worker's higher-up to what was happening.
It was decided that several of us would discuss the matter with him. So we headed up to his office, and knocked on his door, and opened it. Much to our surprise, he was there with a massive boner, ejaculate all over. He must have been in the middle of it when we knocked, because he was quickly trying to clean the mess off of the keyboard and his pants.
It didn't bother me that he was whacking his cock in the office, or that he got his semen on the computer's keyboard. What bothered me was that he was able to get an erection, and I wasn't. So even though I knew far more about technology than he did, he was able to get a boner and I couldn't. I was trumped.
Cyric Zndovzny at your service.
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.
Cotton Gin -- basically, pulls the cotton from the unwanted plant parts by pulling it through a filter with, and I haven't seen one since I was a kid, a brush of needles.
Steam Locomotion -- easy: burn something to heat water resultant expansion pushes piston/turbine to make motion
Similar to above except uses small amount of gas which is ingited with a spark, or diesel fuel which is ignited through pressure and the resultant locomotion is powered through the driveshaft to turn the wheels. All the accessories are run off of a belt system from the driveshaft: water pump to keep the motor cool, alternator to keep the battery charged and the sparkplugs popping...
Electricity -- similar to above except instead of turning a wheel or drive shaft a magnet is spun inside a coil of wires and the electricity is produced and transmitted across a grid of wires and transformers to your home. Alternately, running water, nuclear fusion and wind can do this too.
Telephone: it's basically like pulling the tail of a cat and at the other end the cat screams.
over the air broadcast system -- same as above, but without the cat.
Wheel of Fortune -- Vanna White is the oracle of the goddess Fortuna and the wheel intereprets your fate.
any other smart questions whippersnapper?
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
I am often put into the role of teaching others how things work. I am 29 years old and have no CS background (I am entirely self-taught). I talk to most techies and they have no idea how things work behind the scenes. I am not talking "this IM client sends the message to the server which sends it to the other IM client." I am talking an in-depth understanding of how things like TCP, IP, and UDP work. They generally have no clue. I actually had one student who had several years of IT experience tell me that he thought UDP and ICMP were the same thing...
;-)
How did I understand how these things worked? I started by reading the oldest documentation I could find. Part of the problem is that computer professionals have become very good at confusing eachother (using the OSI model to discuss TCP/IP for example) and the other part is that the document writers in general don't understand what they are writing about. Then I could go and read newer documentation and have some sense of what it is worth. Good documentation in this industry is a rare thing.
Maybe it helped that both of my grandparents on my mom's side were writing programs before I was even in diapers
LedgerSMB: Open source Accounting/ERP
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
Would that be the same OSI that is the 7 layer model of which TCP/UDP/ICMP is the fourth layer and IP is the third?
In order to appreciate why this model deserves to die, you have to look into its history. OSI was a large ISO attempt at creating a standard networking system which would have been a direct competitor to TCP/IP. They spent a lot of time writing specifications and engineering things, and not time actually building anything. So while TCP/IP was evolving, OSI was being overengineered.
OSI was intended to be the perfect networking system. With it you could transport Voice via virtual circuits (similar to the cell allocation in ATM), data (via packetswitching), etc. with QOS enforced end-to-end. OSI, had it been implimented would have meant the complete convergence of the PSTN and Internet backbones. Consequently they spent far too much time hashing and rehashing problems and not nearly enough time actually prototyping anything. Eventually everyone walked away from the endevour and conceded that TCP/IP had in fact become the standards through altenate standards bodies and that nobody was going to move from TCP/IP to OSI. OSI therefore serves as a serious history lesson on what *not* to do in both standards and software design and development.
However, someone came up with the not-so-great idea that the basic 7-layer model if stripped down made a good way to teach TCP/IP. Good instructors teach it as "well, a bunch of telecom companies thought that networks were supposed to work this way" but far too many try to teach that TCP/IP follow that model which they don't. A few differences:
1) TCP/IP is entirely packet-switched. OSI was designed to allow packet-switched and circuit-suitched connections travel over the same system (an idea that survives in ATM today, however).
2) TCP/IP is designed around a set of very conceptually simple issues that need to be solved, with network tasks being implimented flexibly in different layers. OSI tries to break down network tasks hierarchically and assign every task to a single layer.
3) OSI was designed to be all things to all systems, while TCP/IP was designed to provide "simple" packet-switching services to get information from one system to another.
Hope this helps.
LedgerSMB: Open source Accounting/ERP