Building @_downlink – I make AI 3x faster

San Francisco, CA
Joined November 2008
Pinned Tweet
I thought these were drawn exclusively for O’Reilly. My whole life is a lie.
Coffee is for closers
I spent $1.5M building our office after raising a seed round. My co-founder thought I was crazy. Here's what changed his mind... 𝐓𝐡𝐞 𝐂𝐨𝐧𝐭𝐞𝐱𝐭: After our seed round, I looked at our team. Mostly immigrants. Working 6-day weeks. Building something incredibly hard. The office wasn't just where they worked. It was becoming their home. So I made a bet, what if we actually designed for that? The requirements I gave our real estate agent: - Shower (for ocean swims between meetings) - as close to the beach as possible, ability to quickly go surfing/kiting etc. - Big enough kitchen for a chef - Room for an actual sauna People thought I was building a vacation house, I thought: I am building a place worth the sacrifice. 𝐇𝐞𝐫𝐞'𝐬 𝐡𝐨𝐰 𝐈 𝐦𝐚𝐝𝐞 𝐢𝐭 𝐰𝐨𝐫𝐤: - Found one of SF's best real estate lawyers. Negotiated hard. - Negotiated Tenant Improvements + First year for free - Effective cost: $250k (not $1.5M) Then I was extremely prescriptive with design and construction. No endless back-and-forth. I drew what I wanted. Told them to build it. Cut iteration time by 80%. 𝐖𝐡𝐚𝐭 𝐰𝐞 𝐛𝐮𝐢𝐥𝐭: - Nordic vibes (keeping our European souls) - Industrial kitchen - Sauna room (yes, like our product: sauna.ai) - Ocean access - Space that feels like home Conclusions: - This "expensive" decision already paid for itself. - In SF, recruiters charge $100k per engineer. We've closed multiple hires -because candidates walked in and said: "I want to work here." But the real ROI isn't only financial. It's this: - We do Friday AMA as a BBQs on the beach. - People actually use the surfboards. - The team's lifestyle supports the intensity of the work. EVERYONE WANTS IN, doesnt matter if events, hiring or using the space as coworking (@bertie_ai and I open it up for our portfolio companies) My co-founder's response after 3 months: "You were right." Some founders optimize for low burn rate. I optimize for: Can great people sustain this pace for years? Because great companies aren't built in one sprint. They're built by people who can go the distance. We're hiring: wordware.ai/careers (Comment if you want intros to our real estate agent, lawyers or construction team - happy to connect)
Over the years in SF you’d meet many company’s with bougie offices, way ahead of their stage. In my experience, at best, it was uncorrelated with success. Likely slightly negatively correlated.
I spent $1.5M building our office after raising a seed round. My co-founder thought I was crazy. Here's what changed his mind... 𝐓𝐡𝐞 𝐂𝐨𝐧𝐭𝐞𝐱𝐭: After our seed round, I looked at our team. Mostly immigrants. Working 6-day weeks. Building something incredibly hard. The office wasn't just where they worked. It was becoming their home. So I made a bet, what if we actually designed for that? The requirements I gave our real estate agent: - Shower (for ocean swims between meetings) - as close to the beach as possible, ability to quickly go surfing/kiting etc. - Big enough kitchen for a chef - Room for an actual sauna People thought I was building a vacation house, I thought: I am building a place worth the sacrifice. 𝐇𝐞𝐫𝐞'𝐬 𝐡𝐨𝐰 𝐈 𝐦𝐚𝐝𝐞 𝐢𝐭 𝐰𝐨𝐫𝐤: - Found one of SF's best real estate lawyers. Negotiated hard. - Negotiated Tenant Improvements + First year for free - Effective cost: $250k (not $1.5M) Then I was extremely prescriptive with design and construction. No endless back-and-forth. I drew what I wanted. Told them to build it. Cut iteration time by 80%. 𝐖𝐡𝐚𝐭 𝐰𝐞 𝐛𝐮𝐢𝐥𝐭: - Nordic vibes (keeping our European souls) - Industrial kitchen - Sauna room (yes, like our product: sauna.ai) - Ocean access - Space that feels like home Conclusions: - This "expensive" decision already paid for itself. - In SF, recruiters charge $100k per engineer. We've closed multiple hires -because candidates walked in and said: "I want to work here." But the real ROI isn't only financial. It's this: - We do Friday AMA as a BBQs on the beach. - People actually use the surfboards. - The team's lifestyle supports the intensity of the work. EVERYONE WANTS IN, doesnt matter if events, hiring or using the space as coworking (@bertie_ai and I open it up for our portfolio companies) My co-founder's response after 3 months: "You were right." Some founders optimize for low burn rate. I optimize for: Can great people sustain this pace for years? Because great companies aren't built in one sprint. They're built by people who can go the distance. We're hiring: wordware.ai/careers (Comment if you want intros to our real estate agent, lawyers or construction team - happy to connect)
15
3
1
201
O'Reilly Wine Pairings Book: Evals for AI Engineers by @sh_reya and @HamelHusain Wine: Balgownie 2023 Gold Label Shiraz
👀 Animals have been assigned. Scheduled to print fall 2026! We have iterated on this with over 3k students (and continue to do so). We give our students access to the full draft as part of our evals course (link in bio).
1
1
1
27
Yes! And you can use cloudflare or configure request-level caching. Many ways to intercept a request from ever hitting the database at all.
Replying to @teej_m
If you live in an HTTP world use HTTP caching - that’s ETags and conditional requests. The query you never see is free.
3
Or just copy/paste this into your AGENTS.md file and let it rip. I don’t care.
I learned this when I was 20. It's not hard to start. There are 2 types of queries: reads and writes. Most of your queries are reads, handle those first. Do this, in order: 1/ Reduce reads - Cache, cache, cache. Use read-thru and write-thru caching. Use Redis. 2/ Optimize slow reads - Add indexes. Fix your N+1 queries. Add limits. Sort responsibly. Alert on slow queries. 3/ Scale hardware - Add read replicas. Upgrade memory & I/O. 4/ Split up data - Shard when you have to. Partition writes when needed (you won’t need it). Understand “good enough”. A single write instance is fine for most people. And if it's not slow, leave it alone!
1
8
I learned this when I was 20. It's not hard to start. There are 2 types of queries: reads and writes. Most of your queries are reads, handle those first. Do this, in order: 1/ Reduce reads - Cache, cache, cache. Use read-thru and write-thru caching. Use Redis. 2/ Optimize slow reads - Add indexes. Fix your N+1 queries. Add limits. Sort responsibly. Alert on slow queries. 3/ Scale hardware - Add read replicas. Upgrade memory & I/O. 4/ Split up data - Shard when you have to. Partition writes when needed (you won’t need it). Understand “good enough”. A single write instance is fine for most people. And if it's not slow, leave it alone!
I have no understanding of database scaling. How many queries is too many, 1k/second? 10k/s?
39
191
7
2,814
“Head of data” is dead.
10
43
This is cool
Excited to announce the release of pg_lake which lets you: - Manage Iceberg tables directly in Postgres - Query raw data files in your data lake - Flexibly data import/export Repo at: github.com/snowflake-labs/pg… Announce post: snowflake.com/en/engineering…
9
I worked with a Chess coach for a year, increased my rapid rating by 500+ points, then played an OTB tournament at the Mechanics' Institute in SF and lost in 10 moves to a 12-year-old
Always give your opponent respect (even though you think they are an idiot)! You wanna crush them but you should also always expect them to play the best move! No hope chess.
1
31
» teej retweeted
Was chilling how easily Claude Code built me a native Swift Mac OS menubar app (without XCode!) and loaded this model
1
1
2
someone hook him up to an LLM it's time
3
12
Since normies will never open an arxiv link, the ai grifters realized they can post a screenshot of a paper, say literally anything, and farm engagement. Sad times
New Stanford+Anthropic paper shows long step-by-step prompts can break model safety and trigger harmful answers. 😟 Long reasoning can quietly neutralize safety checks that people assume are working. The trick adds a benign puzzle and long reasoning before the harmful ask, plus a final answer cue. This shifts attention to the puzzle tokens, so the harmful span gets less weight. The internal safety direction weakens, and the refusal behavior drops. Middle layers carry safety strength, later layers carry the final decision, both shrink with longer chains. Switching off key attention heads lowers refusals further, which matches the theory. On a public model, short reasoning hit 27% attack success, long reasoning reached about 80%. Across frontier systems, the method hits up to 99% success. So scaled reasoning boosts accuracy but also opens a new jailbreak path. ---- Paper – arxiv. org/abs/2510.26418 Paper Title: "Chain-of-Thought Hijacking"
1
1
6
many such cases
We used Kafka + Flink + ScyllaDB for a project that emitted 1 record every 5 minutes instead of Spring + Postgres Why? so we could flex our "realtime data stack" and get promoted faster It worked.
9
If Waymo offered $1 off Dunkin with each ride, this would be solved in 60 seconds flat
Today at 2pm EST, Boston will consider becoming the first major city in the world to ban fully autonomous vehicles based entirely on vibes. Waymo is involved in 5X fewer injury-causing collisions than humans, and employment in SF's taxi and limo industry grew by 7% last year!
1
8
I WROTE A THING ABOUT THE DBT AND FIVETRAN MERGER I FORGOT TO POST IT, ITS VERY LONG "LIKE AARON SORKIN MEETS MODERN DATA STACK" ~ @frasergeorgew ALL CHARACTERS AND EVENTS IN THIS SHOW—EVEN THOSE BASED ON REAL PEOPLE—ARE ENTIRELY FICTIONAL. ALL CELEBRITY VOICES ARE IMPERSONATED…..POORLY. THE FOLLOWING PROGRAM CONTAINS COARSE LANGUAGE AND DUE TO ITS CONTENT IT SHOULD NOT BE VIEWED BY ANYONE
the only correct take [and incoming essay] on the dbt + fivetran merger
2
1
1
29
I have never reinstalled MacOS in my entire life
So today i had to completely reinstall my laptop for reasons. I started installing following Arch (btw)'s user guide, and as always, bumped into various issues. Then I decided to let gpt5 guide me. It's been the easiest arch install I've had. We're truly living in the future!
4
59
Did I tell you I hate corporates open source maintained by people on 9-5 salaries?
82
61
19
3,367
» teej retweeted
To anyone who advocates this all I can say is, respectfully: grow the f*ck up and think about the power and platform you have. I watched my dad (53) die from lung cancer. As in, I sat next to him in the hospital over weeks and days and was there to the very end. He had a 4 week time period from stage 4 diagnosis to death and I can assure you, it's not something you'll ever want to experience yourself or watch someone go through. What started as his body generating blood clots at scale ended in what can best be described as an extended drowning. All because he got addicted to cigarettes.
Palmer Luckey (@PalmerLuckey) is getting into nicotine. "Basically, America smoked its way to being the dominant hyperpower. It kept people focused, it kept people fit. It's an appetite suppressant. "I'm becoming more and more convinced that the health benefits of not smoking have not been properly traded against the health problems caused by the resulting eating." "I think the crazy version of this is we'd all be better off with lung cancer eventually, but fit until then." "Is vaping worse than being fat? I don't know. I struggle. Based on the evidence I've seen."
» teej retweeted
You can't keep doing this.
2
2
76