Ryan Green (@ryngrn) header
Ryan Green (@ryngrn) profile picture

Human-centered systems thinker. AI-centric designer + builder.

Tennessee
Joined February 2009
Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)Photo by Ryan Green (@ryngrn)
🎉 Introducing SiliconForest: a new open operating system built on Darwin and XNU, the open-source core of macOS, running natively on an M1 MacBook Pro. Here’s the interesting part: it runs unmodified Mac apps. This first version runs Apple’s Terminal and Activity Monitor, copied straight from a macOS install, plus the stock Mac build of Firefox. Working today on a 13" M1 MacBook Pro: GPU acceleration (Vulkan 1.4), hardware video decoding, Wi-Fi, sound, keyboard and trackpad, and the Touch Bar. It’s Apple’s open-source kernel, with the parts Apple doesn’t publish reimplemented from scratch. I’ve also brought my Wayland compositor, Chonkstep, over to Darwin, and the results so far are fantastic. The idea: a free, hackable OS that can run native Mac apps. It’s early. Big apps like Logic Pro and Photoshop need a lot more (Metal, for a start), but that’s the direction. It stands on great work: PureDarwin (which we fork), the Asahi Linux GPU and hardware drivers, Omacom Mesa, and the Finch frameworks project. Source is coming soon. Right now it runs on one machine, the 13" M1 MacBook Pro. If you’d like to help bring it to other M-series Macs, get in touch. github.com/chriskearney/sili…
113
212
47
2,038
120,404
Websites blocking agents is going to look so incredibly dumb soon. Like a brick-and-mortar store that refuses to do e-commerce.
1
1
2
381
It’s extremely obvious what is happening, I don’t know why we don’t just say it: Agents have made every system on earth highly vulnerable overnight, and there are swarms of agents attacking everyone. Everyone is running agents to defend themselves, creating rapid patching of security vulnerabilities in every system on earth. Orgs are either choosing to take their networks down during this transition, or the rapid AI-driven patches are sometimes causing mistakes and errors. They should just say what is happening. This is what every IT team on earth is dealing with.
5 MAJOR DISRUPTIONS IN JUST 6 DAYS 🇺🇸 Nov 17: NSA classified network DOWN 🏦 Nov 16: JPMorgan banking failure ✈️ Nov 16: United Airlines outage 🛑 Nov 13: FAA nationwide ground stop 🌐 Nov 12–13: Microsoft 365 outage No coordinated cyberattack confirmed.
138
381
76
2,921
333,383
Ryan Green retweeted
Notes From the HubSpot Refounding, Day 2: Another big day as we plan, ship, adjust and adjust again. One thing I'm learning as we dig into this is the *brand* of HubSpot. In our early years, we punched above our weight-class when it came to brand. Back then, one of the internal aspirations we set for ourselves was this... Make HubSpot: Easy to buy. Easy to use. Easy to love. This was on a slide I used all the time (and I think I may have shared publicly a few times like a decade ago). As part of the #HubSpotRefounding, @bhalligan and I are working to get back to this. 1) Easy to buy: Simplify pricing considerably and reduce the "jaggedness" as customers need key features. Make the pricing smoother so price goes up as value/usage/consumption goes up. 2) Easy to use: Simplify the core product and double-down on both Breeze and our MCP connectors for Claude/ChatGPT. More and more people are happier using HubSpot in that way. Sometimes the interface that we so fastidiously worked on for years just needs to fade into the background. 3) Easy to love: Lean in to the human side of HubSpot. It's the thing that we were defined by in our early years. We cared deeply about truly democratizing technology and made the investment to *teach* millions and help them grow better. We're going to bring that back -- but now, instead of inbound marketing, it's AI. The tricky part about the refounding is that we want to balance the idea of bringing back some of the fundamental things that made us different that are still relevant today while resisting the temptation to just do the same things over again. For example, in the prior generation of HubSpot we got really good at designing a classic web interface that was approachable for SMBs. Now, we need to recognize that the interface is not the value -- it's the gateway to the value that HubSpot provides. And, a hybrid conversational/chat interface is a better gateway to that value. It's going to be uncomfortable for some -- but necessary. Keep the comments and feedback coming (just leave a comment). We're all learning a lot in this process of refounding in public. Confession: Let's keep this between us friends, but thinking out loud in public is actually a great way to spread the message *internally* too.
85
6
3
220
17,770
Ryan Green retweeted
Designers started shipping code to take work off engineers. On a lot of teams it's doing the opposite. The PR looks right and works when you click it. Under the hood it's junk. So whose job is it to fix that? southleft.substack.com/p/des…
25
9
1
120
13,354
Well done 👏 I enjoy reading through these reports Lenny puts out. There's not many folks giving this kind of data away these days. (Hide your eyes if you're a designer, though 🫣)
STATE OF THE TECH JOB MARKET IN 2026 Twice a year, I dig into trends in hiring and job openings. This is the fifth report I've done, and the most surprising yet: 1. PMs are winning in the AI era 2. Engineering demand has stalled 3. Design openings are at a record low 4. Every role now requires AI skills 5. Tech jobs are concentrating in the Bay Area 6. Remote roles are at a record low 7. The tech job market is growing fast, but mostly outside of software (gasp!) Full report here: lennysnewsletter.com/p/state…
2
1
1,269
Its a great product, but the market has already moved. Many local first or free options. Apple should 100% acqui-hire the team to work on Siri. Anyone with a regional dialect probably knows the pain.
Wisprflow death clock 🕰️ 🪦 How long until $2 billion goes to zero?
1
121
AI has made applying for jobs a very automated process. Sorting / screening of job applications is almost certainly being done by hiring managers using AI. I applaud those who have not slipped into nihlism!
1
32
Ryan Green retweeted
The risk with hiring a domain expert for a zero-to-one product is that new products that breakout are always outliers and break the rules. Foolish people who start from a clean slate and operate from first principles don't have that scar tissue that can cloud decisionmaking. For example, Airbnb had no hoteliers on the founding team. However, the best scenario seems to be composing the team with both types of people, as it will create the chemistry to avoid obvious mistakes while also questioning "expert" assumptions.
223
251
45
3,541
220,957
Ryan Green retweeted
Whoever made this is a genius 😂😂
453
6,519
722
49,156
5,070,665
Love this.
We're making lil' experiments almost every day to keep pushing the @wabi brand and product forward This tool, from early this Summer, to finesse a hover effect idea with custom-generated retro icons was one of my fav ones
1
3
259
I asked Claude: "What types of businesses outside of the labs will get stronger as raw intelligence explodes?" Honestly, spot on response.
181
467
60
5,569
477,101
I'm starting to sense a divide in the tech industry: - People thriving on autonomy who are reinventing how they work and what tools they use with AI: LOTS of work, but they're enjoying it and getting very efficient - People used to being mentored / trained / or simply told what to do and how. Frustrated with the lack of guidance from management on what to do with AI; also frustrated by seeing some of their peers thriving; increasingly bitter about AI and the state of the industry, as a whole Neither group seems to be aware that there's another group, or have empathy for the other group
400
413
175
5,590
481,836
Ryan Green retweeted
design slop indicators - tags - italicized words - instrument serif, negative kerning - over the top detailed UI - dividers - multiple color shades and opacities - containers with borders - diagrams. the more detailed, the worse - code breadcrumbs - section numbering
115
100
34
3,087
290,294
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month. I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
646
1,561
752
15,615
2,860,928
more design thinking > faster screens “3 to 4x faster” is the wrong thing to be proud of. If the win is that designers make screens faster, you’ve sped up the part that was never the problem. I don't think moving off Figma makes anyone a better designer. Pointing an LLM at your UI kit just gets you a screen that looks like your product, rendered quicker. The hard part of designing a product isn’t the happy path. It’s knowing your customers and your business. All the research, all the states the product can be in, how it behaves in each one. Our prototypes are code first, so they run on that context in the same code we ship. At @mercury we use the time we get back differently. It goes into exploring more directions, pressure testing them against real customer insights, and iterating on the details until they feel right. That extra time is spent on more revs and it’s how we keep our craft bar as high as it is.
Revolut's designers are moving off Figma. Storonsky spotted one team designing much faster than the others. What they did: 1. Gave an LLM Revolut's design system at the code level 2. Prompted it to build new flows on top of that system 3. Got a live interface they can click through on a laptop or phone, instead of static frames Result: 3-4x faster. Now he's pushing it to every designer at Revolut. His job, as he describes it: find what works in one team and spread it across the company. Full breakdown here: productmarketfit.tech/p/revo…
16
11
1
134
3,634
Things you can use Al for when working on UI: - ask it to try and break the stuff you built - let it create state machines to check different scenarios (success, error, different user roles, etc.) - when finished, ask it to make before/after screenshots - make it ask you lots of questions about the thing you are working on to validate the idea - let it create a few variants of a Ul piece so you can try it out - setup loops to maintain a quality bar by constantly monitoring
70
106
16
2,640
75,737
I’ve done 5 or 6 advising calls this year with designers ~10 years into their career. I told them all the same few things:
12
28
2
355
35,047
Ryan Green retweeted
designers are good founders > engineers: 1) they talk to users 2) they solve problems methodically 3) they care about how it looks 4) they care about users winning, not just tech designers who build things are the future - we should encourage more of it, not less.
13
13
1
117
4,289
Ryan Green retweeted
I got to see @sandbar in action at dinner last night. I will be buying one. So good.
12
4
2
52
11,587