Like anyone, I have a set of skills I'm using pretty much on a daily basis, but also a myriad of skills that haven't been exercised in recent history. This inventory is an attempt to catalogue all of these technical skills.
PHP: I've been writing PHP for 15 years, since college. I've obviously worked in many other languages, but my career has almost always revolved around PHP.
JavaScript: Where PHP has been my backend language of choice, JavaScript has been with me just as long as a front end language. As my career continued to shift away from front end work JavaScript began to fall off my radar, until the advent of things like nodejs, which has brough JS back into my life.
Bash: No one ever lists Bash on their portfolio. I do. Bash can be super powerful and super quick. The fact that you're scripting and have immediate access to all of our command line utilities, how is that anything but glorious. I haven't been using Bash as long as PHP or JavaScript, but still close to a decade.
Laravel: I've been using Laravel for about six years now; I've developed numerous Web Applications and Web APIs on this MVC platform and have made some community contributions in the form of open source packages (see Automation and Architecture)
WordPress: I have a storied history with WordPress as my primary CMS/framework for about 4 to 5 years. I've launched many a client content site on the CMS and even built myself a handful of automation tools.
Node: Over the last couple of years my exposure to and use of Node has ramped up quite a bit to include a solo buid to manage CCPA requirements and deletion requests (with a React front end).
MySQL/MariaDB: MySQL is kind of the defacto database system when working with PHP. For example WordPress only supports MySQL databases. I've been pretty deep into MySQL and its different storage engines. I've spent a measurable amount of time optimizing my own, and other developers queries.
PostgreSQL: I love PostgreSQL for its stricter adherence to SQL standards. I like to utlize it when I can, especially on Laravel projects, though I do conceed that its actual performance benefits are between negligable and non-existant, meaning I usually end up falling back to MySQL to better support other developers more comfortable with it.
NoSQL/Firebase: Firebase has been my go to for NoSQL/Key-Value stores. As you can gather from my frameworks of choice, I'm often in need for structured, indexed database, so in most projects I'm using MySQL or PostgreSQL.
Apache: Like any good PHP developer, I've been using Apache for most of my career for both production and local development. In more recent history, I've used it in a reverse proxy setup along with nginx for the "best of both worlds" in static and dynamic web hosting, though it's always served me well as a local server as well. Lots of experience configuring virtual hosts.
nginx: Nginx has been my prefered web server application for a while now. It's more performant and its integrations with tools like Certbot and Let's Encrypt feel a bit more solid to me. Configurations are also a bit nicer to manage in a JSON format. For running PHP, I've used Apache in a reverse proxy setup in the past, though I've more recently found using php-fpm directly to be just as performant and a much simpler setup.
Tools I am perfectly comfortable with but I don't necessarily get to use on a daily basis.
These include Drupal, React, GraphQL API Development, RESTful API Development, Linux server management, Envoyer, Forge, Git, Gitflow, DigitalOcean
These are languages and frameworks where I either have a smaller amount of experience, or I haven't used these in some time.
These include Golang, Jekyll, jQuery, Vue.js, SQLite, Stripe, PayPal, MailGun, SendGrid, Let's Encrypt/Certbot, OneSignal, Heroku, CloudA, Google Cloud Platform, Java, Spring Boot, Ruby, Ruby on Rails, Python, Django, game development (Unity - C#), data science/analysis (R code), VBA, VB.NET, Microsoft SQL Server, Powershell, C#, ASP.NET, and CNC machines