custard doughnuts

Since I wrote about building a show password component for GOV.UK I've started noticing other implementations online. Let's take a look at how they're built.

JavaScript frameworks are the subject of much debate in the frontend community. Are they good? Are they bad? Should we use them?

I keep having this conversation and I've stopped enjoying it so I'm just going to write down what I think.

I built a couple of random tools a while back and forgot to talk about them. So here's some words.

I used to do a fair bit of frontend development in my spare time, but in recent years it's been increasingly difficult to find the time and energy to do so.

Today I wanted to make some changes to the CSS of my website. I've got a repo for this that I set up a few years ago. I run gulp, make some changes, everything gets built and minified and I copy the resulting CSS file up to the server. Job done.

Except, this time, it wasn't so simple. Here's what happened.

Sometimes you start building something but it never gets finished. That can be a good thing, because not every idea is a good idea, but sometimes it happens for other reasons. It might be worth doing, but maybe there isn't enough time or money to finish it, or other things take precedence.

This is the story of a project that I started but never finished. I don't know if it would have been good or not, but I'm a little sad that I never got the chance to find out.

Managing or working with developers if you're not one yourself can be challenging. You may not understand what they do or how they do it, or even the words they use when they try to explain it. But don't worry. Here is some advice for non-developers on how to work alongside the techies in your team.