3 because creating things is more interesting than consuming them. 3 because, through all my interests, computers are the only thing that have always interested me. 6 So I didn't have to fill out truth tables by hand. 7 at age 8 on two TRS-80s, some of the first classroom computers in Oklahoma. 9 when I realized it would allow me to do much more deep complex work than I could do alone with pen and paper. 10 investigating how to create a website the way I wanted. 11 after I saw a computer and fell in love with it. 11 by typing in the BASIC games from the back of 3-2-1 Contact Magazine with my nerdy friends. 12 because I wanted to be a producer, not just a consumer. 14 by building games in visual basic by moving windows forms elements. 14 nominally in Basic, but actually for my Tamagotchi website '97-'98. 14 when I was 7 years old, from BASIC books my father gave me which had entire games printed out line by line. 14 with TI programmable calculators in the late 70's. 15 because I wanted to know what this QBASIC thing was that came bundled with Windows 3.11. 15 when I was 14 (1993) using MS Visual Basic 3.0 and MS Access. 16 by making math apps and games on a TI-83 calculator during study hall way back in the day. 16 in 6th grade, when I coded up an ugly animated fish in BASIC; it was awesome. 16 on an Apple II Plus and experimented with graphing all kinds of things. 17 because I thought the Demoscene was awesome and wanted to write my own demos. 17 by reading books on writing games in BASIC at the library. 17 in high school by writing a chess game that I never finished. 17 when I was 32 years old, on a Vax VMS, so I could support my children. 18 by playing with the "Big Trak" toy tank when I was 10 years old. 18 by recording, then tweaking, Excel macros. 18 by turning pixels on and off using Peek and Poke on a Commodore Plus/4 when I was 12. 19 an old 8088 trying to create an animation in Turbo Pascal. 19 as a technical outlet for expressing my creative ideas. 19 because I wanted to invent. 19 because shop class was full. 19 copying pages of a BYTE magazine and then figuring out where there were typos/bugs to make it actually work. 19 drawing silly geometric patterns in LOGO in the third grade. 19 from a school class in BASIC, but didn't really learn how to write computer programs until I studied LISP almost twenty years later. 19 in 7th grade on an Apple II clone that I transformed into a playable monophonic synthesizer. 19 making a website for my band that I wanted to be more dynamic. 19 on a Commodore PET with 4K of RAM. 19 when I discovered the internet and wanted to make websites. 19 when I was 16 and discovered programming was as expressive as my pencil; I fell in love. 20 at camp, from a seven-year old camper who showed me Scratch so that I would take him to the lab whenever he wanted. 20 because I wanted to build cool things. Now that's my job. 20 because as a kid I could not sleep without thinking about my code of tomorrow. 20 because creating something useful where before there was nothing has to be the coolest thing in the world. 20 by taking apart old text-adventure games written in BASIC. 20 by writing BASIC games on my TI-73 calculator 20 entering code from Atari BASIC magazines, and making changes to see how things worked (on an Atari 400 computer). 20 to tweak the game Gorillas that came with QBasic in the x286 computer I got in middle school. 20 watching my brothers make turtle graphics on the Apple II in my crib room. 21 Lingo and Action Script in college; learning to make interactive experiences was fascinating to me. 21 as a junior in college, with FORTRAN IV using punch cards, because I thought it might be useful someday. 21 because I love creating something, releasing it, and seeing what people do with it. 21 because I wanted to make a mind. 21 because it's not an assembly line; it's creating something new every time you do it. 21 by finding artistic problems which made absorbing the knowledge easy. 21 by studying my co-workers' code and asking questions if I didn't understand something. 21 in BASIC on a TRS-80 model 1, pouring over code from TAB books on AI and articles in Byte magazine. 21 in Flash and I don't have a computer science degree. 21 in a middle school gifted math program called MEGSSS, circa 1982. 21 in college for the satisfaction of proving to myself that computer programmers could be regular folks like me. 21 in college, because Computer Science courses were not offered at my high school. 21 in pre-calculus class because I wanted to out-geek my valedictorian boyfriend. 21 so my TI-86 could do the stoichiometry for me. 21 when I was 12 and my mom made a deal with me that I could go to soccer camp if I also went to computer camp that summer. 22 accidentally, when fulfilling my "Technology or Applied Science" in college with a class I thought might come in useful as a chemist; then I switched majors. 22 and it changed my life forever. 22 because I had a TRS-80 but no storage devices so I had to type in all of my games from scratch. 22 because I wanted to be able to create things of use to others. 22 because solving puzzles was fun! 22 because the high school programming class was taught by the hotest teacher in school. 22 by hand-decoding a paper tape left behind in my high school computer room by a kid chortling over a simple game he'd written. 22 by making websites for my favorite punk rock bands in 8th grade. 22 by reading code others had written. 22 by reading programs on my TI calculator and modifying the code to solve homework problems. 22 during an internship my senior year of high school when I discovered that solving problems with code is fun. 22 first in college, but not really, and then as a teacher. 22 on my TI-86 calculator while bored in high school classes. 22 when I realized that it was more entertaining to create than it was to consume. 22 when I was an art major and a friend dared me to take "Intro to C programming". 22 writing BASIC games on the Apple IIe; you could buy games, but it was more fun entering line by line yourself. 23 because my Dad wouldn't buy me any games. 23 because my sister recommended that I try the intro Computer Science class when I started college. 23 because the ability to craft your own tools is more valuable than any of the tools you create. 23 in English class on a Commodore PET. 23 in my first year in college, in the CS department's introductory class. 23 making games on a TI-83 in middle school. 23 on an old programmable calculator using BASIC. 23 so that I could display pretty graphics on my Atari. 23 to get infinite lives in ZX81 and VIC20 games. 23 when I realized there was a huge gap between the "flow-factor" of games kids play outside school and educational applications. 23 when I was 8 years old on a Tandy TRS-80; I fell in love. 23 when I was seven, and I'm still learning. 24 after graduating with a Philosophy degree. 24 as an extra-curricular activity when I was bored at school. 24 because I believed (and still do) that it's one of the best skills to have in order to change people's lives for the better. 24 because I wanted to figure out how a computer worked. 24 because I wanted to make interactive electronic literature. 24 because I wanted to solve problems. 24 because my TI-89 came with a user manual. 24 because there were ideas I wanted to explore that I couldn't explore in any other way. 24 because the "learn basic" program was on a diskette with games and I accidentally started it, not knowing it was real stuff. 24 by not being afraid to break things; it's more important to be a good problem solver than a mathematician. 24 by taking a course in BASIC at my high school. 24 making the most basic of games on my TI-83 calculator that we used in high-school 24 on my TI-89 in order to make an RPG. 24 on the back side of punched cards on a UNIVAC 1100 as an intern at the Swedish Defence Central in the late 70s. 24 so I could become a wizard on a MUD. 24 using QBasic to make interesting visuals to show to friends. 24 using Q-basic to make a funny spinoff of tic-tac-toe, called Tic-Tac-Yo-Momma. 24 when I got a job that required me to sit for 8+ hours a day and write Java. 24 when I was bored playing the games that came with my Commodore 64. 24 when my dad told me I could make the computer play me a melody using BASIC. 25 because I was curious about what the little box could actually do. 25 because as soon as I plugged a phone line into my PC, I wanted to leave my mark on the net. 25 because of bad organization in a dot-com boom company's web team. 25 by translating code from "Writing Adventure Games on the Amstrad CPC 464 / CPC 664" (a computer we never owned) to 386 QBasic. 25 copying games onto my dad's TRS-80. 25 from some friends in high school who had been programming since they were in middle school. 25 in high school, back when we had just a dial-up connection. 25 in the second grade with the Logo turtle (I named him "Tiberius") on an Apple IIe. 25 so I could mix colors of light with a microcontroller. 25 teaching myself BASIC from a book on my Dad's TRS-80 Model III, then later hacking on dial-up BBS systems. 25 to explore Mandelbrot and Julia sets generated by my own code. 25 when I was an Explorer Scout 42 years ago by loading Fortran punch cards in an IBM 360/44. 25 writing QBert clone on Sega 3000, saving 'basic' lines on tape recorder! 26 because my first computer would only sit with a blinking cursor if I didn't program it. 26 by reading all the public library books about BASIC during 1986-7, before I had ever seen a real computer. 26 by typing BASIC program listings from a children's magazine into my Atari 800XL. 26 in my first semester in college, when I took a required programming course in the engineering school. 26 to calculate as many prime numbers as possible with my dad. 27 after I finished my military service, inspired by the power and freedom it gives to make whatever experience I desire. 27 at the University of Delaware as a freshman with no programming experience; I was so lost! 27 because I wanted an entertaining job. 27 because I wanted to invent something that others would find useful. 27 because I wanted to see the buildings I was imagining in my head out in the world, instead. 27 because in 1977 I got an AMES 65 kit computer. 27 because it was a prerequisite for the Engineering major in college; I liked the professor and thus liked the course. 27 by copying simple games in BASIC from a book into my dad's Timex/Sinclair 1000. 27 by figuring out how to cheat at ZX Spectrum games. 27 by watching my dad program games on a black and white computer console in 1987. 27 by writing HTML with a pencil on paper. 27 from the Commodore 64 User's Guide. 27 in BASIC, an hour before bedtime each night on my father's machine. 27 on a computer borrowed from my dad's office, plotting fractals using polar functions. 27 on a computer with 8 bytes of memory that we built in the high school physics club from a pile of donated relays. 27 on a spring break visit to my father's house, in 1997, when he sat me down with a book on learning Perl in 365 days. 28 FORTRAN in order to model transistor behavior for electronics class. 28 Java to make e-cards for friends and family using applets. 28 because I wanted to make webpages and HTML was for me not enough. 28 because I was going to get a Computer Engineering degree on my way to becoming a patent lawyer. 28 because the superintendent offering me a job pointed to a TRS-80, asked if I knew anything about them, and I said yes. 28 by breaking things, and then fixing them. 28 by writing a BASIC game on a manual typewriter, and being driven by my mom to the local Radio Shack where I typed it in to the TRS-80 I coveted. 28 hacking BASIC on a Commodore VIC-20, to create interactive narrative — bouncing balls were way too mathy. 28 in 10th grade when my world changed with my first Computer Science course. 28 in BASIC on an Amstrad 128 because I couldn't fathom how a computer could possibly do what it did. 28 in QBasic on an IBM AT using a tattered old book full of example programs in GW-BASIC. 28 in a batch file using MS-DOS. 28 on an Apple II, because my best friend and I wanted to create new video games together in middle school. 28 when I booted a Commodore VIC-20 without a cartridge. 28 when I was 11 so that I could beat my dad at Robot Battle. 28 while trying to avoid taking a math class in college. 29 Basic. On the Atari 800. Good times! 29 as an undergrad, to get a job to pay my tuition. 29 because it was easier than writing (and re-writing) specifications. 29 because i wanted to recreate the miniclip dancing bush video using my cousin's head. 29 by playing with my TI-83's BASIC instead of listening to lectures in high school. 29 by taking "Intro to Programming" in college; I had never heard of a computer before that. 29 from magnanimous friends in order to make beautiful things intelligent and responsive to human bodies. 29 in 8th Grade on a Sharp PC 1403 (a calculator with a BASIC interpretor); coded so much that year I had to repeat the grade. 29 in 1963 to impress my girlfriend's father. 29 in BASIC as a way to learn my times tables and it just got more complex from there. 29 in an introductory C++ class in junior college taught by a wonderful female teacher. 29 on an HP-85 with my dad when I was 6. 29 while trying to dig into the internals of the old text-based Colossal Cave Adventure. 29 with a lot of Googling and a strong desire to make something cool. 30 by typing in BASIC example code on a Casio PB-100 programmable calculator. 30 on an Atari ST by reading the omicron-basic-manual during my summer holidays. 30 on a Commodore 64 by reading a book with a BASIC game in it and typing in that game (about 5000 lines of code). 30 starting when I was 12 by trial and error because of my passion to create awesome websites. 30 to simulate model rocket launches with my dad in ninth grade. 30 when my buddy started a company; he gave me a Perl book and told me to make a web gallery of their products. 30 with QBASIC writing an Eliza clone, for fun, around 6th or 7th grade. 31 6809 assembly on MO5 because I wanted to understand the custom tape loader of the first game my parents bought me. 31 at the age of 13 because my best friend did and it looked amazing what he could do with it. 31 in my senior year of college because I wanted to improve my ability to do astronomy. 31 on an Apple IIe so I could draw a picture of my house. 31 on an Italian calculator, the Olivetti Programma 101, in my high school calculus class in 1970. 31 to make a letter writing web app in Perl/CGI for my Amnesty International group. 31 when I was introduced to Scratch in the sixth grade. 31 with an book on introductory programming in QBasic on a DOS machine. 32 because my teachers taught us LOGO in 4th grade and I fell in love with making the computer do what I wanted it to do. 32 because the computer looked like a magic box that did what you told it to, and I wanted to find out how it worked. 32 by copying BASIC code for a simple guessing game from a teen magazine and adapting it later. 32 by dissecting friends' source code to understand what the pieces did. 32 in BASIC on the KC85/3 when I was 8. 32 using the BASIC interpreter on a TI99/4A. 34 at age 12 back when that was still unusual. 34 by writing a text adventure that used a .BAT file to navigate between discrete text files. 34 to write a text based adventure game for my friends with C64. 35 as an extra-curricular in high school with the help of a few friends. 35 because I wanted my own version of Bomberman. 36 because it was the simplest way to draw patterns consisting of 100 circles on ZX Spectrum. 36 in a one-semester BASIC class (with a teletype!) during my sophomore year of high school. 36 when I was twelve, making networked text adventures on the school computer network. 37 on a Commodore 64 so I could text-based games for my Dad. 38 with Ada in my CS 101 class. 39 at an NCR week long training for the NEAT II programming language. 58 using Lego logo to make a robot draw a baseball with sunglasses and a mohawk from the "Major League" movie poster.