3 ms·
Scaling can take time but they've had at least a year to prepare. It's not like any demand increase they've seen was overnight... At most normal companies you
by kypro 2mo ago
Scaling can take time but they've had at least a year to prepare. It's not like any demand increase they've seen was overnight...
At most normal companies you monitor your systems and address potential bottlenecks before they reach a tipping point. And generally you want enough headroom that a sudden 2-3x increase in demand wouldn't take out the service.
Either Github's technical leadership/talent is completely out of their depth (seems unlikely), or they're not hiring enough engineers to work on these capacity issues.
- unknownfuture 2mo ago> Either Github's technical leadership/talent is completely out of their depth (seems unlikely), or they're not hiring enough engineers to work on these capacity issues. Regarding their leadership, I'd argue the latter implies the former. So yeah I'd say they're out of their depth.
- dannyw 2mo agoMore likely, as seen in a lot of companies, perhaps infra teams got whittled down (or frozen HC, less than BAU, etc) with resources reallocated to AI org units.
- lkjdsklf 2mo agoHardware resources are also allocated to AI uses so you can't scale out that way anymore.
- peezd 2mo agoI got the impression from a previous thread that the continual issues were largely driven by the required move to Azure, and underlying Azure stability
- m4rtink 2mo agoRather, lack of Azure stability. ;-)