Weekend Reading: Ess Vee Gee
So far today I’ve spent several hours grouping all the countries in an SVG map of the world by continent.
As well as exposing the limits of my geographical knowledge, it’s also led me down a rabbit hole of searching for tiny remote islands on Google Maps, and wondering what it would be like to live there.
Maybe it’s because I already live on a fairly small island that I’m so fascinated by other, even more isolated communities.
Understanding Team CultureAnton Sten
But as discussions were about to finish up, he said that “as such an important part of the work is to help form the culture, he strongly believes that I should be on-location at least 4 days / week”.
I was a bit amazed to be honest. I admit that there are benefits to working in the same location, but I was baffled that people still so strongly believe that physical presence is needed in order to perform work.
The discussions have left me wondering why this struck a chord inside of me and what I believe.Anton Sten, Understanding Team Culture
Some interesting thoughts from Anton (and other members of SuperFriendly) about what makes a team culture. This especially resonated with me as the majority of work I do is remote, and there’s a definite difference between the cultures of the different organisations I work with, even when they’re using the same tools to communicate (e.g. Slack and Zoom).
Some Imaginary CSSTyler Sticka
The other day I was using CSS grid and custom properties to solve some problems that would have seemed almost impossible only a year or two ago. This made me wonder: What CSS could I be writing in a few years that might seem far-fetched today?Tyler Sticka, Some Imaginary CSS
This is fun. The obvious thing that I’d love to see in real life is container queries, which I mentioned last week, but there’s a lot of good stuff in here that I’d never thought of before, but now I’m sad I can’t use. Touch target sizing and a between pseudo element have now shot to the top of my list of wants.
Let’s talk Neumorphism and AccessibilityUyen Vicky Vo
I always enjoy seeing the development of a new design trend, even if it’s something I never plan to use myself. Neumorphism has been floating around quite a lot recently, and seems to have nicely divided opinion. That means lots of discussion pieces talking about the pros and cons of the style, which means lots of stuff for me to read.
Neumorphism is a play on words based on New + Skeuomorphism. It is a style that uses blur, angle, and intensity of an object’s shadow to highlight the object. It’s a design that looks realistic, futuristic, modern, appealing and extremely breathtaking due to its soft shadow and overall appearance.
But let’s be honest, it’s not the most practical design for actual use. Try building and releasing a product that has used Neumorphism as its main style, and you’re most likely going to frustrate everyone…
In this post, Vicky Vo talks about the accessibility issues inherent in a style that tends towards low contrast. As you might expect, there are a lot.
Actually, the more I see of neumorphism, the less I like it.
Link TargetsSebastian Greger
The only arguments I’ve ever heard for opening links in a new tab/window — despite presenting evidence from usability research — came from marketing. And it’s always about the goal of an organisation to trick users into “keeping them on our site”Sebastian Greger, Link Targets
The discussion over whether links should be set to open in a new tab/window has been ongoing for years now. Personally, I like links to open where they are, allowing me to choose whether or not to middle-click and open a new tab.
So far I haven’t read much research into the usability question (although I will do so now), but I’m inclined to agree with Sebastian that the requirement to open links in new tabs usually comes from the marketing side of a business.
UtopiaJeremy Keith, Utopia
Jeremy Keith posted a quick write up of Utopia, Trys Mudford and James Gilyead’s breakpointless fluid typography and spacing project. Both Trys and James work at Clearleft, so Jeremy has an interesting perspective here.
The genesis for Utopia came about after Trys and James worked together on a few different projects. It’s all too easy to let design and development splinter off into their own caves, but on these projects, Trys and James were working (literally) side by side. This meant that they could easily articulate frustrations to one another, and more important, they could easily share their excitement.
The end result of their collaboration is some very clever code. There’s an irony here. This code could be used to discourage collaboration! After all, why would designers and developers sit down together if they can just pass these numbers back and forth?
But I don’t think that Utopia will appeal to designers and developers who work in that way. Born in the spirit of collaboration, I suspect that it will mostly benefit people who value collaboration.Jeremy Keith, Utopia
After a succinct breakdown of the project’s aims, Jeremy highlights some of the reasons you might want to use it on your own projects.
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.
And if you're feeling particularly generous, please like, retweet or share this post on Twitter. It really helps me out.