Comment by fridder 4 days ago I think the reliability struggles of Github may have helped with this 3 comments fridder Reply saghm 4 days ago I can't help but wonder if the causation is backwards here and the millions of lines of slop had more to do with the Github struggles than the reverse fridder 4 days ago In reality yes, and probably a complex mixture of things. Dedicated time and resources being siphoned off for Llm work, etc Chu4eeno 4 days ago I also think starting to migrate to Azure just as their traffic/usage exploded from LLM use (plus I assume merging a bunch of poorly written early-gen LLM code as early adopter dog fooding) was poor planning by Github/Microsoft.
saghm 4 days ago I can't help but wonder if the causation is backwards here and the millions of lines of slop had more to do with the Github struggles than the reverse fridder 4 days ago In reality yes, and probably a complex mixture of things. Dedicated time and resources being siphoned off for Llm work, etc Chu4eeno 4 days ago I also think starting to migrate to Azure just as their traffic/usage exploded from LLM use (plus I assume merging a bunch of poorly written early-gen LLM code as early adopter dog fooding) was poor planning by Github/Microsoft.
fridder 4 days ago In reality yes, and probably a complex mixture of things. Dedicated time and resources being siphoned off for Llm work, etc Chu4eeno 4 days ago I also think starting to migrate to Azure just as their traffic/usage exploded from LLM use (plus I assume merging a bunch of poorly written early-gen LLM code as early adopter dog fooding) was poor planning by Github/Microsoft.
Chu4eeno 4 days ago I also think starting to migrate to Azure just as their traffic/usage exploded from LLM use (plus I assume merging a bunch of poorly written early-gen LLM code as early adopter dog fooding) was poor planning by Github/Microsoft.
I can't help but wonder if the causation is backwards here and the millions of lines of slop had more to do with the Github struggles than the reverse
In reality yes, and probably a complex mixture of things. Dedicated time and resources being siphoned off for Llm work, etc
I also think starting to migrate to Azure just as their traffic/usage exploded from LLM use (plus I assume merging a bunch of poorly written early-gen LLM code as early adopter dog fooding) was poor planning by Github/Microsoft.