I started teaching myself HTML by building my first website in 1998, and CSS in 1999 or so when I customized my very own LiveJournal. But my experience on the internet dates back further, to 1990, when we got our first ISP, Prodigy.net. I've been enamored since.
Throughout my career, I have been lucky to join teams where I learn new technologies, and new development languages. The best part for me is that I get to use them on-the-job so it's not just theoretical. I do like to join classes and workshops, as well as keep myself sharp by using online classes like Codecademy. Yet there is something great about seeing these new languages already working in an environment; how code compiles real-time, how your code integrates into a working, customer-facing environment, and how different stacks can be utilized in highly-customized technology stacks.
Here, I'd like to show you how much of that real-world experience I have.
The bulk of my work experience is in e-commerce. Though most of my work has been on the front-end, I have been able to collaborate with back-end teams to integrate code, and learn how all of the pieces of the puzzle fit together. Early in my career, the e-commerce platforms I coded for were on PHP-driven stacks with assets managed in SQL databases. As Web 2.0 was ushered in, I saw more and more single-page web apps, and my latest experience has been in light-weight JavaScript Node stacks.
The Agile Software Development Lifecycle has gained a lot of popularity in the last five or so years, and for good reason. In addition to using the methodology, I've also got experience using project-planning and bug-tracking tools that allow teams to be more agile day-to-day. Besides standups and scrums, these two areas are the foremost areas in development that benefit from agile planning.
Aside from coding, I also have experience in design, retouching, image optimization, and composing complete images. Of course, this requires some working knowledge of Adobe!
The very first Analytics tool I used was the Urchin marketing pixel. About two or so years after I learned Urchin, Google acquired them, and we began using Google Analytics, which was based on the Urchin technology. Though I've experience with a couple others, Google Analytics remains the easiest instance to propagate, and the easiest dashboard to pull data from.