Joe Chung

The Age of the TPM Coordinator is ending. The Age of the Autonomous TPM has began. We will see TPMs focus less on being coordinators and more on creating platforms, workflows, and tools to scale program execution.

10

1 Comment

The Age of the TPM Coordinator is ending. The Age of the Autonomous TPM has began. We will see TPMs focus less on being coordinators and more on creating platforms, workflows, and tools to scale program execution.

📌 Build Momentum Through Continuous Releases 📌   Releasing something every sprint keeps your team sharp and confident. Sharon Allpress, VP of Strategic Engagements at EOT.AI, shares how maintaining a continuous release rhythm prevents teams from getting rusty and strengthens collaboration across product, engineering, and stakeholders.   Here’s her approach: Release something every sprint, even small improvements Keep documentation and stakeholder comms updated Use momentum to stay ready for larger launches   🎥 Watch now on YouTube: https://lnkd.in/e-PgruY7

1

𝐁𝐞𝐡𝐢𝐧𝐝 𝐭𝐡𝐞 𝐒𝐜𝐞𝐧𝐞𝐬: 𝐇𝐨𝐰 𝐒𝐭𝐫𝐞𝐚𝐦𝐥𝐢𝐧𝐞𝐝 𝐅𝐢𝐥𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐒𝐚𝐯𝐞𝐝 𝐎𝐮𝐫 𝐒𝐚𝐧𝐢𝐭𝐲 Let’s talk about the chaos of collaboration—when everyone’s working hard, but no one can find the right file. Last quarter, our team was knee-deep in a client proposal when disaster struck: three different versions of the budget were floating around. One was in Slack, another buried in a Google Drive folder labeled “Old Stuff,” and the third? Attached to an email from 3 weeks ago with the subject line “Here you go.” (Helpful, right?) As the resident Organization Enthusiast (read: file-naming stickler), I decided enough was enough. Here’s what changed the game: ✔ Centralized Hub: Migrated everything to Microsoft Teams with clear folders—no more “mystery documents” lurking in random places. ✔ Version Control: Implemented a “_v1, _v2” naming system (and trained the team to actually use it). ✔ Automated Backups: Set up nightly cloud backups so even the “accidental deletions” weren’t fatal. The result? Zero “Which file is the right one?” panic attacks, and our project manager called it a “glorious miracle.” (High praise from someone who once rage-quit a Zoom call over a missing spreadsheet.) The lesson? Time spent organizing isn’t overhead—it’s insurance against future chaos. 𝐆𝐨𝐭 𝐚 𝐟𝐢𝐥𝐞 𝐦𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 𝐡𝐨𝐫𝐫𝐨𝐫 𝐬𝐭𝐨𝐫𝐲 (𝐨𝐫 𝐰𝐢𝐧)? 𝐃𝐫𝐨𝐩 𝐢𝐭 𝐢𝐧 𝐭𝐡𝐞 𝐜𝐨𝐦𝐦𝐞𝐧𝐭𝐬! #DocumentControl #WorkplaceOrganization #ProductivityHacks #FileManagement #TeamCollaboration #NoMoreChaos #VersionControl #EfficiencyWins #OfficeHacks #SmoothWorkflow

4

Every PMM team needs to do this now! Get access to the source code repo. Here is why: 1. Ask questions in Claude or Cursor 2. Uncover how the product works 3. Answer technical and high level questions quick 4. Format outputs by audience 5. Even draw flow diagrams Now there is never a new question you can’t answer in minutes. No need to ask a PM. No need to wait.

12

This is a huge update that anyone who cares about workload identity or agentic security should be paying attention to. Kong Mesh is the first and only service mesh to natively act as a SPIFFE identity issuer, to interoperate with an existing SPIRE deployment, or to federate between two. This vastly improves interoperability in hybrid and multi mesh deployments. Great work Kuma team! We'll be sharing more about how this can help solve for modern enterprise security challenges in a future post.

32

