I'm old (a few years shy of 50), and a second generation professional programmer. E.g.: when I was in kindergarten, my father's main job was maintaining the COBOL compiler on a particular series of Sperry-Univac mainframes. I grew up in a house where the scratch paper for grocery lists was punchcards because my dad brought home reams of unused ones when they were being thrown out in the early 80s. (Fun fact: with a sharp pencil, it's totally possible to fit a full D&D character sheet on the back of an unused punchcard)

So for "how did I get started", I was born into it; I was of the age when you'd get magazines in the mail with code to type in (later, the magazines came with audio cassettes with programs on them). So BASIC initially, then in high school my dad got us a copy of Turbo Pascal and set me loose on that. (Plus tiny TSRs in x86 assembly)

I had a few mid- and upper-level programming classes in undergrad., but was a pure math major, not CS. (so didn't get any CS theory classes, though I did have a job working for campus networking people) After grad school, I got a job writing code in java and perl for a company you've never heard of unless you were in a particular corner of the finance world in the late 90s/early 2000s. I'm now on my third or fourth employer, depending on whether you count a buyout that kept the team intact but moved offices as a change in employer.

My day-to-day coding these days is primarily in python and C++, but in the past six months it's also included work haskell and go, not to mention sh scripts and the weird groovy dialect used in Jenkins.

Oddly enough, my hobbyist stuff these days has all been HTML+javascript because it just makes simple GUI demos so easy. It's kind of wild coming from the mid-90s when I was heavily involved in early web stuff at my undergrad school to this new world where javascript mostly works and is a basically sensible language. Recent-ish projects have included a solver for the NYTimes "digits" game, a Mandlebrot set viewer and the "come back for more meeting" timer at breakmessage.com.

I consider myself both but I'm progressively leaning more and more professional.

First off, I'm 100% self-taught. I discovered Linux around 2003 and immediately learned, several times, how not to install it and multiple really good ways of destroying data on a hard drive. I have had the open source / Linux bug ever since.

I went to school for CS for about two semesters before I dropped out. I then started off my career in IT of all places, I was a helpdesk IT administrator. About 12 years ago I landed a job where most of my responsibilities revolved around Linux servers and workstations (academic research lab). I started learning more about systems automation and configuration management tools/languages/strategies. This constantly lead me down roads involving reading source code for projects that I used day-to-day when something didn't go right. This lead to filing bug reports and ultimately making a pull-request here or there to fix my own issues.

Fast forward two jobs and 10 years and I've migrated to a role where the majority of my day is writing systems code. Most of it is in Go now but I still maintain a handful of Python/Django applications as well. The majority of the tools I write for work are focused on developer experience, cloud automation and internal CI/CD pipelines. In my personal time, I contribute to a number of open source projects.

Pro and hobbyist. I started by learning Basic back in the late 1970's. Got a EE with strong emphasis on Analog and DSP. Did analog for test and measurement systems but had to add microprocessors (and EPROMs and RAM) to build the systems that control the analog. For embedded I learned C. For PCs I did Basic, Forth (ugh), Turbo Pascal, Delphi, then C#. I'm heavy into unit testing. I did web development as well, back in 1997 to maybe 2010. Perl, PHP, MySQL, Linux, then Drupal. A lifetime ago.
I can't tell what I'm working on now (professionally) but hobby-wise I do a lot of arduino stuff and some of it has been a blast. I did an automatic dog food dispenser a few years back that was an amazing tour of engineering your way out of failure. The look on my dogs face when the MK1 version sent a fire-hose stream of dog food across the room was awesome.

I've been a professional software engineer in the game industry for 22 years now. I started off in school at first on Apple computers with Basic, then when I got a graphing calculator in school I started writing tools for school work and games on it all the time. After college, I wasn't sure what sort of software I wanted to work on (dot-com era), but one of my good friends talked me into applying to some game companies. I've been in a bunch of different companies since then but right now I'm working on online systems for one of the biggest online games.