Opens blog, blows off the dust, sweeps away the cobwebs.
Apparently I haven’t published a blog post in 2 years (something something pandemic). Time to see if these old writing muscles still work.
During 2020–21 I withdrew a lot from doing tech stuff. Online-only meetups were unenjoyable, and I stopped watching video recordings from conferences, stopped working on my own open source stuff, stopped writing blog posts. What little coding I did do was limited to simple scripts, or very occasional contributions to the MDN compat data project. (In fact, that was a topic of a different blog post that I never got around to finishing.)
With enforced working from home and spending all day staring at a screen of code in my room, I really didn’t want to spend more time doing the exact same thing at night.
What I did instead was throw myself back into the world of origami.
There was a helluva lot of stress and preparation involved in trying to make a rather dry topic sound interesting for 20 minutes. In the end, the results were worth it, but I was reminded why it had been several years since I’d previously given a conference talk. It will likely be several years before I do another one entirely from scratch.
I got some good feedback about the talk, but there were two parts I was particularly pleased with. Even if the presentation had tanked, I’d still have been satisfied with the completion of two slides. Mainly because they gave me the excuse to muck around in design tools and pretend I’m a real designer.
These items were the mashed-up browser logos, and the “IE-lephant in the room”. I had enough people talk to me about the images after the talk that I’ve decided to pop them online for all to see. Both images are linked from this post in SVG form, under a Creative Commons Attribution 4.0 International license. That means you’re free to copy them, modify them, do whatever… but with an attribution credit too.
Some-in-one browser logo
The idea of smooshing many web browser vendor logos into a single image was one I had years ago. This talk was finally the excuse I’d been looking for to actually do something about it. I’m perhaps far more pleased with the result than I should be.
I’ll refrain from calling it an all-in-one logo, as there are many more browsers available than just Chrome, Edge, Firefox and Safari. Important note: This isn’t intended to favour any one browser over the others. My intent was for this image to equally (but light-heartedly) offend the designers of each of the featured logos. 😉
It would also be hypocritical of me to request attribution without also giving some in return. So for completeness, here are the links to the original vector images that went into this (before a lot of cleaning, nudging, and mangling of the files in Illustrator):
Of course, as soon as I’d finished the mashup image and put it my presentation, 2 of the 4 logos became outdated. Firefox has just got an updated and simplified logo, while Edge’s logo has had a complete revamp for its move to a Chromium base. Oh well, I guess I’ll have to make a Version 2 at some point.
In contrast to the well-planned logo mashup, this image was pretty much a spur-of-the-moment joke. Its only purpose was to be a punchline — “I’ve only talked about support for modern browsers; but what about the elephant in the room?”
I’m not really sure it has any reusable purpose beyond that joke, but I’m still rather pleased with the result, so I’m sharing it anyway.
This year I took the approach that I would write some minimal notes after each presentation. This meant that I wasn’t so distracted by writing notes that I stopped absorbing the presentation content. It also gave me time to reflect on the presentation in “down time” and distill the key points. (The only exception to the rule was when I wanted to capture a link or an exact quote.)
When trying to summarise the presentations for the write-up, I forced myself to give a synopsis of each talk using only one sentence. While doing this, I suddenly remembered one of my old favourite sites that I hadn’t looked at in a long time: Four Word Film Reviews.
Inspiration struck, and this post is the result. (Though unfortunately it probably doesn’t make sense to anyone who wasn’t at the conference to begin with.)
Last week I went the Web Directions South 2013 conference, my first experience of WDS. Now, within Atlassian, we’d normally rely on WDS old-timer Ben Buchanan to do a great big write-up of the conference each year.
Unfortunately Ben left Atlassian earlier this year, so I took some notes of my own during the presentations, in order to post a recap blog within Atlassian. Then I remembered I have this blog as well, and in the sprit of “The Road to Hell…” I figured it would be worth re-posting the content.
Other than the keynotes, the conference was split into two tracks: Development and Design. Obviously no-one can see all the presentations, so I just wrote up what I saw.
Any quotes I’ve listed are based on my memory, and therefore might not be exactly right, but the message is the same. I apologise to anyone I may have misrepresented.
The opening credits this year were done by Small Multiples. A glowing blob traveled across a dynamically generated landscape littered with the speakers’ names, using WebGL. The credits are detailed (and can be played) at http://www.south.im/; during the breaks between talks people could play with an interactive version where you could control a heap of landscape/lighting settings.
Opening keynote – Rachel Binx: People, Not Users
I didn’t take many notes from this one, mostly because I forgot to.
Described the differences between the “prescribed self” (single identity; Facebook, Google+) and the “flexible self” (multiple personas; Twitter, Blogger)
Highlighted some quotes from Zuckerberg and Brin talking about the death of privacy, and pointed out that only incredibly sheltered and privileged people could make those statements
“Facebook is a game of whack-a-mole with privacy settings”
Andrew Betts: Conquering the Uncanny Valley
Andrew is from FT Labs, the division of the Financial Times responsible for playing with new web tech that has put out several interesting and useful JS libraries (like FastClick, currently used in Confluence Mobile and JIRA Mobile).
I took a lot of notes for this one, but won’t dump them all here (but if anyone’s interested I can put them somewhere else).
The 3 key things for mobile web apps:
Keep all transitions to 16ms or less for smooth frame rate
No pauses more than 100ms – anything under 100ms feels instantaneous
Matching expectations of native apps – don’t venture into Uncanny Valley territory
Network performance – other than the already-known cost of making multiple network requests on a mobile device, he also pointed out that the speed of a network request is dependent on what the CPU is doing at the time, and whether the radio antenna is in an active or dormant state.
They wrote all their REST APIs to handle being called in a batch, then on the client their API wrapper transparently auto-batched any API requests within a certain time period and only sent off one network request.
Typically 70-95% of web page data is image, so optimising them is especially important. Their testing indicated that only loading one high-resolution, highly compressed image and scaling it down was better than loading different images for different resolutions. “Image decoding is probably the most expensive thing you ask the browser to do when your page loads.”
Rendering – various techniques to improve rendering performance, including disabling any hover effects when scrolling a page. Perf hits can also come from unlikely sources (like animation of one element being slowed by box-shadow on an unrelated element).
They wrote FastDOM to do async DOM reads/writes and batch them up, using requestAnimationFrame
Storing data – There are too many options, each with pros/cons. He came up with a brilliant “dysfunctional family” metaphor to describe the difference between cookies, localStorage, IndexedDB, AppCache and the Files API
Mobile devices have limited storage space, so they halved the storage requirements of their strings by doing a clever trick that relies on JS strings being UTF-16 (well, UCS-2, technically)
Perception – When you can’t make it any faster… make it seem faster
Excellent breakdown of the principles of animation and how they should be used in interfaces. Pasquale is a designer and animator who was trained in classic animation (the hand-drawn type).
He wrote a brilliant article a little while ago on “Transitional Interfaces” which got him invited to speak at this conference, and he didn’t disappoint. A remarkably comfortable and humorous speaker for someone who had never done a public presentation before.
His key points to remember about animation in interfaces:
Static interfaces suck
Animation is a clue
Great animation feels invisible
Learn from the classics
A lot of the talk was showing examples of sites/apps that do animation well, those that don’t do it well at all, and how they can be improved.
“Use animations between states to avoid merge conflicts in our brains”
Twitter’s loading of new tweets is “a slap to the eyeballs”
Quartz Composer is “like trying to draw with a microwave”
“I wanted to start a site like Dribble but for animators; only instead of circle jerking over 400×300 flat images, it would actually be useful”
Ryan Seddon: Flexbox
This started a round of 3 shorter talks in the development track, so I didn’t have many notes.
Good overview of the basics of flexbox, the different specs and decent real-world use cases. Rather than hyping up something just because it’s new, he advocated use in moderation. Use it for small modules, but don’t overdo it (“use it where it makes sense”) – still use floats or inline-block as needed.
A CSS-focused talk about splitting up old, bloated, messy codebases into neat, modular components. Fiona has had to do this at several different jobs and has gained a fair bit of insight into how to Get It Done.
Build the simple components first – find commonalities and abstract from the start
Good naming for components / classes is important – make them generic as possible, but not so generic that they’re unusable like “box1” (try “box-feature” instead)
Make components “just work” – don’t make developers resort to clearfixes
Namespacing using SASS/LESS nesting can be good, but it’s better to just include the namespace in the class name itself
The most important thing is communication. Have a code standard within a team and write a living style guide.
Jared Wyles: CSS – (Finally) Making the Web a Less Blocky Place
Jared hates CSS, but he likes that there are now tools available that can help us avoid writing hacks. He showed off two CSS features that have been created by Adobe: Regions and Shapes.
Regions allow you to write content in one element, but have it flow into multiple defined regions made up of other elements. This makes it possible to do true magazine-style layouts where text content flows into multiple columns. It’s supported in the latest versions of Safari because Adobe have been putting a lot of work into submitting patches to Webkit. There’s also a JS API so that you can query named regions.
Shapes allow you to define non-rectangular content areas using basic polygons, which is something that CSS has needed for a long time. It’s early days so far, but looking promising.
“While we’ve been struggling with these basic layout concepts, the print industry has been laughing at us.”
Closing keynote – Maciej Cegłowski: Barely Succeed – It’s Easier!
Words can not do justice to the humour of this talk. Maciej is the creator and maintainer of http://pinboard.in/ and spent a large part of the presentation bagging out the bullshit of startup culture, using bizarre slides about animal parasite lifecycles.
Startups are constantly trying to disrupt the publishing industry and the film industry and the record industry, but they’re using the same broken business models and not realising it. They’re not disrupting the business of running a business.
There’s a different model to follow: Barely Succeed. A lone operator charging a reasonable fee for a high quality but narrow-scope service. Keep control and be free to change things to maintain the vision.
“You too can find success within your mildest dreams”
“I’m a Slav. Slavs believe the world is misery and pain. This worldview makes it difficult to be a motivational speaker.”
Opening keynote – Scott Jenson: Beyond Mobile, Beyond Web
A wonderfully inspiring talk about how to think for the future and stop using “default thinking” when trying to come up with future devices. Scott created the first Human Interface Guidelines at Apple and this talk is worth watching when the video gets posted online.
Stop thinking everything has to be/have an app.
When making things “just work,” beware of false positives.
Don’t forget that “smart devices” don’t have to mean putting a touch screen on your toaster. Things can be “barely smart” – e.g. broadcast a simple URL via bluetooth that points you to a support page for that specific model.
When coming up with something new, closed and proprietary will win… at first. Then open and shared will come roaring past and take over. It’s happened before, it will happen again.
Products and features should be evaluated by the golden rule of Value > Pain
If value goes up, but pain doesn’t, it’s a win
If value stays the same, but pain reduces, it’s a win
Forget responsive design – imagine if you built a website designed to work on 2 or 3 different screens at the same time
“I’m not going to play World of Warcraft on my toaster”
“You know what QR codes are called, don’t you? Robot barf.”
“There is no ‘Cloud’; there are [proprietary] Clouds and they don’t like each other”
“We evaluate tomorrow’s tech by how well it handles yesterday’s tasks”
“Everyone wants innovation, but no one wants risk.”
Troy Hunt: Hack Yourself First
Decent overview of using security tools to try to break your own sites/apps before letting the public do it. He used various techniques to highlight just how easy it is to get free airport lounge wifi, get a free credit card number, and do man-in-the-middle attacks (see the link to the right).
An overview of how the people at MailChimp collated all their disconnected fragments of user feedback, stats and research into one giant repository of information using Evernote. By careful use of notebooks and tags (they tagged by feature as well as personas) they were able to gain new insights that they hadn’t seen before because the data wasn’t in one place.
They got every department of the company to start sending data to a shared Evernote account, automating it as much as possible. They even took screenshots of Survey Monkey charts and relied on Evernote’s OCR to convert them into searchable text fragments.
The other problem they had was at the other end of the process. So instead of writing 40-page research documents that would be read by no-one, Aarron teamed up with a video specialist to create 2-minute videos detailing the research. Suddenly everyone in the company was watching them.
This started off with a quick discussion on how browsers render page elements, and in what order. But rather than focus on the complicated rules (“I don’t expect anyone to remember that spec”), he focused on how to use Chrome dev tools to debug layout/stacking problems.
Some of the experimental features of Chrome dev tools are fantastic. The bit that astounded everyone was being able to analyse page layouts and paints frame-by-frame, with a replay tool that also gives you an interactive 3D view of the paint area at that point in time.