Sabitlenmiş Tweet
Adit Gupta
9.3K posts
Adit Gupta
@aditgupta
Building TypMo — https://t.co/zDb8QA2pOG | Prev- Director of Design @servicenow | Philosophy Nerd
Katılım Nisan 2009
91 Takip Edilen1.5K Takipçiler
Look at this screen.
Every role, every agent, and every state change is visible in a single view.
You can see exactly how an incident moves from queue to closure. Who triages. Who resolves. Where the AI agent pre-populates, checks SLA rules, surfaces similar past incidents, and indexes the resolution for next time.
This is what TypMo generates from your spec. A living swimlane that shows how information passes through people and agents, how they act on it, and where the system enforces rules.
Build systems, not screens.
English
In a world where execution is table stakes, Before the Prompt is my attempt to appreciate deep thinking and what it takes to build robust, scalable products with AI rather than screens.
The hard part is knowing what to build before you build it. The thinking that happens before the first prompt. The structure that determines whether what you ship actually holds.
Before the Prompt is not a newsletter about AI tools. It is a primer on systems thinking for people building complex products with AI. How to reason about what you are building before you ask an agent to build it.
No tips and tricks. No listicles. Just rigorous thinking, written to be worth your time.
If that resonates, subscribe to the newsletter.
beforetheprompt.substack.com
English
Share your product (free marketing).
Support others in the comments. 🔗
English
Adit Gupta retweetledi
I’ll say the thing no one is saying: design culture is broken in lots of companies.
Often design teams & designers are the most resistant to change org in the EPD triad, with highly vocal AI opponents, and little skill or interest in the art of campaigning for influence or resources. Won’t hold a number like a PM, not yelled at about timelines like engineering. While I have brought design topics to the board convo, not a single board has pressed me our design talent, strategy, or velocity. Most teams treat design like a tax they don’t want to pay, and those that *do* take a deep interest and want to invest in design get back big “get out of my figma” energy. And if you’re too precious about craft to dirty your hands with the dark art of corporate politics, good luck getting more headcount. If a PM or engineer can get 85% there with tailwind and a dream, you better come to the table with more than “I represent the user.”
Great designers are worth more than almost anyone on the team, and I’ve worked with lots of gems, but this is 0% surprising to me.
Lenny Rachitsky@lennysan
I don’t know exactly what’s going on here, but it does feel AI-related. Unlike PM and eng, which started growing in 2024 (two years post-ChatGPT), design didn’t. If I had to venture a theory, I’d say that because AI is allowing engineers to move so quickly, there’s less opportunity—and less desire—to involve the traditional design process. That said, you’d think design would become a differentiator as more products compete for attention. Something to think about for your company! We’ll keep watching this trend and AI’s impact on org design more generally. One interesting observation we made when we went a level deeper: the ratio of demand for PMs vs. designers has flipped. In mid-2023, we went from more open designer roles to more open PM roles. And ever since, PM demand has been pulling away (currently 1.27x). This will be another trend to monitor, in terms of how AI is reshaping org design.
English
You are monitoring the wrong thing
open.substack.com/pub/beforethep…
English
@rishikagupta__ TypMo - Two purpose-built languages (DSLs) compile your product thinking into structured specs that coding agents consume directly via MCP.
typmo.com
English
Are there any good AI startups that don’t look like simple wrappers?
English
Here's a free 2-minute quiz that tells you the real complexity hiding in your application.
Most PMs think their app has 20-30 decisions to make. The real number is usually 150-250.
Roles that each see different data. Entities that move through states with rules at every transition. Business logic that cascades when one thing changes. Agent behaviors that need guardrails and fallbacks.
If these aren't in your spec, they'll show up as rework, bugs, and production incidents.
typmo.com/complexity-res…
English
MercadoLibre is training 20,000 developers on Spec Driven Development. They identified the frontier: spec-as-source, where you edit the spec and code regenerates to match. TypMo is already there. PMs write the spec. Coding agents read it via MCP. The spec is live, queryable, and verified against the build.
Julián@juliandeangeIis
English
This. Honestly, folks declaring these death sentences have never really worked on complex, workflow-driven applications. Their immaturity stems from their inexperience.
Tuomas Artman@artman
Getting tired of this
English
A collab you never saw coming: TypMo 🤝 @paper
Your TypMo wireframes can now flow directly into Paper for stunning high-fidelity designs. No back-and-forth, no endless revision cycles. One click and you're there. From structured thinking to beautiful designs, just like that.
English
Setting up 10s of plugins, maintaining tons of md files and ripping your hairs apart with Skills. Why do all of this when you have a plug and play solution?
English