Product & GTM veteran; pursuer of cooking, history, and gardening. AI for productivity, automating workflows & prototyping. GitHub: enalbenerraw

Research Triangle
Joined July 2007
I’m in a text group with 30 AI-pilled enterprise executives. Someone in the group asked: “What is the highest ROI AI use case/initiative in your business?” There were a ton of great answers, but mine was the 10x leverage engineers are getting from coding agents. A group member asked me to explain what I meant. So I slacked two of our engineering leaders and said “Why are you guys so cracked?” Here’s what one of them (@dan_zakon) said: Software engineering is becoming more unrecognizable every day. Historically, detailed system architecture planning was expensive and rarely done. “Agile development” became the industry buzzword to justify not planning upfront. Even the strongest engineers could not hold the whole file structure, code conventions, dependencies, edge cases, and product requirements in their head at once. Now we spend 95% of the time and effort planning and 5% executing. Over the past year at @tenex_labs, we’ve built custom tooling for structured engineering context that self-improves. It gives agents instant access to things like product intent, architecture, conventions, delivery workflows, and plans. With this process, we use agents to map out whole systems far in advance with a level of coherence that used to be impossible. Then the system can almost assemble itself. Long-running agents execute against the plans, implement scoped work, adhere to conventions, run tests, fix issues, update GitHub, sync Linear, refresh documentation, and revise the original plans as progress is made. The result is a fundamentally different operating model for engineering. Across Tenex, we are consistently proving it with small teams that are building complex, ambitious products in months. Work that used to require huge teams, multi-year timelines, and massive coordination overhead is now becoming the baseline for what small, elite engineering teams can take on.
41
18
5
273
74,838
Today we're launching Intercept: a $500M philanthropic initiative to make respiratory infections, like the common cold and flu, a thing of the past. We treat respiratory infections as a minor nuisance, but that’s really not the case. Most of us will spend 5% of our lives (!) sick from these viruses, they kill 1M people a year, cost $600B annually in productivity, and periodically threaten civilization through pandemics. So, if they’re such a big problem, why haven’t we dealt with them yet? Last year we convened ~40 leading scientists, pharma R&D leaders, biotech investors, and regulatory experts to better understand that. We heard two main reasons: (1) First, it’s just technically very challenging: respiratory viruses represent hundreds of distinct, mutating strains across several families. Fortunately, recent breakthroughs make this newly possible. (2) Second is a lack of funding: broad-spectrum solutions have historically been underfunded, in part because they’re not a great fit for most philanthropic or commercial funding (and while COVID generated a burst of activity around preventing and understanding respiratory infections through an influx of new funding, that hasn't been sustained). We think that with enough focus and funding, this might be solvable. Intercept is a $500 million philanthropic initiative that will take advantage of new tools to catalyze the development and deployment of two types of products: broad-spectrum preventatives and air cleaning technologies. This problem is undoubtedly difficult. But it’s more tractable now than it’s ever been. We think we should give it our best shot. We’re enormously grateful to our anchor funders: @stripe, @AnthropicAI, @TheFluLab, @FoundationOAI and individuals from Jane Street. And, I’m very excited to be building this with @incredutility and the rest of the team.
198
553
218
3,544
1,458,819
No comments.
173
3,152
187
25,324
972,738
This is so insanely corrupt, I can’t even believe it. More than half the donors to Trump’s $400 million White House ballroom just won over $50 billion in new federal contracts in six months. And here’s the part that should make your blood boil. Sixteen of these 27 donors were facing federal enforcement actions, antitrust reviews, labor cases, securities charges. Many of those cases have been quietly dropped or scaled back since Trump took office. You write a check, your legal problems disappear. That’s not a coincidence. The White House won’t even release the full donor list. They’re hiding it on purpose, because daylight is the one thing pay-to-play can’t survive. A federal judge already ruled ballroom construction has to stop until Congress authorizes it. Government is supposed to serve the people, not auction itself off to the highest bidder. When access goes to whoever pays the most, working families always end up paying the price. We either end the corruption, or the corruption will end us. wapo.st/3QmJjSz
1,565
23,383
1,357
48,954
1,371,281
Your CLAUDE.md file is probably growing every week. Pawel Huryn's has six items and hasn't changed in months. His file contains a 2-3 sentence project description, a file structure map so the agent never scans blindly, identity context (role, audience, goals), knowledge routing that tells the agent where domain-specific files live, workflow pointers, and a three-line self-improving prompt. That's the entire file. Six items. A routing table. Writing style rules live in a voice file. Good and bad examples live in a patterns file. Platform instructions live in platform-specific folders (x/, linkedin/). Historical metrics live in a metrics file. Hypotheses and confirmed rules live in domain-specific knowledge files. Detailed procedures live in skills folders. The agent reads the routing table, identifies the domain, and loads only what it needs. The three-line self-improving prompt is the part you can paste into your own CLAUDE.md today: 1. Before starting any task, review existing rules and hypotheses for this domain 2. Apply confirmed rules by default to your work 3. After completing work and receiving feedback, update rules and hypotheses based on what you learned Three sentences. Works for any domain: marketing, testing, strategy, hiring, content. The agent reviews what it knows, applies what's confirmed, and updates its knowledge after every session without you rewriting instructions. Over time, the system auto-discovers hook patterns that correlate with engagement, voice archetypes per platform, sentence structures that get quoted and shared, and which format/length/topic combinations drive reactions. All organized by domain, all ranked by evidence. The compound gap between someone running this and someone prompting from scratch doubles every month.
This guy literally broke down everything you need to master Claude: 6:07 - Why to Stop Using Chat 9:56 - Cowork vs Code vs Dispatch 18:44 - Skills and MCP Connectors 25:03 - The Skills Marketplace 29:06 - Strategy Canvas Demo 35:14 - Skill Iteration Cycle 40:46 - Why You Need Code 44:43 - Building a Second Brain 56:00 - Self-Improving Knowledge 1:10:00 - Dispatch and Remote Work 1:21:07 - Top Mistakes and Future
4
20
181
17,613
This is fantastic work
Who actually shapes AI policy in the U.S.? We mapped 1,812 entities: 745 people, 918 organizations, 2,925 relationships. Frontier Labs, AI Safety orgs, Think Tanks, Government, VCs, and more. mapping-ai.org
167
2
1,372
193,578
no professional economist has ever been or will ever be again this funny on purpose
REPORTER: You mentioned that, staying on as Fed governor, you intend to keep a low profile. Could you give us a little more detail on what that looks like? JEROME POWELL: *ducks down*
114
2,841
43
44,720
1,641,149
A truck loaded with thousands of copies of Roget's Thesaurus spilled its load leaving New York. Witnesses were stunned, startled, aghast, stupefied, confused, shocked, rattled, paralyzed, dazed, bewildered, surprised, dumbfounded, flabbergasted, confounded, astonished, and numbed.
1,057
3,484
517
19,009
862,207
Blano retweeted
My employer has a new, astronomically awful expense-reporting system. Opaque, inefficient, and mind-bogglingly duplicative. Am I being too much of a smartass?
320
202
50
11,031
1,876,891
Blano retweeted
Went to the Oreo website and hit accept all cookies. Now we wait.
405
18,607
427
159,953
2,940,534
Blano retweeted
I dread the day when @atmoio stops posting. 🫶🫶🫶
Claude Mythos is Delusional
28
83
3
1,397
211,116
Blano retweeted
Hello, Moon. It’s great to be back. Here’s a taste of what the Artemis II astronauts photographed during their flight around the Moon. Check out more photos from the mission: nasa.gov/artemis-ii-multimed…
9,749
169,446
9,052
794,829
30,494,459
steve jobs' home office
This is what offices looked like before AI was a thing
17
56
3
1,242
98,312
Replying to @Pogue
I’m 75 pages in. It’s really good! I’ve read nearly every book written about Apple (and the people behind the company) and I’ve already learned a number of interesting nuggets in @pogue’s book. Book clubs — take him up on his offer! 😊👍🏻🍏
3
10
3,094
Blano retweeted
Here's my "@CBSSunday Morning" story about Apple's first 50 years.. youtube.com/watch?v=C-02yv6C… And my full, unedited interview with CEO Tim Cook. youtu.be/xLqUXIwPGUo?si=10hP…
22
79
8
425
163,231
Blano retweeted
The @WSJ review of "Apple: The First 50 Years": “It’s about as dramatic a business narrative as you could think up. To write a biography of a corporation that has lived numerous lives in its 50 years is a huge task, and Mr. Pogue’s easy style fits…" wsj.com/arts-culture/books/a…
5
14
120
12,622
Blano retweeted
One thing that totally blew up my January was being offered the unique opportunity to write a review of @Pogue's book for The Wall Street Journal. Couldn’t pass up the opportunity, and so I read a big book about Apple history at the beach! sixcolors.com/offsite/2026/0…
2
44
4,524
Some of our best hires were totally unqualified on paper. They always had the same qualities: entrepreneurial, high agency, smart, mission aligned, and they got shit done. If you’re hiring, especially in early stages, seek out & bet on these people. Don’t over-index on resumes.
938
1,676
333
18,057
1,389,732
20% of all open PM jobs on LinkedIn right now are AI PM roles. That's roughly 10,000 out of 50,000 listings. And the trajectory is obvious: FedEx, UPS, Target are cutting PMs. OpenAI, Meta AI, and Amazon Bedrock are hiring them. The constraint nobody is pricing in is that these aren't just "PM jobs at AI companies." They require a completely different technical vocabulary. Context engineering, orchestration, observability, evals. Most PMs can't explain the difference between RAG and fine-tuning, let alone when to use them together. Shopify now puts AI usage into performance reviews. Teams must prove AI can't do the job before requesting headcount. Lütke called it a "fundamental expectation." Shopify cut its workforce by a third since 2022 while keeping headcount flat and selectively investing in AI engineers at higher comp. This is the pattern across the industry. Companies aren't asking "should we use AI?" They're asking "why aren't you using AI already?" And they're measuring it. The PMs who spent 2024 and 2025 treating AI tools as optional enrichment are about to discover that 20% number is heading toward 60%. The learning curve doesn't get easier when you're competing against candidates who've been building agents and running evals for two years.
I gave the keynote at @UCBerkeley's ProductCon - "How to Become an Elite AI-Powered Product Manager" This is the full talk + behind-the-scenes footage: 0:00 - Why This Matters 4:11 - Layer 1: Prompting Fundamentals 10:46 - Layer 2: AI Co-pilots 19:45 - Layer 3: AI Agents 27:00 - Layer 4: AI Prototyping 31:45 - Layer 5: AI Discovery 39:37 - Layer 6: Evals & Observability 42:53 - Layer 7: Vibe Experimentation 50:56 - Behind the Scenes
11
29
1
228
65,433