Eric Bidelman

leaning on proprietary undocumented formas like xcode projects might have seemed a good idea for many years, but it’s become as painful for llms as it’s always been for humans

1

💥 I just found a foundational flaw in Claude. All models, all interfaces. Repro steps below: 1. Go to Claude settings 2. Attempt to update your email address 3. If you can’t find how to do it on your own, ask Claude how to change your Claude email address 4. Validate that Claude is not hallucinating by going to https://support.claude.com and searching for “How do I change the email address associated with my account?” 5. Shake your head and think “sorry users, I know we kind of slid past this when you signed up. Hope the email you used to sign up never gets compromised or needs to change – magic links or SSO are the only option (darn it). And if it does, hope you didn’t buy an annual PRO plan because no refunds / transfers even if to the same human ✌ (grrrr…)” Perhaps this behavior is the result of conscious prioritization based on a thorough understanding of needs / trade-offs. If this behavior was an oversight, then based on prior trips on the modernization train, this could be a massive slog of tech debt. Particularly in a hyper-growth business dependent on uninterrupted & high-integrity data access / entitlements / provenance. Product people – let's use this moment to build foresight! - Don’t abdicate PM or UX from “technical” discussions about data models, identity, or access control – decisions within these domains have incredible implications - Customer onboarding & admin workflows are foundational CX, not afterthoughts - If you’re using Claude Code, invest in Git + GitHub integration for improved resilience (and much more)

3

Terminal Use (YC W26): Vercel for background agents. Terminal Use is hosting infrastructure for background agents that makes harness engineering easy. https://lnkd.in/gv99wN2t

51

2 Comments

Over the past year, my team and I built Pinterest's Model Context Protocol (MCP) ecosystem from the ground up: a central registry, a growing fleet of domain-specific MCP servers, and production integrations across our IDEs, internal chat surfaces, and AI agents. MCP is an open standard that gives large language models a unified way to talk to tools and data sources. At Pinterest, we used it as the substrate for AI agents that can safely automate real engineering tasks, from querying Presto data on demand to diagnosing Spark job failures and surfacing institutional knowledge. A few things I'm particularly proud of: * We designed for security from day one: two-layer auth (end-user JWTs + mesh identities), business-group-based access gating, and mandatory human-in-the-loop for sensitive actions. * We made it easy for any team to ship a new MCP server by creating a unified deployment pipeline that handles all the infrastructure, so domain experts just write business logic. * The ecosystem has scaled to 66,000+ invocations per month across 844 monthly active users, saving an estimated 7,000 engineering hours per month. This was a cross-functional effort. Thank you to everyone on the Agent Foundations, Security Engineering, and Traffic Engineering teams who made this possible, and to our engineering sponsors for their support and guidance. Full write-up on the Pinterest Engineering Blog: https://lnkd.in/e-mH26Bw

146

7 Comments

Experimentation isn’t the hard part. Knowing which decisions are reversible—and which aren’t—is. In the latest episode of Pendo.io’s Hard Calls podcast, Trisha Price and Jeff Lash break down how thinking in one-way vs. two-way doors helps product teams move faster without creating long-term drag. Give it a listen! #ProductLeadership #ProductManagement #DigitalAdoption #HardCalls

1

Investors take note. The Sass-pocalypse is overly sold off. Innovation and AI adoption will look like this going forward. Time tested platform and capablities, like Intuit, combined with agentic orchestration. Both pieces create the big wins for customers.

12

My Startup Was Working… Until It Wasn’t We had paying customers. We had local press. We were gaining traction. It was 2016. Then UberEats, DoorDash, and Postmates entered Portland with billions in funding. At the same time, Intel—where I worked full-time—announced massive layoffs. Overnight, my 40-hour week almost doubled. Midnight fab shifts, weekend work, endless overtime. My startup didn’t die because the idea was bad. It died because I didn’t have the financial runway to compete. Here’s what that painful chapter taught me: 1. Passion + grit aren’t enough. Startups need time, capital, and breathing room to survive. 2. Corporate is just built for stability. It can’t nurture the creative chaos that startups need. 3. Adaptation beats stubbornness. Sometimes the smartest move is to regroup, save, and come back stronger. So I made a choice: doubled down on my W-2 career, moved to Seattle, and joined Amazon to maximize income. Every dollar earned—and every loan I could pull—went straight into real estate. One property a year turned into two… then into double digits in a single year. Deals kept coming, I kept closing, and I built a local team to keep momentum alive. By the end of 2022, my portfolio was generating more passive income than my paycheck. That’s when WoolooAI.com was born—not as a flashy startup, but as a necessary system to simplify and automate the chaos: acquisitions, CRM, portfolio management, project management, all streamlined. The truth is: - Without the grind of my early startup days, I wouldn’t have landed the Amazon role. - Without Intel’s layoff threats, I wouldn’t have learned the importance of building a financial runway first. - And without the expertise I developed at Amazon, I wouldn’t have gained the skills that helped me build WOOLOO AI. The irony isn’t lost: the same challenges that once crushed me ended up shaping the freedom I enjoy today. 💡 Takeaway: Sometimes what feels like an ending is really just the foundation for the next chapter. 👉 If you want the full story, I wrote it here: https://lnkd.in/geEVye36 💬 I’d love to hear your story too—what twists or setbacks ended up shaping where you are today? #Entrepreneurship #Startups #RealEstateInvesting #AmazonAlumni #FinancialFreedom #LessonsLearned #HumbleGrowth

226

8 Comments