It's a big day at Honeycomb! We're announcing major advancements in Honeycomb Telemetry Pipeline that unlock a new era of observability—one without tradeoffs. 🔥 Over the past several years, conversations around observability have revolved around challenging tradeoffs: retention versus fidelity, availability versus speed—and always, the constant pressure of cost. With the rise of OpenTelemetry shifting telemetry ownership from vendors to engineering teams, it was no surprise to see telemetry pipelines quickly emerge as essential infrastructure. Yet—as standalone solutions—these pipelines reinforce divisions between the producers and consumes of telemetry data (but this time, more toxically, often within the same organization). Honeycomb is committed to a different approach: deeply integrating telemetry pipelines into the observability experience itself. ✨Enhance✨ is the first step toward this vision, eliminating the traditional tradeoffs in data management. Teams now retain easy, cost effective access to all their telemetry, even (especially! 💥) the bits they didn’t expect to matter. By aligning telemetry data management directly with data usage patterns, we're able to foster positive feedback loops across engineering teams and lay the groundwork for a more integrated, insightful, and collaborative future. Welcome to an era of true lossless observability. It's gonna be exciting. 🚀 Learn more from our press release: https://lnkd.in/dqgCZDyy

103

2 Comments

High availability is a core feature for hCaptcha. Here we pull back the curtain on some of our strategies, and why we were unaffected by this week's outages at Cloudflare and Google. https://lnkd.in/guG7hf2E

36

Site Reliability Engineering (SRE) isn’t just a discipline, it’s a strategic advantage. As systems grow more complex and customer expectations rise, SRE brings the mindset needed to keep organizations running reliably, efficiently, and at scale. SRE teams bridge the gap between development and operations by combining software engineering with a focus on resilience. They help organizations:  - Reduce downtime through proactive monitoring and automated remediation  - Improve performance by identifying bottlenecks before users ever feel them  - Scale safely with repeatable processes and infrastructure as code  - Accelerate innovation by allowing developers to ship faster without sacrificing stability  - Build trust because reliability is a critical part of the customer experience In a world where digital experiences define brand perception, SRE isn’t optional. It’s essential. Invest in reliability. Invest in SRE. #SiteReliabilityEngineering #SRE #DevOps #Reliability #TechLeadership #CloudEngineering #Scalability #Automation #Observability

4

1 Comment

Cloud cost uncertainty isn’t a fluke; it’s by design. Cloud providers profit from complexity: 💸 Granular billing 💸 Shifting discount programs 💸 Opaque pricing for AI workloads 💸 Exploding SaaS and shadow IT The result? Engineering and FinOps leaders are left scrambling to explain unpredictable cloud bills while innovation can’t slow down. Traditional dashboards and static budgets won’t save you. You need adaptive cloud cost management that embeds cost awareness into engineering workflows, detects anomalies early, and drives shared accountability. We break it all down in our latest post, including 5 steps to start leading through the chaos. Read it here: https://lnkd.in/ge4jadxr #FinOps #CloudCost #EngineeringLeadership #CloudComputing #AI #SaaS #Ternary

35

1 Comment

Just like Deepesh, for the past five years, I haven’t written a single line of code. Like many engineering leaders, my world shifted to strategy, org design, business alignment, and scaling teams. Coding became something I used to do. Then Claude Code was rolled out across our engineering org. We have an upcoming project to build an agent, and almost playfully, I thought: Why not? Let me ask Claude to write it. A few months ago, I had built something similar as a side project. It took real time and effort. This time? It was done in minutes. That was an eye-opener. Was the code production-ready? Maybe. Maybe not. But that wasn’t the point. The point was this: the constraints just changed. The friction between idea and implementation is collapsing. The cost of experimentation is approaching zero. I may not go back to “coding” in the traditional sense — and that’s okay. The world will still be full of strategy, architecture, and business conversations. But now, those conversations are backed by the ability to prototype, test, and explore at a speed that felt impossible not long ago. The real opportunity isn’t just writing code faster. It’s reimagining what we dare to build. We’re only getting started.

9

2 Comments

Urgent change may be required for publishers who use #Prebid -- Microsoft is shutting down the public Prebid Cache that's been hosted at adnxs.com since #AppNexus days. #Sincera data shows that this cache is still very widely deployed among web publishers. Pubs using it need to stand up their own cache (and update all their configs), use a 3rd-party vendor's cache, or work on storing ad markup in local cache in the browser. If you do nothing, a lot of video ads may fail to render starting in January. Just in time for the holidays!!

37

7 Comments