Pinned Tweet
Metaverse in NYT (2007): “John Maeda isn't real, nor is the island. He is the Resident, and the island is the Metaverse in the virtual world of the Second Life online game. Other works exhibited are a beige Apple II computer, and a dozen or so iPod Nanos.” nytimes.com/2007/05/04/style…
Design And Engineering Are The Same Thing youtu.be/AK8zLQeRI2M
⚪️→◻️→🏆
This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax.
- 100-500× faster than mermaid.js
- 6× smaller bundle
- No dependencies
- Easy to theme
- Responsive to device width
In pursuit of making Obsidian insanely fast and cohesively designed, I always found the Mermaid library to be too big, too slow, and too hard to theme. Pele will be the new renderer in the next version of Obsidian, but you can start using it now.
Pele [ˈpɛlɛ] is named after the goddess of volcanoes and fire. It's open source under the MIT license. Try the playground!
John Maeda retweeted
Replying to @kitasenjudesign
It's the 30th anniversary of @johnmaeda's 12 O'Clocks! This project and his Reactive Square were what made me want to enter the field. In 2016 I captured GIFs of his clocks, since the apps required an OS9 emulator to run.
⚪️→⚪️ 🏆
I added a new /state-machine skill to the collection.
It renders any component you want in all of its states on a throwaway page with mock data.
I enjoy working like this a lot. It makes it very easy to work on more complex components.
github.com/jakubkrehel/skill…
👉🔊🏆
Most UI sound libraries ship folders of audio files, so I made cuelume synthesise all 14 of its cues live in four materials
cuelume.dev/
🌑🌒🌓🌔🏆
the gradient tool is out! and man, i'm so touched by all the overwhelming support i got for it last week... if you have any suggestions for mmeshy, rip me apart in the comments! SOUND ONNNN 🗣️
mmeshy.com
👾🏢⛪️🏭🏆
What if you could explore your codebase rendered as a city right in the terminal. Watch your agents work as they create, delete, refactor and build software as an interactive visualisation. @fabricated_it and I built this last week
🇬🇧 🗣️ October 8 👇
🎓 Join us for the Dyson School of Design Engineering’s annual Commencement Lecture!
This year, we’re delighted to welcome John Maeda @johnmaeda author of "Laws of Simplicity" and "How to Speak Machine", who will deliver talk: “Design and Engineering Are the Same Job Now.”
1/2
▵ : Change is always imminent. Change is never immediate.
I'm lucky to sit next to my speedy colleague @t2govind at work, who is consistently running a few steps ahead of me in this unusual era. Whenever I already know something Govind tells me, I let out a loud 😮💨 "phew." And once in a blue moon I'm ahead of Govind… and I get a fleeting 😎 fist-pump moment that I relish for a few microseconds.
If there's one thing I've learned in life, it's that there are people who are fast at change, and then there's everybody else.
When everyone's comfortable with the existing direction, people don't want to change. When a direction does change, it has to meet three requirements to get organizationally metabolized:
1/ Be familiar to our culture — ideally invented by "one of us," so it doesn't contain any enemy booby traps we might not know about.
2/ Be known to have succeeded 99 times out of 100 — ideally 100 out of 100, so we don't end up being the 1-in-100 failure.
3/ Cost nothing and require almost no effort — not everyone has to participate, and it gets charged to a new cost center, not mine.
I've found that when these three aren't met, folks start drifting back to the way things were, because that's what appears safer. Why? Because their existing recipe for success worked so well in the past. Why break what's already working?
So change can be immediate for a person. It's never immediate for an organization. When I was younger I could be just like Govind. But in the later chapters of my career, I've come to see fast changers' impatience as a virtue, one I now balance against the puzzle of how to unlock change in everyone else.
Granted, I personally jumped into the Jevolution last week with every other "only the paranoid survive" nerd who instinctively reacts to the latest craze. But it's important to pace oneself.
Although the Cozy AI Kitchen youtube.com/playlist?list=PL… is closed, I'm carrying on its tradition of a cozy attitude as a way to handle all the ch-ch-change that's out and about. Smell the roses. Take a hike. Cook a nice slab of salmon for dinner.
This era of change can feel really tiring sometimes, and the old phrase "it's a marathon, not a sprint" is worth keeping top of mind, at least for me. I'll enjoy my salmon now. —JM
—
Reference:
- On Ch-ch-change maeda.pm/2017/12/10/3-ways-t… (2017)
🎤 🏆
convergence to the mean
when everyone looks at everyone else to decide what to make, we eventually stop making anything of our own.
we copy what works. borrow the language, the aesthetic, the features. we call it learning from the market, following best practices, staying competitive. together, everything starts to feel familiar. polished, interchangeable. nothing wrong. nothing alive.
the mean isn’t necessarily bad. it’s where everything lands when we remove the reasons for it to be different.
numbers are easier to compare than feelings, so we make things that produce numbers. we study what gets attention, then shape ourselves around it. eventually the feedback stops informing the work and starts authoring it. we’re no longer asking what we want to say. we’re asking what will be rewarded for saying.
ai makes this loop frictionless. it can draw from more references than we could see in a lifetime. but access to every perspective isn’t the same as having one. it hasn’t lived a particular life that makes one detail unbearable and another beautiful. when we ask it to choose for us without bringing any intention of our own, we get something plausible, easy to approve.
then we ship it, measure it, copy it, and feed it back into the next round. a tidal wave of mid.
this changes not just the work, but the people making it.
we describe ourselves in categories platforms can distribute and markets understand. designer. founder. creator. pick a niche. build a brand. be consistent. the parts that don’t fit become inconvenient, even when those contradictions might produce our most interesting work. we become easier to classify and harder to tell apart.
i think we need to approach making things more like artists.
an artist develops a perspective through the work. making, noticing, choosing, failing, returning. learning what matters even when nobody else cares. craft gives that perspective a form precise enough for someone else to experience.
the life outside the work matters too. the places you’ve lived, the people you’ve loved, the things you’re embarrassed to care about. these aren’t distractions from having something to say. they’re how you come to have something to say.
we understand this with music, paintings, photographs, movies. we expect a person to be present in the choices. we want to experience something we wouldn’t have encountered without them.
software can do this too.
a piece of software expresses beliefs about how life should feel. what deserves your attention. what you should be free to change. whether a task should feel like paperwork or play. even a small interaction can carry someone’s care, humor, or curiosity.
but we rarely talk about software as a medium. we talk about it as an industry. markets to capture, workflows to optimize, competitors to catch up with. we add a feature because someone else has it, without asking whether it belongs. products accumulate the same parts and lose what made them worth choosing.
underneath the branding, it’s all the same thing.
artists learn from others too. the question is whether you’re absorbing those influences into a point of view, or using them to avoid developing one.
what are you trying to let someone feel, understand, or do? why this particular shape? what have you noticed that the existing tools don’t seem to notice?
those questions don’t have answers you can borrow from a competitor’s roadmap.
if we can make almost anything, deciding what deserves to exist becomes more important, not less. speed gives us more chances to exercise judgment. it doesn’t remove the responsibility.
i don’t want a world where every person becomes a more efficient distributor of the same ideas. i want people to use these tools to go further into what they actually care about. to make things specific enough that we can feel someone behind them.
what is the point of everyone being able to make something, if we all end up making the same thing?
📁🌳🏆
Chatted w/ the creator of d3-dag about a topological rank operator to enable pre-sorting nodes, and the feature just landed. Makes it possible for me to create DAG minimaps for Rill Developer!
Here's a sketch of a query DAG navigator in a @sveltejs repl
svelte.dev/repl/83b44d5d50be…
📝✍️🏆
For years, maybe a decade, I've wanted to build a writing tool that just did a few things I couldn't find anywhere else.
A system that mimicked how I think when I write. A system that provided clear affordances, features, and places to do the things I wanted to do. A way to play with my writing as I'm writing it. A way to settle into just the right way to say something.
It never made sense to make it a 37signals product because it's not commercially viable, nor would it be worth pulling people off their other work to hack on this. Plus, it would have taken months the old way.
So this weekend I just made it myself, with Claude's help.
It's called Write_On and the short video walks you through it.
Essentially it's "alternative control" at the word, sentence, and paragraph level, plus a way to dim stuff back, and stash stuff near by. Not version control, but alternative control. You'll see what I mean when you watch the video below.
So here it is. Write_On.
🖼️ 📏 🏆
How well can models design icons? @andpoul and I benchmarked frontier and open weight models
The results: they’re steadily improving execution, their choices often overly literal





















