I started assembling my own PCs from about 1995 to extract every possible Mhz for low budget (yeah, overclocked dual-socket Intel Celeron 400 ftw).
About 1998, during school, pocket money was just not enough so I started building my first website for a near company using HTML 4 and Dreamweaver - yes, already back then table layouts where old and replaced by CSS layouts.
After that, playing computer games and life and university became more interesting and it took until 2005 when I started doing websites again. I started two companies, one with my mother and my freelancing business (the latter till this day). During my 3 years at University of Klagenfurt I learned to "code" (beyond HTML and CSS) with some small Java projects.
From there I did mostly PHP projects with Mambo/Joomla and Serendipity but also some e-commerce sites with xt-commerce, Oxid e-sales and some other projects with different libraries and CMSes. Around mid 2013 I started to work together with Zensations on Drupal projects up till today.
Currently I'm doing mostly Drupal architecture and backend development and leading/collaborating with fellow developers on tailored solutions like e-commerce, international NGO platforms with lots of API integrations from multiple different vendors (payment providers) and internal systems (CRM, ERPs, accounting) via REST, SOAP, XML, GraphQL or even CSV files.
Past experience shows that different use cases need different solutions. In the case of Drupal for example there are more lightweight solutions for running a small site or a blog - when the flexibility of Drupal is not needed. But if you want full control over data structure and/or fully decoupled CMS, custom checkout flow, etc. - then Drupal might be the right choice. As said, it depends - so let's find out!?
I have started working intensively on Drupal projects since 2013. We were working primarily on bigger projects with lots tons custom code written. Integrations from external APIs to ERPs, CRMs, Single-Sign-On (SSO), newsletter systems or other internal custom systems and data pools. Big projects with Drupal Commerce and highly performing Drupal apps used for big votings handling well over 1M votes and users.
tooling Features, Drush (Drush make for continous deployments), Redis, Drupal custom installation profiles approach, DDEV, platform.sh CLI
functionality Views, Ctools (ctools content-types, access, context plugins), Entity API, Rules, Commerce, Migrate, Token, Pathauto
theming Panelizer, Page Manager, Panels, Panels Everywhere (Styleguide tailored markup output), Libraries API, Styleguides (Fabricator) used to separate design/CSS from theming in Drupal
tooling Drush, Console, Config-Split, Config-Ignore, Redis, Memcache, Acquia BLT, DDEV, platform.sh CLI
functionality Core (Views, Entity API), Commerce, Migrate, Paragraphs, Token, Pathauto
theming Most works with new Twig layer, no more Panelizer, Paneles suites needed, yay Styleguides (PatternLab)
Git, Bash, PHPStorm, Atom, NodeJS, NPM, Yarn, YouTrack, Jira, Bitbucket, Github, Slack, Mattermost
Laravel, Lumen, TailwindCSS, Wordpress, Oxid e-Sales, Magento