Has anyone had issues with YouTube lately? I know YouTube went down about two weeks ago, but there still seems to be issue. Like if you pause a video and come back after some time, the video will play for a bit, and then go to black screen, although last week it was the video not available. And once we refresh the page, it loses track of how far along you are on the video.

Where are you from? Virginia, USA Tell us something about you? I'm a developer with mainly backend experience. Recently, I picked up Java What do you hope to achieve here? I hope to learn the latest trending concepts like AWS, and perhaps become more Full stack. And being able to ask any questions I have while coding Which platform brought you here? Youtube

In progress. Currently at Streams section

1. Collaboration Tools (Linear, MS Teams, Slack, Zoom, Confluence) 2. Programming Languages (Java, JavaScript, Python, C#, Go) 3. API Development (REST, gRPC, Security, Encryption, Signing, Protocols) 4. Web Services (Nginx, Tomcat) 5. Cloud (AWS, Azure, Kubernetes) 6. Authentication (Tokens, OAuth2.0, JWT, Cookies) 7. Testing (TDD, Unit Test, E2E Test, Performance Testing) 8. Databases (Relational: MySQL, PostgreSQL; Non-Relational: MongoDB, Cassandra, Redis) 9. CI/CD (Jenkins, GitHub Actions, CircleCI, GitLab) 10. System DesignProtocols: TCP, UDP, DNS, Caching, Content Delivery Networks, Microservices Messaging, Architecture, Load Balancing, Sharding, Distributed Systems, Database Replication 11. Data Structures and Algorithms (Big O Notation, Recursion, Sorting, Trees, Graphs) 12. Design Patterns (Factory, Dependency Injection, Proxy, Observer, Facade) 13. AI Tools (Claude, ChatGPT, Prompt Engineering, Cursor Where are you in your journey?

What was the most broken part of your post-mortem process? Not the incident itself, the aftermath.For me, the worst part is always the "How did we miss this in staging?" question. It's never a simple answer, and trying to explain environmental drift or non-deterministic race conditions to a VP who just wants a "yes/no" feels like a losing battle. I end up writing a doc that's half technical narrative, half political damage control, and neither half is actually useful the next time something breaks. Curious whether this is universal or just a me problem. Maybe your team has actually figured this out. I genuinely want to know if anyone has a process that doesn't feel like reconstruction work after the fact.