I've been noticing more and more recently how different types of work line up with how my brain works. Am I doing what want? Am I pushing against the current? And also paying attention to various tendencies in others as well. How can I balance this out.

Finding it difficult to read output to the console when debugging? Try this quick tip for debugging in Python.

After all these years I’ve still got a soft spot for CSS. I’ve been doing some poking around as I haven’t done a ton of CSS work recently and was feeling kind of out of the loop and a little itchy for some CSS fun. One of

Consider this a plug for using the good ol’ debugger as part of your Javascript workflow. We’ve all done the thing where we throw console.logs all over the place, but I’m here to tell you that the debuggercan be your friend. It's not that scary. Really. How

Did you know you can split your form inputs from the form and still submit a group of inputs together as the same form? Well, you can.

I recently ran into an issue when working on a deployment that ended up pretty clearly pointing to some issues with environment variables. The application is leveraging PM2. This is a really handy tool most of time time, but there is also a lot of hidden corners and black magic

One of the core selling points of writing styles using Sass (or SCSS) is being able to use variables. This isn’t as novel a concept now that we have CSS variables native to CSS, but it’s still a big part of Sass. They work as you’d expect

One of the core skill-sets a developer needs are some strategies to handling data. I don't know about you, but I feel like I'm always doing this type of work. Arrays are a super common structure we encounter a lot in JavaScript and ES6 brought along with it some pretty

One of the most basic, yet most useful functions of a preprocessor like Sass is the ability to leverage variables in your stylesheets. This little feature can save you lots of time and shield you from many headaches. There are a variety of strategies for using variables, but we're not

I've been spending a fair amount of time working with microdata recently and I've found this Google Structured Data Testing Tool an incredibly useful to have a tool to help me test whether or not my markup has been correctly written. This tool allows you to either analyze a URL

This post from html5 Doctor is more than four years old, yet it's still one of the best resources on microdata that I’ve found. If you’re working on the web then you should have some knowledge of microdata. Essentially we’re able to add more semantic meaning to

Here’s a brief introduction to the concept of microdata from Google. It’s a nice resource with a handful of examples attached. SEO is definitely something that microdata improves so info coming straight from the horse’s mouth is something we should pay attention to.

Reading through a spec is not always super useful for actually understanding how to use it, but it isn’t a bad thing to have on hand.

This is the where the microdata spec is documented. In general, I'd say that microdata can be a bit confusing to start, but this section of schema.org is quite insightful (as compared to the actual documentation). I highly recommend reading through this area before digging to far into microdata.