All deployments on Railway is now enabled. Please feel free to shout here if it doesn't work.

Enabled for Pro users now! Working on enabling Hobby & Free/Trial next.

IMPORTANT: Please rotate any API keys/tokens you've added as environment variables to any Railway services.

Builds and deployments have been re-enabled for @Railway Enterprise customers. We’re working on enabling builds for all tiers, starting with Pro next. Apologies for the inconvenience folks! Live updates available at status.railway.com/incident/…

Beat my sleep schedule.

Customer support in 2026 is just two LLMs talking to each other with a meat proxy on each end.

Culture is the compression of a thousand decisions you no longer have to explain.

A community member in our Discord asked "what causes @Railway to go down". I ended up writing more than I planned. Sharing because the answer is less obvious than people think! (Caveat: this is the high-level version. Infra failure modes as a platform are long tail and I left plenty out, but this covers the shape of it.)

about to do it again, I'm sorry if GitHub goes down

Model-specific ASIC like Taalas is the way forward IMO. TPUs are still bottlenecked by its HBM for model weights. Taalas etches the model on the silicon so weights are directly fabricated into the silicon itself. Taalas has accomplished 17k TPS on Llama 3.1 8B at ~250W power draw which is astonishing. Imagine a future where models are cartridges you can plug-and-play like components of a Framework laptop.

The best interview question is a design prompt with no right answer, because the job has no right answers either.

It’s 100% a skill issue. I’ve been fully remote in globally distributed orgs for more than a decade, and I’ve built successful remote teams and processes spanning 15-hour timezones. A good remote team ships *more* efficiently than an in-person team. The key is autonomy, ownership, & clear written comms as defaults. Writing is also why remote orgs compound. Every decision leaves an artifact. In-person orgs evaporate their context daily. “Remote doesn’t work” almost always decodes to “I can’t tell who’s working/what they’re working on without watching them” which is less about remote and more a confession about your org chart.

Churn dashboards are a lagging indicator. Your support queue is the leading one. Guess which one gets exec attention? ;-)

"We're data-driven" usually means "we're waiting for numbers to give us permission to do the obvious thing"

It's crazy how the whole visual web is becoming legacy -- SEO optimized pages for readers who skim, & AEO is now about optimizing for readers who never even render the page.

Leadership is repeating yourself until other people can say it without you.