Product Engineer @SquadsProtocol | ex- @framer • Building @fusewallet and @altitude • Opinions are my own
Joined January 2011
- Tweets 3,120
- Following 2,976
- Followers 2,151
- Likes 9,775
171 Photos and videos
May 18
Come work with me
May 18
We’re hiring product engineers at @altitude.
We believe the next generation of companies will be built differently: smaller teams, faster cycles, deeper customer understanding and engineers who shape the product and the outcome.
At Altitude, every engineer is a product engineer.
You’ll work with our internal agentic framework to build the future of how businesses manage their money. We’re going to shift the center of gravity from traditional financial rails to newer, better ones.
We’re looking for people who want ownership, ambition and the chance to build something that becomes foundational infrastructure for modern companies.
If you’re not afraid of the climb - DM me with proof of work.
8
2
37
4,905
Apr 29
If your financial product depends on a bank, you're building on someone else's balance sheet.
We built Altitude on stablecoins with custody, permissions, settlement rethought from first principles.
Businesses no longer need a bank account.
We've raised $18M on this bet.
Go altitude.xyz
3
2
27
3,376
vo—va 🇺🇦 retweeted
Apr 23
Introducing Smallbits – 200 free pixelated icons on a 8×8 grid where every single pixel counts.
Work in progress. Tell me what's missing.
smallbits.design
14
42
562
31,915
Apr 7
The framing most people use for AI in engineering is: how do we make each engineer faster.
It's the wrong question. Faster at what, exactly? Generating output?
Output isn't the constraint, the real constraint is judgment and taste.
4
24
2,460
Apr 4
Work of beauty 😍
Apr 3
I designed the new icon set for @cursor_ai. ✨
420 icons. 2 sizes. 2 styles. One single family.
Simple, beautiful and practical – with just enough character to feel satisfying.
1
4
522
vo—va 🇺🇦 retweeted
Mar 24
payables shouldn’t be a manual finance workflow. it should be an agentic pipeline.
data comes in → processed → pushed in real time. no humans in the loop for routine transactions.
you don’t run deployments manually. why are you still running invoices that way?
2
6
23
2,136
Altitude Bill Pay is live.
Pay bills directly from your stablecoin balance.
→ Email-forwarded bills for auto-ingestion
→ OCR AI populates every detail
→ Pay in USDC or via fiat rails your vendor prefers
→ Payouts from one account make reconciliation simple
No more patchwork. One account. All your bills.
Closing your books has never been easier.
20
31
164
118,412
Feb 19
Just like that, the team shipped the first feature that uses AI under the hood, without much fluff. More is on the way.
2
5
290
vo—va 🇺🇦 retweeted
Feb 12
Launching @altitude Bill Pay next week.
You can't escape your bills. But you can stop processing them manually.
Bills in, stablecoins out.
21
15
135
29,148
vo—va 🇺🇦 retweeted
Jan 29
We've just given our React scroll animations guide an overhaul. Check it out for quick recipes:
- Scroll direction detection
- Hide header on scroll
- Image blur & zoom
- "Blinds" clip-path reveal
And much more.
3
7
125
7,722
Jan 5
The @expo App Awards Prize has arrived 🛬 An absolute beauty of a keyboard, I'm a bit jealous but happy for @nickpylll ❤️
2
19
1,806
27 Dec 2025
If your software isn't chasing this metric, it might hopelessly fall behind the competition in 2026.
There recipe starts with aggressive local caching and optimistic updates
What do I mean when I say everything in Obsidian should feel instantaneous?
No more than 0.1 seconds.
The target was established in 1968 by Robert Miller and well described in 1993 by Jakob Nielsen here:
ALT 0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result. 1.0 second is about the limit for the user's flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data. 10 seconds is about the limit for keeping the user's attention focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done. Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect.
1
13
5,432
24 Dec 2025
Me prediction for 2026:
@jetbrains buys @augmentcode and properly re-enters the agent coding race with big chances of winning. Or it doesn't do it and loses the loyal user base to Cursor
457
24 Dec 2025
Wasn't a terrible year, I guess
2
18
2,246
12 Dec 2025
The best microbiome booster I can imagine
11 Dec 2025
Born by C-section? The baby’s microbiome ends up resembling mom’s skin not reproductive tract. And your microbiome can shift over time, but it’s pretty much set in the first three years of life. And then you can modify around that. Oh, and owning a pet improves your kids’ microbiome for life.
1
8
1,199
10 Dec 2025
This is already awesome, what could do it even better if we could make it deterministic, that would basically solve the UX of app install referrals. Last time I researched the space the best potential solution I could find was App Clips on iOS because they preserve the state until the full app is installed
9 Dec 2025
Let’s be honest: most deferred deep linking tools are built for marketers, packed with features you’ll never use. 😬
Detour is different – it gives React Native devs exactly what they need for deep links, all in a super simple dashboard.
Try it now – it’s free and open-source: docs.swmansion.com/detour/
2
9
1,446