
grim retweeted
As a student of design tools, this feels historic
In Ramp's spend data, Paper passed Sketch in adoption and is the "most switched to" design tool
It's humbling to see Paper alongside Sketch and Figma. I have so much respect for what they've done for our industry.
I hope that Paper can do for the next generation of designers what Photoshop, Sketch, and Figma did for mine.
grim retweeted
Did some digging
dusk bot is a re-licensed fork of MausBot (@mausbot_ )
But he just copied the code instead of forking
And then made it paid to use for commercial use
Lmao
we’re hiring android and ios developers for @heliumbrowser (2 people in total)
email me at [email protected] if you’re exceptional at making native mobile apps and are interested in creating the best mobile browser. include links to your previous work, where you’re based, and your twitter username. we will offer good compensation, benefits, and a comfortable work environment.
if you work for a competitor and would like to work in a better environment, please mention that in the email
if you know someone else who’s a good fit, please refer them to me
grim retweeted
“The 996 work culture is a schedule requiring employees to work from 9:00 am to 9:00 pm, six days a week, totaling 72 hours per week”
This is satire right???
grim retweeted
Day 8 / 46
Released our mobile app!
Get the full Hoplite experience on the go: hoplite.sh/mobile
grim retweeted
Paper team doesn't stop shipping. Wouldn't mind if it took over my whole design stack. 👀😁
grim retweeted
Tomorrow I'm teaching you how to rank on google for FREE, on my newsletter.
If you haven't subscribed yet, you should!
It's at lessons.sh 👀
grim retweeted
Good morning!
Today @paper launches Remote MCP
This may change the industry forever.
Use Paper anywhere you work:
• Cloud agents: Grok Bot, Muse, Devin, etc
• CI: update Paper on every commit
• Design from your phone
Any agent, any time, any place
Start in the thread 🧵
grim retweeted
I’m looking to join a team as a product designer and move @spottedinprod to nights and weekends.
I’ve been full time on SIP for the last 18 months and have driven the development of a web and iOS app that I'm quite proud of alongside some awesome friends. A few things are prompting this:
1. I’m still figuring out what the right business model is for the SIP community
2. It’s easier than ever to handle company admin
3. I like working with great people and want to have a crew to jam with every day
SIP is not going anywhere! My hope is that this allows me to nurture the platform more patiently over years to come.
The most important thing to me is working with people who care. My DMs are open :)
Athas is now in gpui. Completely Rust.
Smaller, faster, better. Shipping this week as a new version.
finally got a mac??
here's everything you need to install
- homebrew
- raycast
- ghostty
- claude
- t3 code
- opencode
- grokbot
- cursor / zed / athas
- wonder / paper
- aside / dia / ego lite / helium
- notion / obsidian
- recordly / shotbase
- gatherOS / pond
- rex multiplexer
- vorssaint
- rectangle
- droppy
- tilde
- mac mouse fix
- stremio
grim retweeted
everyone ask me how do I make these launch videos so I made a skill for you all
/make-motion is live on design.how
/make-font skill is live on design.how
upload couple references and it is gonna make you sexy font book
that post went mega viral, so thank yall for motivation!
grim retweeted
Got to experience the magic of @uisdk.
Two prompts of fx + Gemini Argon. Pure Web Components. No framework.
The agent reused 14 UI SDK behaviors out of the box 🤯: window resizing, drag, menubar hover-switching, typeahead, roving toolbar focus, 10-band EQ sliders, scoped hotkeys, ARIA, and WebMCP agent control.
winamp-ui-sdk.vercel.app/ (source linked)
Music by @suno.
grim retweeted
Another example of the destruction caused by wind turbines. Unnecessary waste--horrible! http://t.co/eod0dxXBTg
grim retweeted
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage.
I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care.
But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently.
For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios.
But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.



































