Koti Vellanki

If you signed up on Treatwise in the last 2-3 days, you might have noticed some technical issues completing your verification. We noticed all affected users and emailed them the next steps based on the specific issues each faced. Treatwise's IDP implementation is built on AWS Cognito. There are a couple of nuances Cognito doesn't handle out of the box, but we've augmented it with custom implementations — and going forward, you'll never face an issue past 30 minutes before we step in and help. As a health platform, trust isn't optional — it's the product. Every signup matters, every broken flow gets tracked, and every user gets a response. #startups #buildinpublic #ai #llm #saas #healthtech #innovation #technology

21

1 Comment

❓ Why Terraform alone cannot prevent cloud cost overruns Terraform gives teams confidence. But confidence isn’t cost control. Terraform tells you what will be deployed — not how much it will cost when traffic, scale, and reality hit. Two clean Terraform plans can differ massively in long-term spend. That’s why cloud bills spiral even in “well-managed” environments. Cost has to be visible before terraform apply — not discovered weeks later in invoices. This is a pattern we repeatedly see while building CrftInfrai. #Terraform #FinOps #CloudCost #DevOps #InfrastructureAsCode

4

1 Comment

-- Microsoft Layoffs Layoffs at the Top – A Sobering Industry Reminder The recent round of layoffs at Microsoft has sent ripples through the tech industry — not just for the scale, but for who was impacted. Among them was Ron Buckton, a respected engineer with 18 years at Microsoft, including a decade dedicated to the evolution of TypeScript — a foundational language for modern web development. His departure underscores a reality many professionals and hiring leaders must now confront: Tenure and impact no longer equate to job security. This is not about performance. It’s about the new structure of global tech: #AI is shifting priorities and #skill demands. Efficiency and margin pressure are driving reorganizations. Even high performers with deep institutional knowledge are being affected. What this means for us as professionals and hiring leaders: - Job security is no longer linear. Career stability now depends on agility, visibility, and continuous evolution. - Networks matter more than ever. Strong personal brands, public contributions, and community presence are no longer optional. - Companies must evolve how they recognize and retain technical excellence — before it's lost in reorgs. As hiring leaders, we must look beyond resumes and tenure — and as professionals, we must prepare for a world where stability is self-created. To those impacted: Your contributions do not go unnoticed. The market still values technical depth, integrity, and leadership. The best companies are watching, and many of us are hiring. Let’s stay connected. Let’s support our peers. And let’s build a future that values long-term impact, not just short-term alignment. #TechLayoffs #Microsoft #TypeScript #Hiring #Leadership #AI #EngineeringExcellence #CareerStrategy #OpenToWork #Future

42

🚨 AWS US-East-1 outage on Oct 20, 2025, hit hard: DynamoDB DNS issue downed 14+ services for hours, impacting Snapchat, Roblox, Venmo & more. 5th major US-East-1 outage in 5 yrs. AWS averages 2-4 big downtimes/yr. Cloud concentration risks exposed again. Is US-East-1 single point of failure?!!! 🛠️ #AWS #Cloud #Outage

3

💡 Lessons from the AWS DynamoDB Outage This week’s AWS outage — triggered by a DNS issue in US-EAST-1 that cascaded into DynamoDB and other core services — was a strong reminder of a simple truth: Even the most reliable platforms have failure modes. Many businesses across the globe experienced ripple effects. Some degraded gracefully. Others went dark. The difference came down to architecture resilience — and, more importantly, organizational readiness. A few leadership reflections: 🔹 Operational resilience is a leadership choice. Designing for failure isn’t only a technical decision. It’s about where we invest time, complexity, and cost before incidents happen. 🔹 Dependencies compound risk. We often celebrate velocity and abstraction in cloud architecture — until a core dependency like DynamoDB falters. Leaders need to routinely ask: “What’s our plan if this dependency fails at 2 a.m.?” 🔹 Communication beats perfection. In outages, your team’s clarity matters more than the system’s uptime. Teams that have practiced incident response — with clear ownership and psychological safety — recover faster. 🔹 Postmortems are gold, if we treat them that way. When AWS publishes their root cause analysis, resist the urge to just skim it. Map their failure pattern to your own systems. Every incident, even external, is a free rehearsal. We can’t eliminate outages. But we can choose how prepared, transparent, and adaptive our teams are when they arrive. The real test of reliability isn’t when things are working — it’s how we behave when they don’t. #Leadership #ReliabilityEngineering #AWS #DynamoDB #EngineeringManagement #IncidentResponse #SystemDesign

5