If anything, back in the 90s having to learn to create web pages was a barrier to creation. Video? Forget about it. Digital cameras were just coming around, but were still super expensive. I have some old pics taken on my flip phone from the early 2000s and they are...really bad. Instead I had to spend hundreds of dollars are completely separate device to be creative. And that device still didn't do video.
The problem is that outside of certain subjects, video is a time-inefficient and low-information-density medium. So many things could be conveyed in fuller form, and in a way more respectful of people’s time, by using text. Unfortunately, the use of phones as default devices by many people today young and old discourages longform text, due to the limitations of tiny touch keyboards and screens. That is my own feeling of unease with the way tech is today.
In some niche travel scenes, I have seen a big decline in meaty, useful information since the early millennium, when a blogger generally had a laptop to type on. Sure, now we get glamorous video content, but that can’t be all there is.
I’m not sure why I prefer video content. I find my attention relaxes more when watching a talk than it does while reading. Like, I find it more effortful to concentrate on a long article in comparison to watching a talk. (Though usually 1.5x+ speed is a necessity). Also, good talks are generally better written than the average article, and good talks are easier to find than good articles are. Project readmes and webpages will say useless things like “This is our database in Go, here’s how you install it. It’s fast and reliable!”. But a good talk by the author will give me the background and the story. “So, here’s why Postgres wasn’t working for us for this problem we have at Netflix. We really wanted to solve our problem this way. So then we built this new thing to do that and it’s working great! Let me show you the weird parts we’re really proud of…”.
Text is great for reference. But I could listen to technology stories like that - telling the “why” of what people have made all day long.
I just get annoyed when people call these devices consumption only. I could say the same thing about computers when many people only play games on them. These devices are what the person makes of them.
But that isn't some kind of law of nature - it isn't true for everybody. There's a significant group of people who find it much easier to use video or voice and powerful tools have arisen to help them.
For example, the TikTok video editor gets people started quickly and lets them learn as they go. I'd really encourage you to watch a tutorial to see how easy and surprisingly powerful it is.
There is no doubt that modern technology has enabled people to realise a lot of things they woul dneve rhave been able to, such as creating a movie using tools available in your pocket.
However, the original post was about learning technology. I.e. understanding computers. The difference between being a mechanic and someone using a car to drive to the grocery store.
The problem is that that the term "digital native" implies that the person understands how computers work. One might argue that the term actually should mean something else, but I argue that would make it an even less useful term. Do we call people who has drivers licenses "motorised vehicle natives"?
And no, I'm not blaming the kids who grew up with this and can't know any better (yet). It's the adults who are wrong. They're old enough to know better, but they're content with their positions, they're lazy and they're scared of taking risks by speaking up.
I sympathize with what's been lost, but what happened was people realized they didn't actually want to build a web page, they wanted to converse on a forum and share pics, and be entertained. Sure, you could publish anything you can imagine that's less than 4 MB on Geocities, but I'd rather have Wikipedia.
I find it pretty inspiring that we live in a time where someone who really loves doing, like, aerial yoga can reasonably make doing aerial yoga their job just by learning how to edit videos and engaging with other people who are also into that thing.
Though there doesn't seem to be a huge difference in practice between "youtuber" and "television presenter" other than the broadcast medium. One thing that youtube adds to television is an easy way to interact directly with viewers.
The modern "digital native" that I categorize is the legions of young people getting started in programming the vast number of rich environments that exist today.
Yes I remember the times upgrading my 486DX-33 to 8Mb of RAM, installing slackware from floppies, figuring out whatever dark magic was needed to run Duke Nukem 3D over IPX networks simulated over dialup, and heady and critically important discussions about the role of Amigas, coveting the barmaid in LoRD on the high school BBS, running unauthorized star wars MUDs on the high school computer network and getting dragged in front of school boards because you ran "nethack" once (in fairness it was likely also the pornography being accessed and distributed leveraging the school T1 lines as well but in my defence I was 14).
It was a time and a place, and there's certainly value in reminiscing. But these new kids will create their own time and place, and demanding that they somehow pay homage to my experience as being "more authentic" seems a bit pleading.
And to be honest we downplay the limitations of our times. Free and accessible development environments? Not on the standard desktop PC operating system (until DJGPP came along anyway, and even that had severe limitations for a while for building native windows apps). If you were a super nerd who went out of your way and downloaded an obscure little free unix system developed by some finnish guy named after a peanuts character, you got a compiler. And then if you scrounged around random docfiles spread out across dozens and dozens of random howtos, you could sort of learn how to program C, or python or perl.
I look at today's technical environment, available to the entry level student in some technical field, and the available breadth and depth of tooling, the amount of documentation and tutorials, all available for free, and it's amazing. If you're someone looking to build something interesting, there are a 100 different more opportunities to do that today using accessible tooling than there ever was when I was a kid.
And I admit having a sense that I am not as knowledgeable as I could be about using these insanely powerful devices to their fullest potential. The demoscene can make amazing things happen with teensy amounts of code. Amazing!
So I started watching the Ben Eater making your own breadboard computer series, and am now following hia 6502 series so I can eventually convert my model M to a self-container battery powered DIY Alphasmart word-processor-to-SD-card contraption, because why not?
So I too agree that the tiktokers are the kids these days for now, but I more heartily agree that some of them will discover something new and amazing on that there YouTube. Maybe they'll learn something we've forgotten and leave all of us in their dust with what they do with it!
Then again, bit earlier you had included BASIC on every microcomputer, and hardware documented way better than random PCs glued together with duck tape.
First; I must say I was surprised that my little rant made it to HN, but obviously some found it interesting, and it did spark a discussion.
Secondly: Yes, I do come of as a jerk. English is not my native language, and my Norwegian dry humour may not have translated as well as I had hoped (which is not an excuse). Also, at an age of 38, I do not really have that much experience with what todays youth does, with exception of kids between 5 to 10. And that is not a fair comparison anyways.
I have not yet read all the comments here, because I fear some of them might be a bit personal, while my "attack" was mostly a generational one. As I said earlier, this is the first time I gotten a real audience on my blog, and I was not prepared at all for this kind of reaction.
But I value your feedback, and I see your point. Next time I will try to look a bit past the "rough" language and see topics from different angles. Because the world I grew up in is gone, and we are still making progress, so obviously things are going the right way.
its the kids who grew up in digital land that we should consider the digital natives.
2 cents from the peanut gallery!
You are right. My intention was not to come of as a jerk, nor did I expect anyone to read my blog post, to be honest.
My point, which kind of got lost in the end, was to show of the big difference between my generation and the next.
I have heard so many people praising today's kids as technical wizards because they master the gesture/finger based interface so much better then the generation before me. The term "digital natives" I got wrong, big time.
In hindsight I could have spent some more time polishing my idea before publishing.
Folks now have web page editors in their phones/tablets. Drawing apps, etc.
When I was 16, yeah, I want to make a webpage about WWE/F, so I had to spend days learning table based layouts and how to ftp files to a server (and find one).
Now I (my son) can open his phone and he has various tools to do so. He can share/post pictures of someone doing a full nelson and write about it, and get it up on the web in minutes vs days.
Just because he didn't have to learn 45 different incantations at the command line, doesn't mean he isn't creative, he just doesn't need to slog through programming to do it. (He is learning python though)
Think about it as frameworks, when we started, we needed to learn it all to make any kind of decent page, now most folks here would use bootstrap/material ui/whatever, or react/rails vs writing all the css by hand, fighting with all the problems it brings, configure perl scripts to be able to send an email from it, etc etc.
The comments here have been a helpful reminder that creativity is very much alive and well! I do worry about how many people would think "This app is cool! I want to learn how to make them" but stop because the device for consumption is different from the device for creation.
Really dating myself here but the very first programs I used were ones from a magazine I typed in to a little TRS-80 pocket computer from Radio Shack myself (I'm not 100, really, I just started young and had an encouraging grandpa), and in the process realized "hmmm I could change this line and get a different output, cool!". I think that's about the lowest possible barrier between consumption and creation.
On the other hand, I learned very, very slowly compared to now, in large part because it meant getting a magazine or reading a book, and having nobody to ask when things weren't clear. On the whole it probably is easier, now that I think about it, but only if you're motivated. Maybe that's OK - people who want to can still learn to rebuild a transmission, even if most drivers don't.
But there are tools on mobile/web to create those things also. I've been researching and trying to get something that is intuitive to work on tables to program web apps (it started web based, but now moving it to mobile as I think it matches the visual paradigm better).
There are various tools for kids to learn to program creating games (Scratch is probably the most well known) but other visual programming apps also.
I don't think you need to go back to early car enthusiasts. A lot of people would argue that at least being able to do basic car maintenance is a life skill everyone should have. I don't necessarily agree but I do think it's useful to understand at least the basics of how a car operates.
You might argue I'm not car literate, but I'm not sure that is particularly insightful, as the type of specialized knowledge is not actually relevant to doing almost anything with a car that people want to do.
Similarly, while coding is great and all, I'm not sure that not being able to code is the same thing as not knowing how to use a computer effectively.
It would be a huge problem if you're an aspiring mechanic or anything related, but that's an increasingly niche role so we aren't worried about kids not having mechanical literacy. Many kids are aspiring to work in roles where computer literacy is vital and becoming more so every day. The one's that lack the fluency to do things like automate the repetitive parts of their jobs will gradually not be adding enough value to be gainfully employed.
Not being computer literate will have a huge impact on their careers, not being car literate won't (for most).
Most people want a car to go from A to B, many times, if every few years (I only had a blown tire in 20 years driving) they have to call someone to help them, it makes much more sense than spend the time to learn how to do it themselves. Same with computers, they don't want to know how the bytes get into ram, they want to play Doom or write a school paper. There is no need for them to learn all that.
So, I always feel better with a small amount of understanding to arm the BS detector.
This attitude was around for a while when Linux started getting easier to use (I feel like it's gotten a bit better, but maybe I'm just a part of better communities now). It's the same attitude that came up occasionally in game dev around Unity. It's pretty predictable and pretty tiresome. I don't think the author is a bad person or that they hate kids, but I think this kind of attitude is something that shows up regularly in technical communities and it's worth forcefully stamping out.
This article as it's written isn't interested in education, it's purely inwardly focused on describing how hard the author had it growing up, and how rewarding it was, and how great they turned out, and how everyone else who didn't have that same experience is a poser. It's purely designed to put younger generations down and denigrate them rather than reach out to them in any kind of thoughtful or meaningful way.
The author isn't proposing any solutions. Forget solutions, they're not even identifying problems. There's nothing of substance in this post other than bragging. No mention of how proprietary hardware incentivizes lock-in. No mention of how laws have changed. No mention of how software gets written today and how our toolkits affect accessibiliity. No mention of the rise of SAAS and how that affects people's ability to modify the programs they run. No mention of education challenges. Just nothing at all.
The only reason this blog post exists is because the author is mad that some kids are getting more attention than they did. And while it's worth talking about increasing barriers to creation, the author doesn't seem to be equipped to do so, and their targets of ire (streamers and content producers, arguably some of the more technically involved youth communities out there today) are poorly chosen.
> "If anybody is a digital native, it is me. I did not just grow up with computers, I grew up alongside them."
We get it, you're very smart. I'm super proud of you for installing Windows from a floppy disk. Do you want a medal? Should we all clap for you? Round up and scoff at the people who didn't appreciate your generation enough?
Notice what this article never says. It never says that a reduced hacker ethos in younger generations is a problem. Its primary concern is not that younger kids aren't engaged enough with technology, or that they're not hacking their devices. The primary complaint this article raises is that younger kids are called digital natives, a title that the article is concerned they don't deserve.
But that's not tech literacy.
Maybe my definition of programming is quite narrow, but I wouldn't consider using CAD software, spreadsheets, or (physics, space, etc) simulation software as programming, yet I would consider the ability to use them a degree of computing or tech literacy. I would certainly consider them very far from only being a consumption device.
It's like you would like to claim "desktop literacy" for the noble tasks that can be performed on a (e.g. wooden) desktop, traditionally it being let's say copying evangelical scriptures, and are angry against those ignorant young folks that don't give a fuck about the bible but find writing novels cool, and let's not even talk about the peasants that merely use their "desktops" to cook and eat (and in the background you have a pen maker who listens to the copyist rant, with a small smirk)
At this point the vague "tech literacy" term is not useful anymore, and the problem is just that more precise terminology is needed to communicate efficiently.
For example, joining together many separate 3D objects is extremely slow if one just selects all and does an union, since the algorithm needs to check all pairs of objects for overlaps in 3D space.
That may not be immediately apparent to non-programmers, but to programmers, it will feel like an intuitive consequence of the problem and the inevitabilities of its solution.
Literacy isn't about reading all the time, it's about being able to read if you want/need to. Same with computer literacy.
Looks at all the creation-related tools on his iPad and iPhone, none of which involve programming
You sure about that?
Does this mean that my laptop undergoes some sort of miraculous transformation when I type :wq and open my browser?
What if I'm watching video in the background while coding - does my laptop then enter some superposition-state?
The defining feature of books is that you can read them, and books are useful because they have that property. You are literate if and only if you can read a book, regardless of whether you are reading a book at the moment.
The defining feature of computers is that they are arbitrarily programmable machines, and computers are useful because they have that property. You are computer-literate if and only if you can program a computer, regardless of whether you are programming a computer at the moment.
You are literate if you can read an arbitrarily chosen book. You are an author if you can write a book. Similarly, you are computer-literate if you can accomplish tasks in an arbitrarily chosen program and maintain a system. You are a computer-author if you can write a program.
We use literacy to describe understanding, not creation. What you're claiming is the equivalent of saying that modern generations can't be book-literate unless they're writing fan-fiction.
I would argue tech-literacy means understanding the common language of tech/UX today and being able to use common technology. Someone is tech-literate if they can "read" technology and are comfortable with common interface conventions, terminology, system maintenance, etc... Anyone who sets up a streaming platform using OBS, who manages a community using admin tools on tech platforms, who figures out how to tune games that they're playing to accommodate recording without dropping frames or de-syncing audio, who sets up microphones and figures out how to balance audio using mixers, who edits the result and uploads it to Youtube -- they would fall very squarely into that category of literacy. They clearly know how to "read" software, even complicated programs like video editing tools.
Whereas a computer can do many different things. Yes, it's because it's an arbitrarily programmable machine but if I choose to use software written by others rather than programming it myself I'm not sure why that's a lower use.
In fact, I can program but rarely do so. Usually I'm using a computer to do tasks like writing, working on photos, etc. My day to day use is sort of irrelevant to the fact that I can do some programming. So I guess I'm not computer-literate.
Just like an Office 365 subscription is a simulacrum of a horde of calculators (people) with mass-produced calculators and typists on mass-produced typewriters, which were simulacra of noblemen scholars, pens (mass-produced simulacra of quills) and papers (mass-produced simulacra of expensive parchment)… which themselves were simulacra of prehistoric humans making cave paintings.
So do you really feel the need to tabulate, calculate and write today?
Now, the rest of your point is, who cares? Do with that thing whatever floats your boat, it's fine if you don't program. That point is valid. But when "that thing" is a computer, and they're "doing" something with it, that qualifies as "using a computer". At least by the definitions the rest of us are using.
The point I'm trying to make is that I percieve a very clear conceptual difference between "using a computer to program" and "using a computer to do other things", and I would tend to believe an effort to improve computer literacy should attempt to point people to the former rather than the latter.
Do you believe those things to be the same? I have a strong intuition that they aren't, but I'm very willing to hear a counterpoint.
Once again, I'm specifically trying to avoid any kind of value judgment.
>I would tend to believe an effort to improve computer literacy should attempt to point people to the former rather than the latter.
is why? I mean sure. If they want to become programmers, then they need to learn how to use a computer to program but I'm not sure why that's any more about "computer literacy" than lots of other tasks.
I use computers for lots of things on a day to day basis, including many "creative" tasks, and almost none of those involve programming. Programming is a specific way that you can use a computer and it may imply deeper knowledge of the underlying system than making a video, but so what?
For that matter I could equally argue that a pure front-end developer isn't really computer literate because they maybe don't understand kernel schedulers, security model, processes, interrupts, etc. work. Oh, and how about TLBs, cache eviction policies, dynamic resource allocation, etc. at the CPU level?
There's certainly nothing wrong with using a computer for other stuff, also. Or even exclusively, not everyone needs to be a programmer, that's for sure. I would argue, however, that algorithmic thinking/basic scripting is a very important piece of human knowledge, is it really more esoteric than Latin or Greek, which are routinely taught to high-school students?
> For that matter I could equally argue that a pure front-end developer isn't really computer literate...
There are different levels of literacy. A 7-year old and a PhD in English literature are both literate, but not at the same level. Same goes for computer-related knowledge, it's a bottomless pit, like any other interesting field.
But this guy is just being a jerk: "Digital natives my ass, all they do is stream videos on YouTube and Twitch."
Which is a shame, because it crowds out what I was hoping would be a more thoughtful discussion about devices created purely for consumption, or perhaps walled gardens, and how they don't afford people the same opportunity to learn as general purpose computers.
I wonder if early car enthusiasts felt the same about people who learned to drive when you no longer needed to know how to fix your car all the time.