Butterfly Brands revisited
I've revisited Butterfly Brands, one of my earliest pieces, using AI. The original turned familiar brand logos into butterfly wings. This time, I've reimagined them as lifelike pinned specimens.
I've revisited Butterfly Brands, one of my earliest pieces, using AI. The original turned familiar brand logos into butterfly wings. This time, I've reimagined them as lifelike pinned specimens.
We added a links field to our APIAPI (Application Programming Interface). A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information. response objects this week.
Small change, and I'd put it off for a while because it felt like ceremony.
It isn't.
A status field is a contract. It is also the place where most APIsAPI (Application Programming Interface). A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information. quietly leak ambiguity, a single word doing the work of three, consumed by people who weren't in the room when you named it. Get it right and an integrator can build correct handling from the payload alone. Get it wrong and they reverse-engineer your intentions from support tickets.
In a recent piece, I made the case that we should stop trying to build "perfect" AI. That imperfection is not a failure mode — it's intrinsic to how these systems work. Here, I want to go one step further: not just to excuse AI's flaws, but to explore how we can use them. How we can design with imperfection in mind.
Errors and warnings are a minefield for developers, and very inconsistently implemented across APIsAPI (Application Programming Interface). A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information.. I've been thinking about what a consistent, developer-friendly approach to surfacing issues looks like, one that helps both developers and their end users.
This is focused on APIAPI (Application Programming Interface). A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information. responses and logs rather than native SDKsSDK (Software Development Kit). A collection of software development tools, libraries, documentation, code samples, and guides that help developers create applications for a specific platform or framework..
I care about how products feel to use, but “delight” has always felt slightly too decorative a word for it. The thing I’m after is more practical: design that makes a product work better.
I call it functional elegance.
A small plea: stop abbreviating field and method names in your APIsAPI (Application Programming Interface). A set of rules and protocols that allows different software applications to communicate with each other. APIs define the methods and data formats that applications can use to request and exchange information., SDKsSDK (Software Development Kit). A collection of software development tools, libraries, documentation, code samples, and guides that help developers create applications for a specific platform or framework., and config.
A collection of hand-typed letterforms and numbers, each with their own character and texture. These were created using various materials and techniques, from traditional pen and paper to more experimental surfaces.
Doodles at the RA.