
Sai
42 posts



DESIGN: THE FIRST AI CASUALTY I'm increasingly sure that 2026 signals the end of product design as a full-fledged stand-alone function within companies. If so, it will be the first role / function to be eliminated by AI on a go-forward basis. Instead of hiring FT designers, startups are hiring / will hire design consultants to create a design system that the founder likes (this takes a few weeks max). Once the design system is finalized, PM/Eng feed it into their AI tool of choice to generate prototypes. The design system is refreshed annually by the same consultant. Larger companies will likely not backfill design roles and will do some targeted attrition to reduce the design department to 20% the size it is today. If you're a designer, I think you have two choices: 1. Become an entrepreneur: Start a design agency and become the go-to resource for design systems for startups and even larger companies. This can be a good recurring revenue business. 2. Become a builder: Add PM/Eng responsibilities to become a product builder. Would suggest you embrace this proactively vs waiting for the other shoe to drop. I'm really sorry about this - some of my best friends and the people I admire most and have learnt the most from are designers - but it seems inevitable.


Stanford is kinda crazy because as a CS undergrad this term you’re choosing between: - CS336: 0 to hero on frontier model training - CS224R taught by Chelsea Finn (founder of Pi) - CS231N taught by Fei Fei Li (Imagenet, WorldLabs CEO) - CS221M Mech Interp Intro taught with Goodfire And a host of personal podcasts delivered by $T CEOs.

thread of types of reactions from programmers to LLM progress 1. the scaling law believer it’s all over, just a matter of time. might as well enjoy these last few years apps and UI will be a solved problem in a couple a years, we’ll maybe stick around as testing nannies



you gotta be strangermaxxing you gotta be chatting up random people as much as you can. Big Individual lobby doesnt want you to, but that is why you must


New blog post: "A sufficiently detailed spec is code" I wrote this because I was tired of people claiming that the future of agentic coding is thoughtful specification work. As I show in the post, the reality devolves into slop pseudocode haskellforall.com/2026/03/a-suff…


Ten years ago, AlphaGo’s legendary match in Seoul heralded the start of the modern era in AI. Its famous ‘Move 37’ signaled to us that AI techniques were ready to tackle real-world problems in areas like science - and ideas inspired by these methods are critical to building AGI




the rationalists writ large were mostly right about most things btw. if you instinctively snicker about yudkowsky, scott, or whomever i take you to be a fish who’s unaware of the water


if you're in college, get an internship at either openai, anthropic, xai, meta ai, or google deepmind. your career depends on it


how I convey intent to autonomous AI agents: 1. frequently write 1-2 paragraphs of rationale (why > how) 2. when logging fixes, write Problem, Solution, Rationale 3. always make agents log direct quotes w/ no rephrasing 4. all instructions are recommendations subject to change






