dotScale 2014 - Robert Kennedy - Life in the Trenches of healthcare.gov
dotconferences3 HN recommenders · recommended in 2 months, 2014-2015
13K views · 12 years ago · talk · evergreen
A dotScale 2014 talk by Robert Kennedy, a former healthcare.gov SRE who later worked at Google, about the engineering effort to rescue the troubled site. It explains the technical and organizational problems behind the failed launch.
HN recommends it as an entertaining first-hand engineer account of what went wrong with healthcare.gov and how it was fixed, including that no one owned the whole site.
28:14Mikey Dickerson Velocity NY 2014 Keynote: "One Year After healthcare.gov..."
O'Reilly
19K views • 12 years ago
25:18dotScale 2015 - John Graham-Cumming - I got 10 trillion problems, but logging ain't one
dotconferences
7K views • 11 years ago
5:28Inside a Google data center
Google Workspace
22.6M views • 11 years ago
28:21Velocity 2012: Richard Cook, "How Complex Systems Fail"
O'Reilly
60K views • 14 years ago
54:51Keynote - Karen Sandler
Linux.conf.au 2012 -- Ballarat, Australia
20K views • 14 years ago
1:14:19NYC Tech Talk Series: How Google Backs Up the Internet
Google TechTalks
41K views • 12 years ago
1:33:27AWS re:Invent 2016: Tuesday Night Live with James Hamilton
Amazon Web Services
133K views • 9 years ago
28:31Velocity 2010: James Hamilton, "Datacenter Infrastructure Innovation"
O'Reilly
9K views • 16 years ago
1:03:48Greg Young - CQRS and Event Sourcing - Code on the Beach 2014
Code on the Beach
170K views • 12 years ago
48:36Matt Might - Winning the War on Error Solving the Halting Problem and Curing Cancer
Curry On!
9K views • 9 years ago
1:00:56RailsConf 09: Robert Martin, "What Killed Smalltalk Could K
O'Reilly
87K views • 17 years ago
52:41Seattle Conference on Scalability: YouTube Scalability
Google TechTalks
30K views • 19 years ago
15:05Steve Yegge, "What Would You Do With Your Own Google?" - OSCON Data 2011
O'Reilly
66K views • 15 years ago
51:27Google I/O 2012 - Go Concurrency Patterns
Google for Developers
894K views • 14 years ago
14:26OSCON 2011: Karen Sandler
O'Reilly
15K views • 15 years ago
28:11Why Everyone Is Talking About Data Centers In Space
Scott Manley
408K views • 10 months ago
26:33dotJS 2012 - Fat - What Is Open Source & Why Do I Feel So Guilty?
dotconferences
73K views • 13 years ago
1:22:45Building Software Systems At Google and Lessons Learned
Stanford
257K views • 15 years ago
19:10Velocity NY 2013: Richard Cook, "Resilience In Complex Adaptive Systems"
O'Reilly
47K views • 13 years ago
1:20:29Stanford Seminar - Google's Steve Yegge on GROK
Stanford Online
30K views • 14 years ago
5 comments from Hacker News
You can watch a very entertaining talk from one of the Google engineers who went to fix the website at the time: ▶ this video
There was a talk at dotScale about the healthcare.gov website and what went bad on a technical level: ▶ this video
Worth watching: ▶ this video I like the way the presenter sums it up...it seems like each contractor was responsible for their own little piece of the stack, and nobody was actually responsible for delivering a website . That should've been the gating criteria.
I was part of the "tech surge" brought in to help patch up healthcare.gov in December. The GAO report gives a decent idea of what went wrong in 2010-2013 from a high-level contracting and policy perspective, but it doesn't really give much technical detail or describe what was broken about the organization, software architecture, and culture. A couple of my colleagues have given talks on healthcare.gov from the perspective of the engineers who worked around the clock to help get the site running again: link ▶ this video A small team is also re-writing the site, starting with the most troublesome components for the next open enrollment period. Wired covered some of what is going on here: link If any of you out there want to help, please email jobs@hcgov.us!
I think it has to do mostly with the image they want to have in the developer community. Plus, watching a HD video shot in a Theater like ours is arguably more enjoyable and impactful than something shot in a studio. You can check this as an example: ▶ this video