The need to code

<i>And then, one day it clicked. I don't know what exactly caused it but it was as if the light had been turned on, I suddenly understood the program that I'd just typed in </i>and* all the ones that I'd been typing in before it. And the next program I typed in was one that I came up with, not one from the exercises*<p>That's <i>exactly</i> what happened to me, and you're the first person I've ever seen express it.<p>I was about 10/11 at the time with a Vic20. I spent quite some time with nothing really making sense. No specific memories, just that I didn't really get it and was close to getting bored with the whole thing. My next memory is that suddenly, I <i>got</i> it. One minute I understood nothing, then it all made sense. Some window opened in my mind and understanding flooded through, an experience I can't explain and have never had since.<p>Here's how my story differs though - Once I was midway through high school I became embarrassed by my affinity with computers. Bit of a social stigma I spent the next 15 years trying to avoid, working all sorts of different jobs trying to fit in somewhere. It wasn't until I ticked over 30 that I was able to admit it (writing code) was the one thing I kept coming back to; the drug I'd been addicted to for the last almost 20 years, but tried to hide from.<p>And now here I am, almost 40 and I've just got myself a cofounder, we've registered a company and I've spent what's been (so my wife says) a lovely Sunday sweating in the hottest room of the house (the study) working on the beginnings of a new life. And I can't think of anything I'd rather be doing. Sad, isn't it :)

A lovely article. I did not start programming with intensity until I was 30, almost two years ago. Now I look back to my youth, when I was poking around in Basic, trying to figure out how to write a login system for my computer (running DOS 5 or something similar), and I wonder, what happened? Why did I ever stop? Why didn't I carry it through? I spent my teenage years and my 20s doing work I wasn't passionate about simply because it was easy.<p>Now programming has changed the way my brain works. I'm a much more critical thinker. I wake up in the morning and the first thing I do is crack open Emacs (yep.) and start hacking. I <i>need</i> to program. Creating software is the first thing I've ever been truly passionate about in my entire life. My entire wasted life. At least I found it. Better late than never.

A great story.<p><i>That process, the act of programming is something that I need to do.</i><p>My feelings exactly. I can't not program. If I'm burned out with some complex work-related problem during the day, I can still catch myself fiddling around some random unrelated little code that does something "cool" (whatever might be cool for me at that moment) in the evening.<p>I started programming in elementary school (10yo), when I got a C64 computer, which was very popular at the time. BUT, I got it with a disk drive (1541-II drive, which cost more, and had more CPU power than the actual computer), and all my friends had tape drives, so I couldn't exchange games with them..<p>So I read and re-read the owner's manual, which was in German, and I didn't really know German .. so I would type these BASIC examples and try to figure out what happens. I think one of the first programs I wrote and understood was a variation of "guess the number" game.

Wow. I can almost picture that kid!<p>I've only done limited amounts of programming, but I can certainly see how it could be addictive as you get better. A lot of the time I've spent has been utterly wasted, e.g. fighting for a week to get a rails install configured 2 years ago and then mostly giving up as various tutorials I was following were all out of date. But when I've gotten something working such as the kongregate shootorial, it's been easy to spend all my free time for a week tweaking it and improving it.<p>I also have to say that the entry point for programming (aside from setting up the environment) has been a lot less frustrating than for some of my other pursuits such as language learning. I must have learned a good 200 words of Swedish before my pronunciation was good enough that natives could even guess at what I was saying. Obviously at a higher level, language learning is more about memory than intense thought like programming is, but a lot of people get frustrated long before reaching that point. Programming is also a hobby that won't lead to being a perpetually broke translator.

&#62;&#62; Programming has an addictive component that is very strong. As you get better you gain more expressive power, you can do more complicated things than you could do before, solve more complex problems.<p>and<p>&#62; &#62; It's like a drug. I'm still fascinated by it, even almost 30 years to the day later I still read about languages, new ways to solve old problems, all kinds of developments in software and hardware as though it is the first time that I hear about these things.<p>It is like a drug. I think our brains fire off the same pleasure inducing endorphins when we figure something out or learn something new. And it happens so much in programming: you implement something old in a new way and you get a little buzz, you squash a bug that's been getting to you for a period of time and you get a bigger buzz. I think curiosity when we were little got us interested, but ever since we, or at least I, have been a junky. I sometimes wonder how my life would be different if, by chance, I would have gotten addicted to something else. There's so many things to get addicted to these days.<p>my other drug of choice is mathematics. the highs are higher, but they take a lot longer to reach. programming gives you rewards almost instantly.

I've never understood why Byte magazine was shut down. There's been nothing like it. I can't imagine it not being popular in today's tech culture. I'd pay $100 or more for a year's subscription to it right now.

When I was first programming I didn't have a computer and so I'd write programs in little notebooks. When I finally did get a computer it had a very slow tape recorder for saving programs. I would frequently write programs and simply switch the computer off without saving. Saving was a hassle and I knew that the programs worked once I'd executed them.

This captures more of the story of my life than I'd care to admit. I'm lucky to earn good money doing something that I can't stop doing.<p>Once, I was deeply burnt out. I took up knitting in an effort to get away from programming for a while. And just like Feynman in yesterday's front-page story, I was once again writing toy programs within a month.<p>Sometimes I wonder what I would have done if I was born 20 years earlier.

