Deciding if you want, need, and can afford to hire outside technical help can sometimes be a quick decision fueled by a need to firefight, but there are some strategic choices that can make the experience more successful for both your company and the other party.
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?
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.
Google has started including your page's loading speed in its calculation of SEO. To help your site (and the web) get faster Google has introduced an excellent tool for measuring your website's performance called PageSpeed Insights. These posts will walk through the criteria it uses to gauge your site and discuss their pros and cons.
- ← Previous
- Next →