I became interested in computers around age 9 (I'm old -- this was before microcomputers) when I was first introduced to a computer. I can still clearly remember the awe and wonder that I experienced when I first laid my hands on the terminal, as if it were yesterday. At that time, all I was doing was making little banners punched out onto paper tape.
I wrote my first lines of code about 3 years after that, in Pascal on a PDP/11. It was through a school program meant to help smart kids who didn't do well in school.
Interestingly, my interest was in electronics, not programming. However, I was from a very poor family and couldn't afford to buy parts -- but I could use a computer for free -- all I had to do was be willing to take a 90 minute round-trip bus ride -- so I shifted to programming.
I guess you could say I'm a dev because of economics, just not in the way that implies.
I was interning at a small startup and made some financial models in Excel (using functions like index and match together).
At the time, I told a programmer at the company that I wanted to learn programming. He looked at my work and told me that I was already doing it. I didn't believe him because I didn't think it was "real coding". I thought he was just being nice.
Yes - This book alongside one on AJAX (oh the days of ready state). I still had databases named mismatch_<x> up until about 2014 IIRC!
The book was a perfect example of frictionless starting to code, jumping over hurdles, skipping wholistic education (e.g. all column types/more than select, update, insert in MySQL) for getting something that worked simply and linearly.
And funny examples that stuck in memory (decades later as it turns out..)... like a dating app that matches by opposites between "opposites attract".
10, got my first computer (in '98) and instantly was interested in the prospects of making websites and having people visting them.
From then I made many websites, made money with adsense when it was initially available, paid my college and made a career that moved me to Germany.
Can't complain about this, it made me stay easily at 99.99% or 100% in the bell curve of income from people where I was born/lived. It has changed my life completely, it bumped me up in high-middle class in the first world. I'm endlessly grateful on the future that it brought me and I still enjoy it a lot!
I've never been outstanding, just "great". Some people had much better backgrounds than me and this helps loads, only on my mid 30s (now) I felt like I catched up on other aspects in life.
I was 12. I had access to an Apple 2 at home, and it came with a booklet on Apple Basic.
But let me say this as well - you'll get a lot of people here quoting young ages. That doesn't mean you -have- to start young.
I often hear the same question with music. Lots of people started young. But equally lots of people start old, it's just not a story. I started playing drums at 20. People I went to college either had never seen a computer before 20.
Age is just a number. There's no virtue in starting young. Ultimately it doesn't really impact every you can end up. It's just a signal that you have an interest, and got an opportunity to indulge that interest young.
Side annecdote - I remember one moment really well. I'd read a bit of the Basic manual and then had to go off to school. On the way home I deduced that the language must have an IF statement. In hindsight it's obvious, but what I remember most was the deduction itself. Being correct (which I verified a few minutes later) seemed like a very powerful thing. I feel like maybe it was the first thing I consciously figured out that wasnt taught to me by an adult or book.
Interestingly, I was a computer nerd since age 7. I found it fascinating to explore every possible setting in windows 95, and I got involved in hosting my own servers for gaming.
So I dove deep into configuration, but whenever I saw any code, I would immediately close the window.
It wasn't until my freshman year in college (age 18), when I took my first CS course and pierced the veil underneath. Wish I had done so earlier.
Actively programming? At age 12. We didn't have a computer at home so I had to use the one at school and wrote my programs on paper by hand them typed them into the computer at lunch time as fast as I could to see if it would work! I was so happy to finally get a computer but it was kind of fun to look forward to lunch time.
About five-six - I got into my mother's old Pascal books, messed around with TurboPascal on her old DOS machine, and then found and installed DevPascal on the family computer.
She was an IT teacher, so she kept on getting new textbooks for her classes, and I kept on reading through them - I learned and forgot batch programming, poked instructions in debug.com without really understanding them, thumbed my nose at Java, painstakingly wrote out PHP code on paper, and kept on playing with Pascal until I found Python, maybe by twelve-thirteen?
I wasn't a great coder: I was completely self-taught, in a really haphazard way, but it gave me some decent foundations - I probably butted heads with every possible error, which can come in handy surprisingly often.
Readit News
I wrote my first lines of code about 3 years after that, in Pascal on a PDP/11. It was through a school program meant to help smart kids who didn't do well in school.
Interestingly, my interest was in electronics, not programming. However, I was from a very poor family and couldn't afford to buy parts -- but I could use a computer for free -- all I had to do was be willing to take a 90 minute round-trip bus ride -- so I shifted to programming.
I guess you could say I'm a dev because of economics, just not in the way that implies.
I was interning at a small startup and made some financial models in Excel (using functions like index and match together).
At the time, I told a programmer at the company that I wanted to learn programming. He looked at my work and told me that I was already doing it. I didn't believe him because I didn't think it was "real coding". I thought he was just being nice.
My first "real coding" was a year later. I modified a few of the example apps from "Head First PHP & MySQL" (https://www.oreilly.com/library/view/head-first-php/97805961...).
The book was a perfect example of frictionless starting to code, jumping over hurdles, skipping wholistic education (e.g. all column types/more than select, update, insert in MySQL) for getting something that worked simply and linearly.
And funny examples that stuck in memory (decades later as it turns out..)... like a dating app that matches by opposites between "opposites attract".
Still got anything running based on it?
From then I made many websites, made money with adsense when it was initially available, paid my college and made a career that moved me to Germany.
Can't complain about this, it made me stay easily at 99.99% or 100% in the bell curve of income from people where I was born/lived. It has changed my life completely, it bumped me up in high-middle class in the first world. I'm endlessly grateful on the future that it brought me and I still enjoy it a lot!
I've never been outstanding, just "great". Some people had much better backgrounds than me and this helps loads, only on my mid 30s (now) I felt like I catched up on other aspects in life.
But let me say this as well - you'll get a lot of people here quoting young ages. That doesn't mean you -have- to start young.
I often hear the same question with music. Lots of people started young. But equally lots of people start old, it's just not a story. I started playing drums at 20. People I went to college either had never seen a computer before 20.
Age is just a number. There's no virtue in starting young. Ultimately it doesn't really impact every you can end up. It's just a signal that you have an interest, and got an opportunity to indulge that interest young.
Side annecdote - I remember one moment really well. I'd read a bit of the Basic manual and then had to go off to school. On the way home I deduced that the language must have an IF statement. In hindsight it's obvious, but what I remember most was the deduction itself. Being correct (which I verified a few minutes later) seemed like a very powerful thing. I feel like maybe it was the first thing I consciously figured out that wasnt taught to me by an adult or book.
So I dove deep into configuration, but whenever I saw any code, I would immediately close the window.
It wasn't until my freshman year in college (age 18), when I took my first CS course and pierced the veil underneath. Wish I had done so earlier.
She was an IT teacher, so she kept on getting new textbooks for her classes, and I kept on reading through them - I learned and forgot batch programming, poked instructions in debug.com without really understanding them, thumbed my nose at Java, painstakingly wrote out PHP code on paper, and kept on playing with Pascal until I found Python, maybe by twelve-thirteen?
I wasn't a great coder: I was completely self-taught, in a really haphazard way, but it gave me some decent foundations - I probably butted heads with every possible error, which can come in handy surprisingly often.