Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Days since last GitHub incident

github-incidents.pages.dev

Post reply on HN
Print view View original

111–120 of 142 posts

Re: Days since last GitHub incident

#111

Post by llbbdd »

colechristensen wrote: post #110
llbbdd wrote: post #83

Earlier quoted context omitted.

I can't say I'm not tempted looking at the Spark, I could probably save some cash on heating my house with that thing. Though yeah unless there's some good software already built around a similar LLM workflow I could use it'd probably be wasted on me, or spend its time desperately trying to pay for itself with crypto mining. Adding Claude to my rotation is starting to look like the option with the least amount of bui…

>Though yeah unless there's some good software already built around a similar LLM workflow I could use it'd probably be wasted on me, or spend its time desperately trying to pay for itself with crypto mining. A big part of my success using LLMs to build software is building the tools to use LLMs and the LLMs making that tool building easy (and possible ).

I tried this for a little while and couldn't really get passionate about it; I have too many other backlogged projects that I was eager to tear into with LLMs and I got impatient. That was a while ago though and the ROI for building my own tools has probably gotten a lot more attractive.

Re: Days since last GitHub incident

#112

Post by 000ooo000 »

landr0id wrote: post #82
IgorPartola wrote: post #55

Earlier quoted context omitted.

The Zig post has since been updated and the objectionable parts have been removed. I think we can put that part to rest.

I have no problem with their opinions but I don’t think it should have been said in a Foundation post. It may have been updated, but nobody is reading the update.

OK, so we keep banging on about it forever? Move on

Re: Days since last GitHub incident

#113

Post by pas »

tonymet wrote: post #92
TuxPowered wrote: post #88

It should always be at 0, because GitHub is unreachable over IPv6, which in 2025 should be considered an incident.

mobile adoption is high, desktop (residential and corporate) is still quite low. I'm a big advocate for github to add ipv6 support , but let's not pretend it's critical for their business.

just a few hours ago we found a pretty nice residential desktop use case for proper v6 (with prefix delegation), due to no need for NAT the old router (2013) became less of a bottleneck!

Re: Days since last GitHub incident

#116

Post by eleumik »

venturecruelty wrote: post #33
ZeroConcerns wrote: post #11

This is a bit... low-effort, isn't it? I'd at least expect a video of an exasperated Github user walking up to the '# days since the last GitHub incident' board, sliding out the '1' or '2' card, and replacing it with a '0'. I mean, that joke is as old as the universe (heck, in the brief period that I worked in an office, decades ago, I had a "# days since the last person asked a stupid question" sign to enact the exa…

I used to have a magic 8-ball that people could use when they wanted me to debug their code for them. I think it was broken, though; it kept saying "Outlook good". Must've been a Microsoft magic 8-ball.

you found the bad-magic-ball, looks like a standard magic-ball with genius inside but is not, the one that finds it works, not the genius..hmmm...but hey glass balls with LLM inside...christmas...wonderful idea

Re: Days since last GitHub incident

#117

Post by OptionOfT »

GitHub Actions is a good example of systems thrown together that at face value have something to offer until they get put under stress.

Just now I found:

    * a job that's > 1 month old, still running
    * another job that started 2 hours ago that had 0 output
    * a job that was marked as pending, yet I could rerun it
    * auto-merges that don't happen
    * pull requests show (1), click it, no pull requests visible
Makes me wonder in how many places state is stored, because there is some serious disconnect between them.

Re: Days since last GitHub incident

#118

Post by colechristensen »

llbbdd wrote: post #111
colechristensen wrote: post #110

Earlier quoted context omitted.

>Though yeah unless there's some good software already built around a similar LLM workflow I could use it'd probably be wasted on me, or spend its time desperately trying to pay for itself with crypto mining. A big part of my success using LLMs to build software is building the tools to use LLMs and the LLMs making that tool building easy (and possible ).

I tried this for a little while and couldn't really get passionate about it; I have too many other backlogged projects that I was eager to tear into with LLMs and I got impatient. That was a while ago though and the ROI for building my own tools has probably gotten a lot more attractive.

I started building my own tool set because I was doing too many projects with LLMs and getting frustrated by a very real need for organization and tooling to get repetitive meaningless tasks out of the way and to get all of my projects organized so I could see what was going on.

Re: Days since last GitHub incident

#119

Post by esseph »

landr0id wrote: post #82
IgorPartola wrote: post #55

Earlier quoted context omitted.

The Zig post has since been updated and the objectionable parts have been removed. I think we can put that part to rest.

I have no problem with their opinions but I don’t think it should have been said in a Foundation post. It may have been updated, but nobody is reading the update.

I just did and wouldn't have know about it if it hadn't been talked about here.

Re: Days since last GitHub incident

#120

Post by llbbdd »

colechristensen wrote: post #118
llbbdd wrote: post #111

Earlier quoted context omitted.

I tried this for a little while and couldn't really get passionate about it; I have too many other backlogged projects that I was eager to tear into with LLMs and I got impatient. That was a while ago though and the ROI for building my own tools has probably gotten a lot more attractive.

I started building my own tool set because I was doing too many projects with LLMs and getting frustrated by a very real need for organization and tooling to get repetitive meaningless tasks out of the way and to get all of my projects organized so I could see what was going on.

I'm convinced. :) I've got some time to kill in transit later today, maybe time to think about my setup a bit.
Post reply on HN