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

I started off 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.