4 ms·

> Its sad but its true and I wish I knew what to do about it. For us that have already been spoiled by modern computing, we need to be shown what useful stuff

by Dewie 12y ago

> Its sad but its true and I wish I knew what to do about it. For us that have already been spoiled by modern computing, we need to be shown what useful stuff that we can do by learning about computers (obviously we would need to be on a relatively open modern computer). If most people are satisfied with whatever gets them through the more-or-less intuitive GUIs that lets them watch some videos, do they really need to know more? Well yes, when their computer eventually starts behaving strangely and simply restarting it doesn't help... but that kind of frustrating troubleshooting doesn't leave a good taste in many people's mouth when it comes to having to deal with computers. If they are already used to modern, powerful computing, chances are that they won't be impressed by the usual computer wizardry that programmers are impressed by. Simply because they don't need, or don't see the utility in, shuffling a bunch of text around efficiently. Instead of becoming a wiz at retro computing - which might be in part because you need to be a wiz, simply because it is more primitive - what can we impress people with on modern computers that they can't do themselves easily (and would like to do)? They've already been spoiled by modern computing - for many, there is no turning back. If the only real allure of being a computer whiz - to most people, anyway - is to be able to operate arcane technology, then the value proposition simply isn't there for people that do not appreciate computing in itself (and even that might be an acquired taste, so sort of a catch 22). It's like a classical guitar virtuoso who can be motivated to learn songs and pieces solely for the technical challenge they pose, while his students just want to gain the skills necessary to learn their favourite band's songs, or the songs that they've written themselves.

solistice 12y ago
Personally, I think if you want to kindle interest in people that aren't traditionally considered tech people, the usual course of action goes from user to power user to novice programmer. It goes from using the most appearent options to using less appearent options that do it better to creating your own options and tools. Say someone watched a lot of different streams. Show them how they can do it in VLC from one place. Show them enough that the utility of using VLC outweights using whatever method they used previously. Then, give them some time till usage of that tool becomes a habit. Then show them how to use the VLC command line options to record and convert streams so they can download them onto say their phone. Gently suggest "There's a rabit hole here, and it's filled with fun". Then give them some time to tinker around, see what they can do. Once they outgrow these shoes, when they're running out of cool addons they can install or when there's something that's just not in there yet, you can start to teach them how to write their own additions. Now this is just a single example, but i think it illustrates the point. You want to help them slowly build momentum and a need for better tools. Most people are cocconed in a comfortable level of software usage, and they belive that their tools are sufficient, and learning more isn't going to be worth the returns in regards to effort. If you manage to sucessfully change those beliefs, their entire modus operandi regarding computers will change. Now what tool and which lesson will get that started differs from person to person. For some it's learning VBA scripting for work, for other people it might be using Autohotkey to create macros or even learning some keyboard shortcuts ("Wait, alt-tab switches windows? That is so neat!"). Luckily, about everything that is commonly used has some kind of handy add on that extends functionality, say Reddit and RES, or getting that Junior Junior Dev to move from notepad to notepad++ and then after a good while to vim or emacs.

by Dewie 12y ago

solistice 12y ago

Personally, I think if you want to kindle interest in people that aren't traditionally considered tech people, the usual course of action goes from user to power user to novice programmer. It goes from using the most appearent options to using less appearent options that do it better to creating your own options and tools. Say someone watched a lot of different streams. Show them how they can do it in VLC from one place. Show them enough that the utility of using VLC outweights using whatever method they used previously. Then, give them some time till usage of that tool becomes a habit. Then show them how to use the VLC command line options to record and convert streams so they can download them onto say their phone. Gently suggest "There's a rabit hole here, and it's filled with fun". Then give them some time to tinker around, see what they can do. Once they outgrow these shoes, when they're running out of cool addons they can install or when there's something that's just not in there yet, you can start to teach them how to write their own additions. Now this is just a single example, but i think it illustrates the point. You want to help them slowly build momentum and a need for better tools. Most people are cocconed in a comfortable level of software usage, and they belive that their tools are sufficient, and learning more isn't going to be worth the returns in regards to effort. If you manage to sucessfully change those beliefs, their entire modus operandi regarding computers will change. Now what tool and which lesson will get that started differs from person to person. For some it's learning VBA scripting for work, for other people it might be using Autohotkey to create macros or even learning some keyboard shortcuts ("Wait, alt-tab switches windows? That is so neat!"). Luckily, about everything that is commonly used has some kind of handy add on that extends functionality, say Reddit and RES, or getting that Junior Junior Dev to move from notepad to notepad++ and then after a good while to vim or emacs.