@ns alumn @superteamCAN member Founder https://xitter.cf/t.co/UtPNqifaT7 | https://xitter.cf/t.co/ap3lnQgXkm | https://xitter.cf/t.co/gq3LHhF8X6
Internet
Joined December 2011
- Tweets5.5K
- Following3.4K
- Followers2.2K
- Likes15.4K
Simon retweeted
the opportunity cost of not working on maximally fun and exciting things is too huge
having fun is like a 10x multiplier on your creativity, intelligence, charisma and just overall lifeforce
so everytime you are not engaging in maximal fun you are missing out on that upside and 0.1x’ing your life
discipline and routine only gets you so far, it only ever helps you sustain your baseline or maybe a slight boost so 1.0-1.2x your lifeforce
so there’s no time to waste, go and do the fun thing and 10x your lifeforce
Simon retweeted
LLMs have a score doubling time of 53.9 days on a robotics benchmark between July and October 2026, while speed increased by 4.4x and cost fell by 6.2x.
More results in our new paper: The Bitter Lesson Comes to Robotics 🧵
Simon retweeted
Biggest opportunity now as a software engineer is clear: master parallelism → outsize scale of output. Value creation in software has always come from leverage: small input, outsized output.
Parallelism-maxxing is not extremely quantifiable because it's so new. The spectrum runs between people managing a couple of agents on their local machine to those running an infinite number of agents + computers at a time than can be spun up and down on demand. You want to be at the far end of this spectrum, and you should be ROI-maxxing every token spent.
If you can do this and prove it, you will have an infinite number of opportunities available.
If you're still trying to do this locally you are at an objective disadvantage, equivalent of hosting a startup on a server in your closet vs using AWS. And if you're spending your time building and maintaining infrastructure that gives you no competitive edge, the AWS analogy applies in the question "why are you wasting your time doing undifferentiated heavy lifting instead of building unique customer-facing features?".
Simon retweeted
The HL Radio Singapore recordings are now live.
At the @HyperliquidX Community Event on October 5, we sat down with @chameleon_jeff and builders and contributors from across the Hyperliquid ecosystem.
All 13 sessions available here: youtube.com/playlist?list=PL…
Simon retweeted
We’re about to learn that most code written over the last 20 years was complete slop and most software developers were never that good
Simon retweeted
New on our Frontier Red Team blog: using Claude to formally verify software at large scale.
Formal verification can prove that code is free of certain bugs, but historically it has only been feasible for small codebases (or required a lot of expert time).
With AI models, however, this is beginning to change. In collaboration with @theoremlabs, we used Claude to prove security properties in over one hundred real-world open-source libraries over the span of a few weeks.
Read our research in full here: anthropic.com/research/forma…
Simon retweeted
who’s hiring? not asking for a friend.
DMs are open.
if you know me or we’ve worked together, a RT would mean a lot ❤️
Simon retweeted
hi everyone! excited to finally share what we've been building at sprout
our team of ex-fb engineers and a PM (founders’ median tenure: 6 years) banded together to save your kids from brainrot, and give parents their time back.
We just launched ParentBench, a live board testing whether AI can do the school-app errands parents do every day. Muse is way ahead: Muse Power can save parents 56 minutes every week. Help us map your kid's apps: sproutgoodhabits.com/map View article
Simon retweeted
Five days to go. Toronto, the choice is yours.
If you want to change the city, you have to change the mayor.
Vote for change on October 26.
Tbh as much as I love the railway UX, the biggest friction with AWS (cumbersome to manage) is actually largely irrelevant if you have responsible agent usage and well-defined IaC
I woke up to an email from AWS: "Your AWS Account may be compromised!"
As head of engineering, that's the email I have nightmares about.
Someone had stolen our AWS keys and was using them to run Claude. AWS blocked over 3,000 of their requests and locked down our whole account, so we couldn't make new deployments.
(The one request that got through was Opus. At least they have taste.)
I checked everything else. No new users, nothing deleted. Ok. Breathe.
Then OpenAI emailed. Then Stripe told us our live key was "publicly available online."
Everyone on the team ran a forensic script on their laptop. My agent went through CI, our servers and git history, and checked for the npm worm going around. All clean. (Which was somehow worse.)
Then we found it. We hadn't used one of the stolen keys since July, and the only place it still existed was an old Railway service that wasn't even running anymore.
Three weeks ago we moved our core infra from Railway to AWS, partly because of all the downtime and partly because we were tired of running up against Railway limits. It took a few months to make the jump, and we'd started wondering if we made the wrong call.
A few hours later, Railway announced it had been breached. AWS told us at 4am. Railway told everyone at 3pm.
They said "rotate your keys". But they also said deployments are frozen. We'd just migrated off, so we dodged that bullet by a hair.
Everyone still on Railway gets to choose: Leave your credentials exposed, or take down your servers?
