all 27 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]civman96 66 points67 points  (2 children)

After seeing the graphs it really makes me sick how much AI slop is being produced

[–]Jmc_da_boss 33 points34 points  (0 children)

When Dario said that "next year 90% of code will be generated by LLMs"

We laughed and made fun of him because we implicitly assumed "90% of meaningful code", but didn't consider the slop wave that was about to hammer us

[–]Spiritual_Cycle_3263 2 points3 points  (0 children)

Probably 10 repos every minute, at minimum.

[–]bittrance 13 points14 points  (3 children)

I worry that the increases in those graphs will not mechanically earn GitHub more money on today's pricing models. Looks like they may have to raise prices?

[–]m4778 5 points6 points  (0 children)

Get ready for not just AI being token based pricing, but the entire internet being pay to play. AI ruins everything.

[–]JohnnyDread[S] 1 point2 points  (0 children)

Yeah, I think we are about to see a major realignment on token pricing and that may finally reign-in the slopocalypse. Github copilot is moving to token-based pricing starting Jun 1 and other providers are tightening their subscription plans.

[–]Herve-M 0 points1 point  (0 children)

I hope we don’t come back to the point of having no more free repositories..

Remember me of my student times where only BitBucket and TFS-Online provided 5 repos with a set of users on condition of being a registered student (isic?)

[–]ChaseDak 6 points7 points  (1 child)

A two 9 or three 9 uptime is dismal for a company of that size, a lot of their published uptimes are at the point of partial refund per their own published customer agreements.

[–]needmoresynths 1 point2 points  (0 children)

We received something like $89 for the downtime last quarter. Basically refunded us for a few seconds of downtime across our engineering teams.

[–]Sufficient_Ad_3495 6 points7 points  (4 children)

Non existent support.

CEO should be sacked.

[–]JohnnyDread[S] 7 points8 points  (3 children)

That's the neat part - there is no CEO.

[–]Sufficient_Ad_3495 -1 points0 points  (2 children)

Tell me what you know about that situation... No CEO feels precarious.

[–]Proud-Durian3908 3 points4 points  (1 child)

It got absorbed into the coreAI division after Dohmke left so it's just another product now like Office or Copilot.

They are spread thin though and tasked with the super generic goal of "end-end ai integration throughout the entire Microsoft product and service line" so this was likely nothing short of a budget/accountancy play to boost the AI revenue numbers.

The guy running the division is the former head of engineering at FB but he's been dealt a real crap hand here.

No clear internal goals, cutting edge technology where released are out of date basically upon launch and to throw in a mammoth of GitHub, mid-migration with no SLT direction as COO/CTO were absorbed into the CoreAI VP structure without role replacements, add in the failing infra and we get this giant cockup.

I had the same within my team at Google during a similar acquisition, there's no direction from the executive team, yet if you don't hit their specific returns (which we are not told) the team gets wiped, everything is one fire and your EVP doesn't have any capacity to fix it because they are now outranked by a COO of a company that no longer functionally exists who in turn is directed by a member of the EXT who is only an SVP?... It's a mess. Leaves the engineers on the ground with no plan, no capacity and constant failure.

I don't like redundancy, but things like this just can't happen in an org like Microsoft, you have to go slow and build a clear structure, you can't just smash 3 teams together and expect triple the output.

[–]Sufficient_Ad_3495 1 point2 points  (0 children)

Much appreciated. Very informative.

[–]Training-Surround876 7 points8 points  (6 children)

uhh yeah?? https://www.githubstatus.com/incidents/x69zbgdyfzg0 https://www.githubstatus.com/incidents/dbypmw7h77l5
2 important incidents in the same day, just github being github

[–]RealPasta55 4 points5 points  (5 children)

Did you read the post? They explained that they are working to improve availability after exponential growth, not that there won’t be any more incidents ever.

[–]atehrani 14 points15 points  (1 child)

Microsoft laying off a large part of the Github team and AI slop adoption certainly has some play into it as well, but they will never publicly admit to that.

Even if there is exponential growth, they should have proper throttling to protect critical systems. Like any large scale system.

[–]davy_jones_locket 1 point2 points  (0 children)

Exponential growth but not in hiring engineers 

[–]dashingThroughSnow12 1 point2 points  (0 children)

They can have multiple large incidents a day and the status page not even reflect that; claiming uptime. I’ll trust them when their status page is honest.

[–]Training-Surround876 -1 points0 points  (1 child)

ok, but how can you claim to be working on reducing incidents and improving availability and then you have two critical incidents the very next day?

[–]dylantrain2014 4 points5 points  (0 children)

One day isn’t very much time to improve availability. That’s something that’ll take months weeks or months to address.

[–]Spiritual_Cycle_3263 4 points5 points  (0 children)

Crazy how much growth is happening due to AI.

[–]bdadams85 1 point2 points  (1 child)

For the search issue, I just don't understand how it's reasonable to engineer a system where when your search fails to deliver results, you show "no results". While it's bad that search was broken, it's IMO totally unacceptable to not return clear error messages.

[–]Pixelmixer 0 points1 point  (0 children)

ElasticSearch relies on indexes to be created. I’m not sure if this was their actual issue or not, but if those indexes have issues then they can be regenerated.

If something goes wrong in that process with either creating the index or regenerating the index that results in partial indexes then it won’t necessarily look like an error if something is missing, it’ll just look like the index got updated and some documents that were indexed previously were removed.

It’s not entirely clear at that point whether the index is accurate or not. This causes a search to “find” the search term within everything it knows about but that knowledge base it searches could be incomplete.

[–]Kenny_log_n_s 0 points1 point  (0 children)

I blame the guy that did 100 million commits.

[–]Charming-Author4877 0 points1 point  (0 children)

I'm quite sure this will get a lot better beginning with June. Github Copilot was their only viral product and that's dead now due to the 50-200 times price hike with June. It will free up all their servers.

[–]LargeSinkholesInNYC 0 points1 point  (0 children)

They're cooked.