&#62; Programming is not like playing a musical instrument, it is not something that you have to have a genetic disposition for.<p>As someone who is stumbling through the basics of programming and learning guitar, I can tell you that the secret to success in both is practice and putting in the time. There are very few activities that you cannot become good at with sufficient time and resources.

<i>...if you add up the number of hours that I've spent in conversation with editors, compilers and debuggers over the years...</i><p>I'm afraid to do that. I would probably be shocked by the number, and then would quickly calculate my lifetime rate, which would probably be about 28 cents per hour. This is the thing non-programmers never understand; programming takes <i>a lot of time</i>.<p><i>It's like a drug.</i><p>Great analogy! For me, there's no bigger high than the exact moment of the conclusion of this process:<p>NothingThere + IDidSomething = SomethingThereForTheFirstTimeEver!<p><i>That process, the act of programming is something that I need to do.</i><p>Sometimes I think this is the difficult-to-define missing requirement for software success. Some call it "passion". Some call it "determination". I call it "I can't imagine doing anything else".<p><i>but it has all the components of a 'real' program, input, computation, output.</i><p>Don't forget storage. That was the killer feature that got me hooked. You could write a simple program, store the result (on a disk!), come back later and build upon that result. Before disk storage, computers were toys. After disk storage, they changed the world.<p><i>there is nothing that can't be learned.</i><p>I've never had a tatoo, but if I did, this probably would be it (backward, on my forehead).<p><i>...all you need to be is a little bit better than you were yesterday and to keep doing that for a long time.</i><p>This advice:<p>1. is excellent. Maybe the best you'll ever read here.<p>2. is <i>not</i> intuitive. Most people don't get it. Like compound interest, it's hard to wrap a human brain around it.<p>3. is universal. It applies to almost anything you can do.<p>4. is very difficult to teach. As soon as you think people get it, they don't. They stop measuring their own deltas and resume comparing to perfection. Grrrrr.<p>5. the single most important thing I've ever programmed in business turn-arounds. The best dashboards and report writers I've ever written are time-phased; they clearly show improvement <i>over time</i>, which is almost always more important than any snapshot:<p>Losing + Improvement + Time = Winning<p><i>Beware of that bug though, once it bites you, you'll be hooked for life.</i><p>To this day, whenever I need something for myself and can't find it in 5 minutes, I build it. It may not be the most effective way, but I just can't help myself. There must be a (3)(2)(2) program for people like me.

&#62; And so I did. That first copy of byte magazine got read to pieces, I even knew the words of the ads by heart.<p>:-3<p>I grew up in a later era and one time in the late 80's my mom brought a portable computer home. When you turned it on the screen would shimmer and my mom let me type in the word processor. It was disappointing, since I expected computers to be so much more Amazing than a word processor. Then, later, we got a home computer, and we had it for seven years, and internet access for two, without the idea clicking that yes, I could probably write programs on it somehow. (I couldn't, actually, because QBASIC was not installed.) Finally I got my start writing "programs" when in eighth grade they taught us how to do word processing and make spreadsheets, and using MS Works Spreadsheet '99 (on a new PC) I made a spreadsheet for managing a basketball pool. I was still unaware of the idea of having a programming environment on a computer. A year later, though, we had to get TI-83 calculators for math class, and that's how the hobby of programming kicked in for a lot of people of my generation. Programming on calculators sure as hell beat devising ways to sort a deck of cards.

This is so similar to what I've done .... My first computer was a Casio PB100, with the 1548 bytes memory extension :) I still have the programs I've done on small cardboard sheets.<p>Then I had an MSX in 1986. I made dungeons games, drawing programs... all in BASIC of course. When I got bored with BASIC I plunged into Rodney Zack's "programming Z80" and wrote a crude assembler in BASIC.<p>From there I had a grandiose plan of a 3D 3rd person adventure game in an open world... I began some work on it and realised I'd need about 10000 times the 64KB RAM to get anything done, and a CPU 100 times as fast, and countless other stuff :) Happy days, everything was possible back then.

Drug Wars on the TI-83 is largely responsible for my interest in computers.

What is probably most significant point of this article is that he has enjoyed programming for that long and still enjoys it, and gets to do it. It is refreshing to read that, amongst all the craze for startups, somewhere folks are interested in programming as a hobby, as an art. And not just high school or college but life-long. I certainly think that just like music, art, sports there is an aspect to programming which is as fulfilling as these art form. And more than the end goal, the act itself is also filled with purpose and fun.

The end really hit me deep...very assuring " It may take a while (it took me more than a year to learn 'BASIC', which is a very simple language) and I gave up several times only to go back to it once more." I don't know how many times I've tried learning python only to fail..but I'm going to keep trying until I can stick with it and get better...bit by bit.

I had one of those sharp pocket computers - though I was a but younger at the time. It was 4 bit!

My need to code comes almost exclusively fromy my need to understand. If I can understand a problem space well enough to explain it to a computer, I probably understand it.

I actually once asked the StackOverflow community where the software we make isn't so dear to us as "one's own child" - at least I feel that way so often.<p>I(){ _just_love_code;} I();