I tuned in for just a few seconds, but had to turn it off. That’s not enough time to make a reasoned judgement about the content of Apple’s latest keynote of course, but I just couldn’t continue watching.
Earlier this month I attended UpFront Conference, an event organised by Dan Donald and other members of Manchester’s digital community.
I recently learnt about a security exploit that can occur when pages served over HTTPS use HTTP compression. Secure or fast, pick one?
The feedback loops and network effects permitted by the internet have allowed companies like Google, Facebook and Amazon to become near-monopolies within their chosen fields.
Finding parallels between redecorating my house and redesigning a website.
I’ve returned to 68 Middle Street just in time for the start of 100 days, a collaborative project where the aim is to complete a creative process every day for one hundred days.
Matthew Butterick’s scrutiny of Medium reveals it to be “a form of human fracking”:
In “Death to Typewriters,” Medium insists that the typewriter is its “sworn enemy.” In certain typographic details, maybe so. But as a device that imposes homogeneous design, Medium still has a lot in common with the typewriter.
In fact, its ethics are actually worse than the traditional typewriter. Why? Because Medium’s homogeneous design has nothing to do with limitations of the underlying technology (in this case, the web)… it’s a deliberate choice that lets Medium extract value from the talent and labor of others.
Convenience always has a cost.
SVGOMG is a wonderful example of how to build a web app in a responsible and accessible way. I asked its creator, Jake Archibald, a few questions about how he designed and developed this native-feeling SVG optimisation app.
For the last year I’ve been working at the Guardian under the leadership of a creative director. I’ve never worked with a creative director before – at least not in the traditional sense – and have found this to be a fascinating yet also frustrating experience; for the first time in my career I’ve not the been the arbiter of good taste.
I’m leaving the Guardian and going freelance in March.
My contribution to this year’s 24 ways attempts to tackle one of the most difficult aspects of web development, naming things:
Working in-house may mean working with multiple developers, perhaps in distributed teams, who are all committing changes – possibly to a significant codebase – at the same time. Left unchecked, this codebase can become unwieldy. Coding conventions ensure everyone can contribute, and help build a product that works as a coherent whole.
Even on smaller projects, perhaps working within an agency or by yourself, at some point the resulting product will need to be handed over to a third party. It’s sensible, therefore, to ensure that your code can be understood by those who’ll eventually take ownership of it.
Put simply, code is read more often than it is written or changed. A consistent and predictable naming scheme can make code easier for other developers to understand, improve and maintain…
This is the fourth successive year I’ve been involved with 24 ways (including last year’s redesign), although this article rounds out a year in which I have been deliberately quiet in terms of writing and speaking. I don’t intend for that to be the case in 2015.
Looking for older posts? Browse the archive