If it already wasn’t obvious. Marvin Harrison jr was half stepping in AZ because he was over it. He will be a high end/solid WR in the league.

Fred Warner is da goat

Another banger

We are looking at you @JensenHuang . We need you and Nvidia to step up for open source and stop this absurdity.

John mateer > Arch manning

All the regulations being floated by frontier model companies must be viewed through the lens of them losing tokens to Open-Source models. The timing of these regulations seems to line up perfectly with Open Source closing the gap significantly (but not completely) — and @nvidia going all in on open source in the last 60 days. If we’re gonna regulate, why don’t we require that last year’s frontier models and weights be open-sourced?

Learn to build a harness, folks. It's not surprising to me that so many YC builders want to build domain-specific harnesses. If you work long enough on a domain-specific problem, you quickly realize the opportunity. But you also realize how important that harness will be to stay competitive in the agentic era. From a product perspective, harnesses open up interesting new surface areas and experiences for the services/products you provide. From a technical perspective, harnesses are how you build and maintain a framework and set of best practices for how your users/customers interact with what you offer. Understanding how to build and design a harness means you can build much stronger intelligence stacks, given that you can customize it and understand the domain well. That's extremely valuable. It may not seem apparent yet, but a harness wave is coming. If you are getting started, give this list of harness papers to your agents and start upskilling: academy.dair.ai/papers/colle… If you are already a builder, try building one for your specific domain. It's a lot of fun, and you learn a lot of interesting things to enhance your current agentic tools.

We live in a world where we are constantly lectured on “safety” and “risk” from people who have never been unsafe or at risk in their entire lives. From charter schools, to Ivy League, to $300k entry level roles. They pontificate on theoretical outcomes while being abstracted away from actual reality. Ignoring the real concerns voiced by the 99% who intimately understand danger. Their recommended outcomes almost always aligning with a reason to create more centralized power and regulatory capture to protect themselves from competition and guard their margins. People need to snap out of the malaise and use basic pattern recognition. Things aren’t this or that, we live in a world of dynamic systems where you can be responsible and not create centralized systems that we are dependent on forever.

ASTRA ATRSA RSTRA RESTR RESET

This is exactly right

Verticalized open source models will win the day. Turns out AGI is an incredible tool but not an all encompassing labor replacement, rather an efficiency improvement. Either AI replaces human labor or token costs need to drop through the floor.

If you hear a person talking about “tax the rich” and they aren’t first talking about getting clear visibility on where our tax dollars are currently going. Watch out. They are a wolf in sheep’s clothing. Pouring more water into a cup with a hole in it is just stupid.

I just found out Dario Amodei is married and even Claude still won’t confirm it. But that’s not the shocking part. 🤯 His wife Camilla “Cami” Clark co-founded a porn startup, pitched Jeffrey Epstein for money (he passed), dated Eric Schmidt, then helped bring Schmidt in as an early Anthropic investor. Once she was with Dario every website, LinkedIn, and Instagram account vanished. The safety lab’s own model still says his marital status “doesn’t seem to be clearly confirmed.” That’s *not* a small scrub.

Designers who build, should be paid the same as engineers.

It has never been a better time to be a designer

Bro the level of pettiness is literally hilarious. I’m totally here for it. “Yo dude, drop this right after the OpenAI webinar”. 😂

If Yu-Gi-Oh was about Tech Jobs

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes: 1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS. A healthy team needs a mix of these, depending on the product: - A product that is new and pre-PMF needs people that are strong at 1+2+3 - A product that is growing and has found PMF needs 2+3+4 and some 5 - A product that has strong PMF needs 3+4+5 and some 2 Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

My design workflow for setting up 0-1 projects. Here is the tactical order: 1. DESIGN.md + Google design linter first
Write the spec with tokens, components, states, accessibility rules, and light AX notes. Choose Radix or shadcn/ui as the accessible primitive base. Document the split so Radix handles behavior while your tokens and components handle visuals. Run the linter to validate structure. 2. Set up Pencil.dev in the repo
Connect it to your project and import tokens. Use the in-repo canvas to design the branded layer on top of the Radix foundation. 3. Iterate the design system in Pencil
Focus on higher-level components and patterns. Keep everything version-controlled and guided by DESIGN.md. 4. Install and configure Impeccable
Point the skill at your DESIGN.md and tokens. With solid primitives underneath, Impeccable can focus on polish and catching generic AI output. 5. Implement in the codebase
Install Radix or shadcn primitives. Use Claude Code plus Impeccable to compose and style your branded versions. Work component by component and re-run the linter after changes. 6. Close the loop with verification
Add token sync and basic a11y checks. Document agent-friendly patterns in DESIGN.md such as predictable states and clear loading signals. The Radix base already covers much of the accessibility work. Anyone else doing anything similar?

How we imbue coding agents with our design standards