Micah Alpern retweeted
launched a little mac app that turns your wallpaper into a wall with sunlight moving across it, synced to the real sun outside: sunstill.app
Micah Alpern retweeted
6 weeks left in 2026... if you're a designer thinking it'd be great to start the new year in a new company/role, my DMs are open. Nearly 70 design positions in our portfolio alone...
We're in the process of renovating our home right now and Opus 5.5 did pretty much all of it
Including making a cinematic trailer and magazine feature to get my fiancée on board
Micah Alpern retweeted
Don't sleep on Claude Slides. This is how I make slide decks now -- no more googling "iphone frame svg" like the old days
Try it: claude.ai/artifacts
Micah Alpern retweeted
One of my favorite papers ever
Drag-and-drop makes the digital graspable, but building it well is fiddly enough that many don’t bother. Declarative Dragging (with Josh Horowitz & Jeff Heer, #uist2026 best paper award), lets you make an element draggable just by listing the states dragging it can reach.
I hate using multiple smart device apps to control the smart devices in my room, so I setup a raspberry pi server, reverse engineered a couple of protocols, added some UX magic, designed an AR enabled app that lets me go “lumos” and turn the lights on
So far I have integrated: Smart bulbs, Smart strips, AC, Bluetooth speaker, air purifier, and a couple of lamps
Micah Alpern retweeted
I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.
There’s 100% a kind of mania you can get into with coding agents, where it feels like you’re getting a lot done and working all the time but nothing is really happening.
I think it's often a form of avoidance of something else in life.
Micah Alpern retweeted
I’m hiring! Come shape the future of the Figma editor: how direct manipulation, AI, and code fit together, built with the craft that makes Figma feel like Figma
→ job-boards.greenhouse.io/fig…
Micah Alpern retweeted
Many of you don't understand how serious this is, so let me break it down.
In computer science there is a famous kind of puzzle called 3-SAT. You are given a long list of yes-or-no switches and a set of rules about how they must be arranged, and you have to find a combination that satisfies every rule. The obvious way to solve it is to try every combination, but each new switch doubles the number of possibilities, so a puzzle with a few hundred switches would take longer than the age of the universe to brute force.
For decades, the smartest people in the field found clever tricks that made this a little faster, but every trick still hit the same wall: the time required kept exploding as the puzzle grew.
About 25 years ago, two computer scientists, Russell Impagliazzo and Ramamohan Paturi, working with Francis Zane, turned that wall into a formal idea.
They proposed the Exponential Time Hypothesis, which says this explosion is not a failure of human cleverness but a law of nature. No algorithm, however brilliant, will ever solve 3-SAT without the time blowing up exponentially. Nobody could prove it, but almost everyone believed it, and it became one of the foundations of modern computer science.
Researchers used it as a measuring stick. If you could show that solving some other problem quickly would also crack 3-SAT quickly, you had shown that problem was hopelessly hard too. Hundreds of papers, across scheduling, graphs, logic and much more, rest on this one assumption.
Now an internal AI model at OpenAI claims to have broken it. It says it found an algorithm that solves these puzzles meaningfully faster than the hypothesis allows, and it has checked the proof in a computer verification system called Lean.
And here is the remarkable part: the very people who proposed the hypothesis, Impagliazzo and Paturi, along with MIT's Ryan Williams, are now leading the public review of whether a machine has disproved their own idea.
So what happens next? If the disproof holds, a large part of theoretical computer science has to be revisited.
Every result that said "this problem cannot be solved faster, assuming ETH" loses its foundation, and researchers will have to work out which of those walls were real and which were simply where we stopped looking. It does not mean everything becomes easy. The new algorithm is still slow in absolute terms and this is not the famous P versus NP problem being solved.
But it means our map of what is possible was wrong in a place we were very confident about, and it was an AI that redrew it. If the disproof fails, the hypothesis survives and the field breathes out, but we will still have watched an AI produce serious, checkable work on one of the deepest questions in the discipline, closely enough that the founders of the idea had to take it seriously. Either way, something has shifted.





























