Skip to main content

Weekend Reading: Valentine’s Day

Valentine’s Day finds me sitting in a client’s office, watching the rain hammering against the window, hoping it stops for long enough for me to make the forty-five minute walk back into town later.

This week’s post is pretty code heavy. The web is changing (as usual) and lots of stuff is coming - or at least being discussed - that will help us produce better, more flexible designs on the web.

Flow Fields

Tyler Hobbs

I love generative art, but it always makes me wish I had paid more attention in maths at school. This article by Tyler Hobbs melted my brain a bit, but was fascinating all the same. When I have time I’d really love to give some generative art a go.

You can see more of Tyler’s art on his site, where he also has a shop.


Lots of discussion about the future of CSS at the moment. First off, this article on CSS IRL on whether or not there should be a CSS4. Michelle summarises the position succinctly.

Do We Need CSS4?

Michelle Barker

Essentially, the argument against is that the term CSS4 is fairly meaningless except from a marketing point of view. The counterargument is that marketing is exactly what we need to push uptake of new features and convince businesses to invest in bringing their websites up to date.

More on this from Chris Coyier over at CSS Tricks.


Towards Responsive Elements

Brian Kardell

Next up, some news about container queries! These are something the development community have been wanting for a long time, but from what I gather they are incredibly complex to implement, so movement from browsers has been seemingly slow.

This isn’t for lack of willing though. Brian Kardell explains, and simultaneously sheds some light into how difficult it is to get new ideas refined enough that they can be turned into a specification and implemented in browsers.


Native image lazy-loading has hit Firefox Nightly. It’s been in Chrome for a while, but good to see it becoming more widely supported.


Agile as Trauma

Dorian Taylor

The Agile Manifesto is an immune response on the part of programmers to bad management. The document is an expression of trauma, and its intellectual descendants continue to carry this baggage.

Dorian Taylor

Oof. That’s quite an opener. Agile - for anyone who doesn’t know - is a hugely influential software development methodology that has become almost ubiquitous since the Agile Manifesto was released almost 20 years ago.

If you’re interested in management and project organisation (and who isn’t?), this is a fascinating examination of the origins of one of most popular methodologies around.

If you enjoyed this, there's a number of things you can do:

For more of this kind of thing, subscribe to the RSS feed.

Send any comments or questions to [email protected], or use the form on the home page.

And if you're feeling particularly generous, please like, retweet or share this post on Twitter. It really helps me out.