As the founder/leader/manager/principal of a professional services company or agency, one of your main jobs is to be a “variability regulator” between your clients and your team. #team #management #lessons

CTO watching CEO pitch investors features that don't exist:

Software engineering in 2026 needs two roles: A pirate and an architect. The pirate codes as fast as possible to figure out what's valuable. The architect turns that sloppy mess into a well-oiled machine. Here's how it works and why:

So @jack wants ~6,000 employees reporting directly to him in the new version of the company. Layers between CEO and any employee in the company: ~5 today → 2-3 this year → basically zero

In my company, we use Google Meet all the time; we used to use Zoom... but never Teams for video calls. Now, some clients prefer Teams... and whenever I go to a meeting, and I see a Teams link, my impulsive reaction is "ahhhhhh crap! teams!" and it ruins my day a little.

Hace poco me escribió alguien que escuchó este podcast que grabamos hace casi 2 años ya (cómo vuela el tiempo!) y creo que nunca compartí esto por aquí. bit.ly/corpcast

AI is making CEOs delusional

Claude can now build interactive charts and diagrams, directly in the chat. Available today in beta on all plans, including free. Try it out: claude.ai

90% of stand-up meetings look exactly like this.

The token cost to build a production feature is now lower than the meeting cost to discuss building that feature. Let me rephrase. It is literally cheaper to build the thing and see if it works than to have a 30 minute planning meeting about whether you should build it. It’s wild when you think about it. This completely inverts how you should run a software organization. The planning layer becomes the bottleneck because the building layer is essentially free. The cost of code has dropped to essentially 0. The rational response is to eliminate planning for anything that can be tested empirically. Don’t debate whether a feature will work. Just build it in 2 hours, measure it with a group of customers, and then decide to kill or keep it. I saw a startup operating this way and their build velocity is up 20x. Decision quality is up because every decision is informed by a real prototype, not a slide deck and an expensive meeting. We went from “move fast and break things” to “move fast and build everything.” The planning industrial complex is dead. Thank god.

What does it mean for software engineering when we no longer write the code? Here's the take from Boris Cherny (@bcherny), the creator of Claude Code. Timestamps: 00:00 Intro 11:15 Lessons from Meta 19:46 Joining Anthropic 23:08 The origins of Claude Code 32:55 Boris's Claude Code workflow 36:27 Parallel agents 40:25 Code reviews 47:18 Claude Code's architecture 52:38 Permissions and sandboxing 55:05 Engineering culture at Anthropic 1:05:15 Claude Cowork 1:12:48 Observability and privacy 1:14:45 Agent swarms 1:21:16 LLMs and the printing press analogy 1:30:16 Standout engineer archetypes 1:32:12 What skills still matter for engineers 1:35:24 Book recommendations Brought to you by: • @statsig  — ⁠ The unified platform for flags, analytics, experiments, and more. statsig.com/pragmatic • @SonarSource – The makers of SonarQube, the industry standard for automated code review. Proactively find and fix issues in real-time with the SonarQube MCP Server: sonarsource.com/products/son… • @WorkOS – Everything you need to make your app enterprise ready. workos.com/ Three interesting things from this conversation: 1. Boris automated himself out of code review well before AI. Boris was one of the most prolific code reviewers at Meta company. And he worked hard to minimize time spent on code review. His system::every time he left the same kind of review comment, he logged it in a spreadsheet. Once a pattern hit 3-4 occurrences, he’d write a lint rule to automate it away! 2. PRDs are dead on the Claude Code team: prototypes replaced them. Instead of writing Product Requirement Documents (specs), they build hundreds of working prototypes before shipping a feature. Boris: “There’s just no way we could have shipped this if we started with static mocks and Figma or if we started with a PRD.” 3. This is the year of the generalist (and maybe the year of those with ADHD) Boris’s work has shifted from deep-focus single-threaded coding to managing multiple parallel agents and context-switching rapidly. As Boris put it: “It’s not so much about deep work, it’s about how good I am at context switching and jumping across multiple different contexts very quickly.”

Me defending my O(n^3) solution to the coding interviewer.

Online calendars are like credit cards; your time is spent in advance before you get it... same feeling when you get paid, and all your money is immediately debited from your account to pay the credit card bill.

mini-rant: when I ask you for your logo in svg, I mean the logo in vectors (or curves?) saved in svg format, not a bitmap saved as svg, that doesn’t help. 🫠 at least that is better than the ones that send it on a docx or xlsx… but ultimately the same end result, a bitmap

🚨MAJOR BREAKING: Jimmy Kimmel just performed his full monologue and it was OUTSTANDING. 🔥 I am so glad he is BACK and in FULL FORM! Welcome back Jimmy Kimmel!

RT @Indian_Bronson: GPT-image feedback loop, asking the machine to replicate the image without changing anything;

Cue the choreography and merriment. #Severance has been renewed for Season 3.

We have another programmer opening at 37signals. Fully remote, pay between $170,000 - $201,980, eligible for profit share after 2 years, and the chance to work with some amazing people on Basecamp, HEY, ONCE, Rails, Kamal. Oh, and Linux 😄 jobs.rubyonrails.org/jobs/77…

Here's a full recap of our news and updates from #GoogleIO — in under 10 minutes 🎉