A thing I miss IMMEDIATELY when i don't have access to Inspect, is the ability to build on the move. Inspect is where ever work happens
Its been such a pleasure to build Inspect, first for @tryramp and now for everyone. It's fundamentally changed how I work, the time from idea to reality is so small now its crazy. I've never been more empowered to solve problems in my years of building software
We built Inspect to help our teammates spend less time getting stuck and more time bringing their ideas to life.
Watching what they’ve built with it has been my favorite part. Today, we get to share it with you.
Can’t wait to see what you build ❤️
Sign up for early access: inspect.com/
jason quense retweeted
Tomorrow!! 🚀
Ramp is obsessed about saving time and money; we are going to close that loop tomorrow for builders!
AI Spend -> Token Spend Management -> Router -> ? (Tomorrow)
Stay tuned!
How often do you get to build fun automation that's going to more than 10x your teams productivity? Go dev, this is the moment it's worth it
Devs love to dev so everyone and their mom is building their own version of Ramp’s Inspect.
It’s a *ridiculous* amount of work though.
You have to build a huge amount of features to just have a simple functional agent orchestration pipeline (that’s actually good with browser testing, cloud sandboxes that actual work, surface area across Linear and Slack, PR review, Security Review, etc, etc, etc)
I know because I built several versions of this.
Got sick of it and just decided to pay for Devin.
Never been happier or freer to just ship a ton of features and bug fixes.
You’re absolutely wasting your time if you’re not buying your agent orchestration off the shelf now.
Just pick a platform and double down - stop switching - all the frontier models are equally capable now.
Focus, double down and build.
Don’t build the tool - use the tool.
Stop playing with this stuff and just get back to work.
One of my favorite parts of building @tryramp is that we aren't afraid to build things ourselves if we think it'll be better. Inspect is better!
Check out how we're enabling all of ramp to help build with us.
The craft of engineering is rapidly changing. At @tryramp, we built our own background coding agent to accelerate faster.
We call it Inspect. It wrote 30% of merged frontend + backend PRs in the past week.
It’s powered by @opencode, @modal and @CloudflareDev. It runs fully in the cloud, and starts in seconds, letting every builder work at the speed of thought, no setup required.
Today, we’re open sourcing the full blueprint so anybody can build their own Inspect. Just give our spec to your current coding agent, and let it build your new favourite.
What happened to @codesandbox it's gone from a super convenient in-browser editor and scratchpad to a bloated mess that almost never works. I have completely stopped recommending or using it.
jason quense retweeted
I'm hiring designers for @tryramp.
Who should I talk to?
If I hire them, your bonus would be enough to buy 50 @figma Creator Micros.
No DMs, no Freelancers, must be US-based → app.liftoff.xyz/kQlk07
hey @sebmarkbage hard to get find an answer for this, Will React ever start to mount a component, run a render, then bail without running effects? Suspense is involved...
For no reason: found is a production ready SPA router that handles data fetching out of the box and with a TON of optional knobs to match your use cases 4catalyzer.github.io/found/
I resent that NextJs and @reactjs for forcing libraries to go add "use client" top the top of every file or deal will with a constant influx of GH issues from people telling me how lazy I am.
I shouldn't need to opt out of new features in a minor react version for Next
jason quense retweeted
hiring frontend eng all levels @ ramp.com dm me <3
jason quense retweeted
So, what's next? github.com/zloirock/core-js/…
A lot of opinions from folks who haven't built a web app for actual users in years. That's fine it's a valid perspective but would be great if some of the thought leaders were building the things they are trying to enable
Does anyone know why frameworks like @nextjs, et all don't use HTTP2 push for priming client data fetches, instead of fetching the data and encoding it in/next to the HTML? Does it not work like that?
I keep trying to be open, but every example of using Suspense for data fetching I've seen seems worse than the version without it, for anything but trivial examples
where "worse" means, less flexible, worse UX, or more bespoke apis' and patterns to do the same thing














