3 ms·
I've been coding since I was six years old. (I'm in my forties). For the first bit of that it was BASIC on a TRS-80 Model 100 laptop, with 16k and a tape drive.
by noduerme 5y ago
I've been coding since I was six years old. (I'm in my forties). For the first bit of that it was BASIC on a TRS-80 Model 100 laptop, with 16k and a tape drive. Then, really, Perl and Hypercard. Answering the question of but what for??? was a huge part of my friends' and my dilemma in building simple games and projects. In my experience, there is a chasm between getting good at doing something technically and knowing what the hell you're supposed to do with that knowledge. Screensavers; that was the best idea we had and that's what we competed against each other on. We'd sit around and talk about how we could make something like SimCity plus SimEarth plus realistic physics and make a universe simulator. Or a driving game that could generate cities to drive through. But I had the same experience with 3D modeling! I could spend a hundred hours to make a dinosaur in a pirated copy of Infini-D. Okay, now what?
Perhaps this is off track, but I guess to us at the time the joy was in discovering the technical aspects, and tinkering and learning how to use them. I read the BASIC manual that came with the TRS, and I remember being 7 years old and skipping the part about "Arrays" repeatedly because it seemed too complicated to light up dots on the screen. Until one day I just was like, okay, what's this "array" thing, I feel like I'm missing something. And suddenly that chapter blew my mind. Likewise, I was deep into my third or fourth PHP online store / shopping cart in the late 90s, when a kid I hung out with was like, what? You're not using a database? And I was like no, I just have text files for each product. There's a whole back end for the business to edit the text files and images. Then, because I couldn't not look at it, I had to look at mysql. Holy shit, you mean I don't have to create text files for every product? Or block one person from editing them when someone else is? The rest being history.
Okay, broader scope: You can't generate use cases until you need them, and also, you can't learn tools until you have the use case for them, or else you're going to forget what they were for. Tools and the experience of working with the tools go together. You might be able to simulate that experience by building a card game, but like all skills, they will be lost quickly unless they're exercised regularly.