TrevorCash

With any tech stack as a web developer you must become well acquainted with HTML to make sure you have the most accessible and intuitive experience for the user. I often spend time browsing MDN making sure I am familiar with existing elements to make sure I can produce the most native experience for the user as I possibly can

As with any web developer CSS is a major part of the process and is a must know. I always strive to learn more to add to my tool belt to incorporate more pure CSS solutions to boost performance when possible

TypeScript is the default for everything I write now. Leaning on the type system to model the data an application actually works with catches a whole class of bugs before they ever reach a browser, and it makes handing a codebase off to another developer far less painful. Most of my day to day is spent writing typed components, composables, and API layers.

SCSS has been a part of my tech stack from the beginning of my career. While it's not a make or break I do believe it makes writing the styles much more fluid and organized whether it's nesting styles to creating deep loops to generate a style sheet for extensive design systems

Maybe my favorite of them all next to JavaScript. Creating highly dynamic reactive experiences to whatever the situation is thrown at it is one of my favorites. I have a rather deeper knowledge in React and strive to learn more and more when I can.

Vue is what I spend most of my time in these days. I've led a team building large Vue applications with TypeScript, Pinia, and Vite, modernized plenty of legacy options API components along the way, and covered it all with Jest and Cypress. The composition API paired with a good store makes it really easy to keep complex state readable and testable.

I started learning Next JS with sites I have built for local businesses in my area. I tend to lean towards Next JS over Gatsby for the development experience and I enjoy learning how to leverage the tooling to enhance the performance of my websites

Surprisingly enough I never used git until I started my first job which sounds absurd to me now. But over the years I've became more and more comfortable by knowing how to leverage it, making cleaner commits, and being able to debug and discovering when and how they came about to get quicker understandings on how to fix the issue

Another element to many stacks I enjoy very much is Node. I enjoy writing anything that will save time or crush a tedious task in a blink of an eye. I've also wrote a good bit in Node while tackling Project Euler problems to grow my familiarity and improve my efficiency since those problems are very large scale in terms of looping and calculations

A CMS I have been rather familiar with over the years is Sanity. While great for small projects like my use cases it is also scalable and easy to build custom interfaces to match content authors needs scalable. I've became really comfortable building these custom one off solutions and discovered some best practices to keep in mind when building a Sanity project

Over the years I always had to make tweaks to webpack builds and was never fully comfortable while doing so, so I took the time to take a deeper dive at understanding how to leverage it in my favor and it has produced great results. These days most of my builds run on Vite, and the same habits carry over. Whether it's improving the development experience, performance, or matching requirements for desired outputs I can get the job done.