We made a Mac app that lets you run a bunch of Claude Codes in parallel. Introducing Conductor!

idea: what if @cursor_ai starts as simple as chatting with one smart Agent, and when you need more power, blooms into a full-blown IDE? simple up front, limitless when it counts

I no longer think you should learn to code.

Not everything needs to be clickbait - but it should absolutely key into curiosity if you want people to pay attention. This has nothing to do with YouTube. This is very basic attention economy and marketing stuff.

I’ve seen a lot of devs and founders looking to get into “vlog style content”. I don’t know a single person who wants to watch it.

if you hired someone new and they start making suggestions in the first week you have made a huge mistake

"Server rendering is stupid. It's only there to increase bills by cloud providers" Increasingly tired of seeing this sentiment so I'm going to explain why this is a really dumb take. 1. SSR costs are low The cost of turning JSON into HTML is not particularly large. Most SSR benchmarks don't include actual I/O, i.e. database calls. Render times in modern frameworks like Next.js are measured in milliseconds, rarely breaking 20ms. A basic DB query will take 10x that. Auth will take similar. There's also a ton of opportunities to skip the render altogether. If the data isn't behind an auth wall, it can usually be cached and invalidated on write rather than read. Now you only have to pay for CDN bandwidth 2. SSR reduces other cloud costs Let's say you have a page with 5 components that need data to render. If all 5 make an API call, you now have to manage 5 separate requests on the server. Each request has it's own: - TCP connection setup and teardown overhead - Authentication/authorization check and token validation - HTTP header processing and parsing - Database connection from the connection pool ...and much more "But theo! I batch my requests!" Sure you do. Link me your fully client-rendered site with zero waterfalls. If you're not using Relay, you're almost certainly making > 1 request client-side. And don't get me started on revalidation 🙃 With SSR, you can generate all of the page content in a single request. With out-of-order streaming (built into most modern frameworks), you can send down the static-y parts immediately and stream the rest later when it's ready. ALL WITHOUT MAKING A NEW CONNECTION. It is genuinely hard to fathom a world where the cost of SSR is higher than all the costs saved by reducing all of this per-request overhead. The only way it would be cheaper to avoid SSR is if you're building a toy app with no actual data. 3. SSR provides a better experience (not just SEO) One of the most common misconceptions I see around SSR. "I don't need SEO, why do I care?" Even if you only use SSR to render a shell, and do everything else client side, you still get: - route-specific metadata - route-specific js bundles - route-specific styles - route-specific loading states (my favorite) This means the user sees something faster, more meaningful, and all while loading LESS javascript. This seems like an obvious win to me. Once you're rendering on the server, doing the "right thing" for your users becomes significantly easier. I have a few videos where I talk about this, but you should definitely check out the SVG example in "My Website Is Airplane Proof" if you want to see how deep it goes. If you're not building a toy project, SSR saves you money.

do not avoid learning hard things because you think an AI may automate it nothing is going to cause a greater gap inability than AI in the next 10 years

I love whenever linux dweebs go "what's stopping you from using Linux?" while posting a screenshot of their incredibly generic rice with 15 novelty terminal apps open, notice how there's nothing productive going on there whatsoever 🤐

I had lunch with @dhh yesterday and he made very compelling arguments for Samsung phones and Beelink PCs. I did my best to Nix pill him lol. In any case I think we’re both excited to make Ghostty work really great with Omarchy and identified some key improvements to do that 🥰

We're releasing a preview of OpenAI o1—a new series of AI models designed to spend more time thinking before they respond. These models can reason through complex tasks and solve harder problems than previous models in science, coding, and math. openai.com/index/introducing…

a century ago, the richest guy alive couldn’t get penicillin, air conditioning, or instant global communication. today, a minimum wage worker has access to those things. so, what *exactly* is wealth today?

nbd, just prototyping some ideas for a better Amp CLI

SQL was never intended to be used by computer programs. It was a console language for printing reports. Embedding it into programs was one of the gravest errors of our industry.

My only regret in life is getting tattoos. If you don’t have any, don’t get them, no matter how meaningful you think they may be. They are degenerate and low-class.

The one person I know who actually uses Linux on the desktop is a brilliant Senior Staff Engineer. Last time I saw him I said something like “ayyy still using Linux eh?” — he sighed and said “yeah but things keep breaking and I’m sick of it. I’m about to give up and get a Mac” 😂

We're announcing some products tomorrow that many of you have been waiting a long time for!