Live data from Hacker News

Incident with Pull Requests, Issues, Git Operations and API Requests

githubstatus.com

41–50 of 221 posts

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#44

Earlier quoted context omitted.

The UI of that page is so nice, should build a github competitor. The user profile / contributions and PR UX is pretty much the entire "hub" product since git is a fully separate offline app.

> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…

What really grinds my gears is how easy it is to get better designs out of LLMs. But if you don't ask, you get the default.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#45

is it me or ever since AI coding became the norm, there have been way more outages with otherwise reliable services? I get downtime on Supabase every few weeks. Even Cloudflare. And now Github

> is it me or

No, of course not.

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#46

GitHub is not agent scale. Multiple companies are trying to create new versioning primitives/architectures which can handle machine-level code generation - 1 commit per second per repo. It's like switching from horse buggies to automobiles, the whole worlds needs re-architecturing to handle the new load. The age of boutique hand-coding is being replaced by the age of industrial software factories.

> GitHub is not agent scale.

Is the scaling issue with git or github?

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#47

GitHub is not agent scale. Multiple companies are trying to create new versioning primitives/architectures which can handle machine-level code generation - 1 commit per second per repo. It's like switching from horse buggies to automobiles, the whole worlds needs re-architecturing to handle the new load. The age of boutique hand-coding is being replaced by the age of industrial software factories.

This seems odd to me. Why would you need to commit every second?

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#48

Earlier quoted context omitted.

The UI of that page is so nice, should build a github competitor. The user profile / contributions and PR UX is pretty much the entire "hub" product since git is a fully separate offline app.

> The UI of that page is so nice Is it? Seems a text description of "Make a website outlining 'How cooked GitHub' is with a modern style" to basically any LLM would produce exactly that UI and design, literally nothing of that design a human had any influence on, besides the ones selecting what training data the used LLMs was trained with. I think most of us who've tried using LLMs for web-design can recognize that s…

Compared to near unusable pages that large organizations produce, yes this page is highly effective at conveying information. Who cares how it was produced?

Re: Incident with Pull Requests, Issues, Git Operations and API Requests

#49
post #12

Earlier quoted context omitted.

Name one thing Microsoft didn't run into the ground post-acquisition

hey now, LinkedIn was terrible before Microsoft.

Java or Bedrock edition, and have you tried logging into your EntraID Microsoft Teams for Xbox account lately? Make sure to check the box to keep you logged in!
Post reply on HN