Micah Alpern retweeted
i have always thought that programmers were divided between puzzle solvers and problem solvers. AI makes this division even more clear.
Micah Alpern retweeted
if you're a designer or PM and your career satisfaction is "it's complicated" rn, @dburka wants to hear about it.
his nonprofit's survey is built on ikigai (a much nicer-sounding word than 'existential crisis')
Fill it out here so we have trustworthy data!
hardproblems.com/survey/2026…
Micah Alpern retweeted
OpenAI should make a keyboard extension for iOS and destroy Apple’s existing Dictation, which somehow feels like it has gotten worse.
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.





























