Alan Jacobs
revisiting architectural blogging
Makers and Making
An Article by Alan JacobsThe [Silmarils] are good; their making was at least potentially innocent; but afterward arose a lust for owning and controlling that led to great tragedy… The aspect of humanity which the elves represent most fully – both for good and ill – is the creative one.”
And this is why “making” in and of itself is not the answer to our decadent moment. “Love of things, especially artificial things, could be seen as the besetting sin of modern civilisation, and in a way a new one, not quite Avarice and not quite Pride, but somehow attached to both” – and this is the Fëanor Temptation. It is in light of this temptation that I advocate repair, which is a mode of caring for what we have not made, but rather what we have inherited. We will not be saved by the making of artifacts — or from the repair of them, either; but the imperative of repair has these salutary effects: it reminds us of our debt to those who came before us and of the fragility of human constructs.
Against Canvas
An Article by Alan JacobsEven with all the features and plugins, Canvas presumes certain ways of organizing classes that might not be universal, just typical. And if (like me) you’re an atypical user, you have to choose between constantly fighting with the system or gradually doing more and more things the way Canvas wants you to do them. This, by the way, is why it’s never true to say that technologies are neutral and what matters is how you use them: every technology without exception has affordances, certain actions that it makes easy, and other actions that it makes difficult or impossible. A technology whose affordances run contrary to your convictions can rob you of your independence — and any technology deployed on the scale of Canvas will inevitably do that. It will turn every teacher into an obedient Canvas-user. I don’t want to be an obedient Canvas-user.
But we're not there
A Fragment by Alan JacobsGet your fucking hands up
Get on out of your seats
All eyes on me, all eyes on me...But we’re not there. There’s a cheering-audience soundtrack, but it’s fake, Burnham knows it’s fake, he’s the one who put it there. He doesn’t know whether we’re watching, whether our hands are up, whether all eyes are on him.
A Q&A with Figma's VP of Product
Since we launched FigJam back in April, teams having been using it to grow all kinds of ideas into great designs. We recently caught up with Figma's VP of Product, Yuhki Yamashita, to hear what it was like to build FigJam and how things have changed since then. Here, he reflects on the evolving role of design and product management, what it means to welcome “non-designers” into the process, and the future of FigJam.
Stretching the product
When we’re thinking about where to take our product next, we actually take a lot of inspiration from our customers and the Figma Community, to see how they’re stretching our product in interesting or unexpected ways. We saw this happening in the early days of the pandemic. Our users were starting to use Figma for everything from brainstorming ideas to running team warm-up activities, to even putting on social events for people to get to know each other. We saw a lot of use cases that got us thinking.
Engineering, design, and product management
The boundary between engineering, design, and product management is blurring. Some of us used to have a mental model in which roles and responsibilities dictated how things work—that designers do one thing and engineers do another, for example. Increasingly, more people are crossing team lines to problem solve together...Now, it’s not about who “owns” what—it’s more of a collective endeavor. And the roles have become more interlocked, and I think that’s fundamentally a good thing.
Embracing the mess
Design is non-linear. At Figma, we often talk about “embracing the mess,” and that really means leaning into the chaos and complexity that makes the design process what it is. Even once you have the seedling of an idea, you need to explore and iterate, then pull back and evaluate to see what’s working and what’s not. Sometimes you’ll scrap an idea after a brainstorm session, and other times you’ll get pretty far with a concept, but still need different perspectives and input to move forward.