I believe that a good developer understands the whole development pipeline.
From the drawing table all the way to making that final commit and releasing the product into the world.
My skillset is a product of my curiosity for new technologies and languages, and by solving the problems I face.
My journey into programming started 17 years ago, I was a kid with an insatiable
curiosity and a
need to solve every puzzle.
I had a subscription to a magazine for kids about science (Zo Zit Dat, Dutch people might know) which had an article about pranking your parents with a fake Blue Screen of Death, written in QBASIC.
This was the first code I ever wrote and I stored it on a floppy drive, ready to prank my parents.
The first few times was fun until I noticed the joke became stale so I started modifying my little script which in turn turned into creating new things, at that moment I wondered if there was more of this and went to the library to investigate and got some very old books about XML, HTML, Java and C++.
Of course I had no clue what it exactly was and after a little reading I decided that C++ and Java were too complicated for the moment.
XML seemed the easiest to understand so I learned that first, but found no real use for it apart from helping me understand the structure of a HTML page which was the next thing I started learning. Remember those ninetees websites? They used Netscape Navigator as browser to show examples in that book, but it didn't matter to me, I could finally create art.
This was fun for a while, but I wanted to inventorize my CD collection on a website I made, with the hopes to publish it one day and have a lot of people using it. This eventually led me to PHP which I learned the only way I knew at that time: I got a book from the library.
Eventually the Internet became a little better and I could find more things to learn (Would it be related to developments at Google?)