119 slides from Sarah on a wide range of SVG magic (with code).
The ability of the physical world — a floor, a wall — to act as a screen of near infinite resolution becomes more powerful the more time we spend heads-down in our handheld computers, screens the size of palms. In fact, it’s almost impossible to see the visual patterns — the inherent adjacencies — of a physical book unless you deconstruct it and splay it out on the floor.
Craig gives us a walkthrough—literally—of the process behind the beautiful Koya Bound book.
Deciding to make any book is an act of creative faith (and ego and hubris, but these aren’t all exclusionary). But before Dan and I sold any copies of Koya Bound, we walked atop the pages that would become the book, not really knowing if there existed an audience for the book.
Monica explains how Shadow DOM could be the perfect answer for scoping CSS:
Although, in a way, Shadow DOM is also another flavour of CSS-in-JS:
Here’s Zach’s style guide. But the real reason I’m linking to this is his lovely description of having a personal website that grows over time:
As my own little corner of the web unceremoniously turned ten years old this year, it’s really starting to feel more like a garden than a piece of software. I certainly enjoy tending to it. I can plant what I like and with proper care it can grow into something useful.
Cynthia Lee didn’t write the clickbaity headline, but she did write the superb article that follows it, methodically taking the manifestbro apart:
Its quasi-professional tone is a big part of what makes it so beguiling (to some) and also so dangerous. Many defenders seem genuinely baffled that a document that works so hard to appear dispassionate and reasonable could provoke such an emotional response.
This is what I was trying to get at with my post, but here it is explained far more clearly, calmly, and rationally.
In the end, focusing the conversation on the minutiae of the scientific claims in the manifesto is a red herring. Regardless of whether biological differences exist, there is no shortage of glaring evidence, in individual stories and in scientific studies, that women in tech experience bias and a general lack of a welcoming environment, as do underrepresented minorities. Until these problems are resolved, our focus should be on remedying that injustice.
We men face shame and firing if we say the wrong thing. Women face the same plus rape threats, death threats, and all kinds of sustained harassment. So women can’t speak up safely and therefore they would have to watch their male colleagues discuss how a woman’s brain determines her interests. How impossibly maddening that would be.
I’m a Google Manufacturing Robot and I Believe Humans Are Biologically Unfit to Have Jobs in Tech - McSweeney’s Internet Tendency
Normally a McSweeney’s piece elicits a wry chuckle, but this one had me in stitches.
Humans are also far more likely to “literally cannot right now.” I have never met an automaton that literally could not, though I have met some that theoretically would not and hypothetically might want to stop.
Silicon Valley’s weapon of choice against women: shoddy science | Angela Saini | Opinion | The Guardian
Those who want to use science to support their views – especially if they seek to undermine equality efforts in the workplace – must make an effort to fully inform themselves about the science of human nature. They may be disappointed to learn that it’s not as simple as they think.
For more, read Angela Saini’s book Inferior: How Science Got Women Wrong and the New Research That’s Rewriting the Story.
An excellent rebuttal of that vile manifestbro, and an informative history lesson to boot.
You can’t cherry-pick a couple of scientific studies you like and use them to justify your arguments against diversity programs, while carefully ignoring the mountains of other scientific studies that show both how and why diversity programs are good, beneficial to all, and worth investing in.
I wish I could be this calm in refuting pseudoscientific bollocks, but I get so worked up by it that I’d probably undermine my own message. I’m glad that Faruk took the time to write this down.
Some of these really tickle my fancy bone.
That’s the icing on the iceberg
You let the horse out of the cart
What planet are you living under?
That opens a whole other kettle of fish
The cat’s out of the barn
Patience comes to those who wait
That’s right up my cup of tea
Paul goes into detail describing how he built a progressive web app that’s actually progressive (in the sense of “enhancement”). Most of the stuff about sharing code between server and client goes over my head, but I understood enough to get these points:
- the “app shell” model is not the only—or even the best—way of building a progressive web app, and
- always, always, always render from the server first.
A series of questions to ask on any design project:
- What are my lenses?
- Am I just confirming my assumptions, or am I challenging them?
- What details here are unfair? Unverified? Unused?
- Am I holding onto something that I need to let go of?
- What’s here that I designed for me? What’s here that I designed for other people?
- What would the world look like if my assumptions were wrong?
- Who might disagree with what I’m designing?
- Who might be impacted by what I’m designing?
- What do I believe?
- Who’s someone I’m nervous to talk to about this?
- Is my audience open to change?
- What am I challenging as I create this?
- How can I reframe a mistake in a way that helps me learn?
- How does my approach to this problem today compare to how I might have approached this one year ago?
- If I could learn one thing to help me on this project, what would that one thing be?
- Do I need to slow down?
Jon’s been drawing a lunch note for his daughter every day since she was four years old. They are somewhat puntastic.
Oh, how I wish I could’ve been at Web Directions Code in Melbourne to see this amazing presentation by Charlotte. I can’t quite get over how many amazing knowledge bombs she managed to drop in just 20 minutes!
Here’s the video of the closing keynote I gave at the Frontend United conference in Athens.
There’s fifteen minutes of Q&A at the end where I waffle on in response to some thought-provoking ideas from the audience.
I’ve never been so excited by a single diff in a JSON file.
Service workers are coming to Safari.