Raw size isn't enough A few months ago there was a sequence of posts to Hacker News about various “clubs” you could post your small website on: the 1MB Club, 512KB Club, 250KB Club, and even the 10KB Club. I think those are a fun indicator of renewed interested in minimalism, but I will say that raw size isn’t enough – a 2KB site with no real content isn’t much good, and a page with 512KB of very slow JavaScript is worse than a snappy site with 4MB of well-chosen images. ...[Instead, it's about] an “ethos of small”. It’s caring about the users of your site: that your pages download fast, are easy to read, have interesting content, and don’t load scads of JavaScript for Google or Facebook’s trackers. Ben Hoyt, The small web is beautiful benhoyt.com minimalismcontentsize
The quality of thought It is the quality of thought and the information we use that determines yield, not the size or quality of the site. Bill Mollison, Introduction to Permaculture thinkinginformationsize
As inanimate as it was gigantic A Fragment by John Ruskin blog.ayjay.org And among such false means largeness of scale in the dwelling-house was of course one of the easiest and most direct. All persons, however senseless or dull, could appreciate size: it required some exertion of intelligence to enter into the spirit of the quaint carving of the Gothic times, but none to perceive that one heap of stones was higher than another. And therefore, while in the execution and manner of work the Renaissance builders zealously vindicated for themselves the attribute of cold and superior learning, they appealed for such approbation as they needed from the multitude, to the lowest possible standard of taste; and while the older workman lavished his labor on the minute niche and narrow casement, on the doorways no higher than the head, and the contracted angles of the turreted chamber, the Renaissance builder spared such cost and toil in his detail, that he might spend it in bringing larger stones from a distance; and restricted himself to rustication and five orders, that he might load the ground with colossal piers, and raise an ambitious barrenness of architecture, as inanimate as it was gigantic, above the feasts and follies of the powerful or the rich. architecturesizescale
Problems With Agile UX A Podcast by Laura Klein & Kate Rutter www.usersknow.com So that you can get feedback on it and make it betterI'm sorry, I love engineers
So that you can get feedback on it and make it better Fascinatingly, one of the other big complaints people had about agile is no iteration. I don't understand how being in an agile environment makes people less iterative, but somehow that seems to be the case. And I think it's because people misunderstand and think that agile is just about putting features out faster, and not about the important part, which is getting something in front of users faster so that you can get feedback on it and make it better. The most rewarding iterationsTo anticipate all the uses and abuses agileiteration
I'm sorry, I love engineers People are afraid to let design have time to actually figure out the right thing to make, because "whatever will the engineers do?" – fuck you, there's plenty for the engineers to do. Go fix some technical debt. Go fix those 700 bugs that you de-prioritized or marked as won't fix because you're an asshole. I'm sorry, I love engineers. I don't know why I'm yelling at them. But you know, there's plenty for the engineers to do. There's all sorts of cleanup. They can work on dev-ops stuff! They can work on their build process! Make it faster! I'm not worried about keeping the engineers busy. If you think that the only thing that engineers can do is build yet another stupid feature that nobody is going to use, then you're a garbage designer and you should quit. ...Happy 2020 everybody! engineeringuxfeaturesrepair