
Founder @Railway, the peaceful way to ship software. People, Product, Production.
SF via 🇨🇦
Joined June 2012
- Tweets21.4K
- Following1.3K
- Followers33.6K
- Likes36K
Jake retweeted
i think the toughest thing to understand is that it literally doesn't matter if your software is open source, closed source anymore - if it's closed source, people can and will RE: its internals, if it's a part of a broader suite, ppl will make it a plugin in their suite, if it's a model that people can blackbox fuzz and the model isnt huge and didn't have incredibly proprietary data, you are going to get copied on the tech
so every core product launch probably needs to be treated as an extreme countdown race, before the incumbent with the distribution eats you
brutal times to be playing, and extremely valuable/rare to find a corner of the stack that may be defensible and will stay defensible
Jake retweeted
Over the years I have recommended multiple friends when the started up to put their infra on @Railway. (Yes I work here now but I was a long time user and fan for many years already)
Months later I'd ask them how it is going and the cloud bill would always be one (or even two) '0's less than what I would have guessed. It is incredible
I spent the last 6 months with a civilian token budget to implementing a homage to Victor Zampella's work and the IW4 engine entirely native to the browser:
Presenting: Open Victor Zulu
and you can play it now: ovz-game-production.up.railw…
Jake retweeted

Bryan Cantrill@bcantrillSep 5
United States
United StatesConnected via WebAccount-level information, not a live location or per-post device.
The revolt of the reader
bcantrill.dtrace.org/2026/09…
Jake retweeted
Replying to @ivanburazin
Tech consistently forgets that most things are not technology problems, they are human psychology, habit, and risk tolerance problems. They take time.
This makes tech often right about the thesis, and wrong about the timeframe over which it’s realized.
Jake retweeted
You can disagree with any single take. But the pattern here matters: @tobi wants Canada to win. He puts his ideas out in the open, takes the heat, and keeps building one of the most important companies in the world from 🇨🇦
That is what ambition for your country looks like.
Carson Jerema: Tobi Lütke will not comply nationalpost.com/opinion/car…
Jake retweeted
everything that can be will be converted into
`state = memo { f(log) }`
all other state management is just too complex at the limit
Figma CEO @zoink warns creatives against "quietly surrendering" to AI — when AI tools narrow the scope of your creative process and end up controlling the direction of your creative output
"Right now, there's almost like this quiet surrender, as our CPO @yuhkiyam put it the other day."
"Where you're almost giving up your own vision to AI in some cases."
"People will have a thing in their head that they're trying to drive toward, and they start talking with AI, and AI kind of convinces them, in its own way, of — 'No, just go this direction. This is what I want to do.'"
"And suddenly, you're just feeding the AI prompts. And eventually you've lost control. And you surrender to the AI."
"You have to bring your individuality, bring your vision, and explore. Because people get really attached to the direction they're pursuing, and that's just not the best way to get to the right result."
New in beta: Infrastructure as Code on Railway
Init, plan and apply your infrastructure changes. See the diff for every change, and ship it when you're ready
Keep your infrastructure defined and versioned alongside your app code
Try it out: docs.railway.com/infrastruct…
Jake retweeted
log scaling increases. spikey RSI sigmoids. compute shortage. algo leaps. compute collapse. humanoids scale to 10B. BCI scales to 10B. log scaling moves to space. bio accelerationism. self-replicating robot space economies. the dissolution of mercury. bishop rings. wormholes.
Jake retweeted
Right now, there's a group of companies building agent-native backend systems and infrastructure.
They are all code-first, typed, and have clean composable APIs, minus the legacy surface area and database configuration sprawl. @convex fits into this club pretty well. So do a couple of other companies.
The more interesting part, however, is to single out the current incumbents who don't. In another 6-9 months, this category distinction will be even clearer.


























