How to Measure Technical Success

Measuring a team or single developer's success is tricky. It's well documented that any kind of performance measuring is ripe for being gamed. You spend weeks evaluating and hiring only the smartest people available; they know how to bump up their numbers.

So how do you determine if a team is firing on all cylinders?

Read More

How to Perform a CSS Audit: Stylesheets Don’t Have to be Awful

When we begin work on an existing codebase, one of the first things we will do is a CSS Audit. The main impact of disorganized and poorly maintained CSS are slower development as a team wades through unclear code, and a broken site, as poorly scoped selectors result in collisions and overriding of styles.

This audit process assesses how organized the project's CSS is, how up to date the pipeline for evaluating and building it is, and how well structured and disciplined the team is that writes the CSS. Here are the steps you could use to run your own CSS Audit.

Read More

When to Level Up Your JavaScript

Websites grow in fits and starts, often with different owners and contributors over time. Some features are made in a time crunch where others had time for planning and testing. There are some excellent strategies to help keep JavaScript fast, free of regressions, organized, and well tested. They are sometimes overkill for a smaller project, which leads us to The Problem:

Right-sizing your JavaScript tooling from the get-go is impossible, because projects grow in unpredictable ways

Read More