Koya Bound — Eight Days on Japan’s Kumano Kodo
Speaking of Koya Bound, here’s the web-based counterpart to the physical book.
Link archive: August 12th, 2017
To Make a Book, Walk on a Book — Craig Mod
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.
Shadow DOM: fast and encapsulated styles – Monica Dinculescu
Monica explains how Shadow DOM could be the perfect answer for scoping CSS:
We didn’t have style encapsulation, so we started naming things “the right way” with BEM, so that we didn’t accidentally stomp over each other’s styles. We wanted to be able to author CSS from inside a JavaScript component, so we started using CSS-in-JS. We needed all these tools, because “the platform” (read: the browsers that be) wasn’t there, and building these tools showed that there was a need to move forward. For style encapsulation, Shadow DOM is the platform moving forward.
Although, in a way, Shadow DOM is also another flavour of CSS-in-JS:
Before you complain that using a Shadow DOM and Web Components means that it absolutely requires JavaScript: this is true.
I made a style guide for my personal web site and you should too.—zachleat.com
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.
I’m a woman in computer science. Let me ladysplain the Google memo to you. - Vox
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.
If you want to debate the Googler’s Manifesto and you’re also a good person
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.