[tedivm]

It really has been remarkable watching GitHub just crumble as an organization. There's a lot of discussion about why: the switch from being independent to being part of Microsoft, having resources pushed to Copilot instead of core service, the organization structure itself, a reliance on vibe coding, etc etc.

Regardless of the reason, it's undeniable that GitHub is facing some serious issues. The unofficial status page[1] tells a horrifying story.

I would absolutely love to get some insider perspective on this (if only to learn how to prevent it from happening anywhere I work), but I think it's clear to anyone who has been paying any attention that GitHub is a sinking ship and the only reason people haven't abandoned it already is inertia. Considering how much else is changing in software right now I don't think inertia is enough to sustain a company.

1. https://mrshu.github.io/github-statuses/

[_doctor_love]

> insider perspective on this

I do not work at MSFT but I don't feel that I need insider perspective to understand what's going on. GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters. Everything becomes the numbers game.

Microsoft, Oracle, VMware, CA (where software goes to die), Salesforce, the list goes on. Every once in a great while there's a good M&A team that doesn't fuck it up but that's sadly rare.

[bsimpson]

I feel like MS went out of its way to make a point that GitHub and NPM would be independent orgs that no longer had to worry about making keep-the-lights-on money. It was positioned as a benevolent acquisition for the good of the development community.

As so often happens, that didn't last long.

Nest was originally independent. Didn't take long for it to merge with the Google Home brand.

I'm sure there are countless other examples.

[AYBABTME]

The problem IMO is that they filled GitHub with Microsoft folks who just don't have the engineering self-sufficient hacker culture that is required to balance the "attraction park" vibe that GitHub paired it with. So now it's just an attraction park for Microsoft employees to go and do silly work with teams of 100 that should have been done by a skilled team of 5 hackers.

I was there for a couple years after the acquisition and just couldn't stand seeing it. I felt I was becoming useless working in a mad house that was becoming more maddening everyday. And MSFT just keeps replacing leadership with more and more disconnected people who just don't get it, who just never used GitHub like the OG users did. Two years ago I interviewed again for my old team, largely out of curiosity, and the Microsoft engineering manager asked me some brain teaser question as my interview. The disconnect is just too large.

They don't take GitHub seriously. It's a toy to MSFT and vibes matter more than the product itself. And they hire for it using MSFT drone logic, fill it with people hired and profiled to be MSFT-lifers, and these two things don't mix.

Sorry I don't have anything great to say. And of course, many of these MSFT folks were actually damn good, but they were swimming in a sea of MSFT drone.

[_doctor_love]

> would be independent orgs that no longer had to worry about making keep-the-lights-on money

It is honestly so shameful that we keep falling for this gambit. It is nothing more than a rank "but this time is different!"

Economics is what drives things. It is what drives things in households and it is what drives things in companies.

Unless times are truly great or the company is truly forward-looking, promises of freedom and independence from the business cycle is just an empty promise of creating a research lab.

[jitl]

What do you mean "we keep falling for it"? I remember after the acquisition there were tons of projects that left for Gitlab or other forges on principle of boycotting Microsoft. And for the many who stayed on Github, we still got about 6 years of pretty great free services before reliability really started to decline.

And its not like Github's load stayed linear over the last 8 years since the acquisition. Repo creation and pushes went exponential about 2 years ago with the AI boom, so even with fantastic execution I think they'd still be struggling hosting the ever expanding archive of all code in the world.

[layer8]

I remember discussions at the time where people predicted that this would certainly happen. If people “keep falling” for it, it’s not the same people. And Microsoft certainly wasn’t (and isn’t) a company you’d trust for such statements.

[hnlmorg]

Yet some people did trust them for it.

But you’re right that it probably wasn’t the same people that got burned by 90s Microsoft.

[bsimpson]

Satya got his own line of "maybe Microsoft's not evil anymore" press cycles out of it.

[bonoboTP]

This Disney brain of the Americans is what the problem is. It's not good guys and evil guys. It's money. Money and power have mechanisms. Pinky promises, benevolence etc. don't mean anything in capitalist business. It doesn't mean it has to be all thrown out the window. It can provide a service for a price, you can take it. Without being invested emotionally, without brand loyalty. That's dummy stuff. Businesses are not charities, and even charities are often quite businesslike. Unlearn naivety, read literature, human culture has known about the effects and incentives around money and power, petty and grand, for a long time.

[pdimitar]

Who is "we", exactly?

Neither me nor dozens of my acquaintances fell for it. 100% of us said "GitHub is toast, it's just a matter of time". And we and many others were right.

Your "we" is misplaced.

[hansvm]

> It is honestly so shameful that we keep falling for this gambit.

I'm not sure who "we" is in this story, but the _most_ optimistic of my peers pointed to typical MS projects of that scale having a little proper investment in interesting features and also taking at least a couple years to fail. HN sentiment wasn't positive either. The 99th percentile in favor of MS were fine with it, but the 90th percentile recognized the M&A for what it was, especially as specific features started showing their colours.

Lest this come across as a drive-by insult, I'm actually very curious who "we" is. Humanity is a very, very broad spectrum, and my intuition often doesn't appropriately capture the divers backgrounds of real people, despite spending large amounts of time with (usually from working alongside) deck-hands, captains, sanitation workers, bankers, pilots, jackhammer operators, semi drivers, farmers, programmers, mathematicians, and a host of other people. The gap I'm seeing is likely in my understanding (rather than, e.g., the post being mal-formed), so I'd like to correct that.

[jarjoura]

GitHub had no reason to sell to Microsoft, they could have remained the bootstrapped company they started as, and rode the SaaS boom, since they were profitable on day 1. Seems a bit unfair to blame Microsoft though, because it was the founders who decided they wanted that sweet VC funding and Andreessen was happy to pay out.

Not sure if it mattered after that but they had that weird Tom Preston-Werner scandal that got him fired. Since he was the CTO, I kind of suspect that sent them on a collision course with needing to exit the VC round and Microsoft paid out.

[Andrex]

Would definitely read a book about this.

[dijit]

> I feel like MS went out of its way to make a point that GitHub and NPM would be independent orgs that no longer had to worry about making keep-the-lights-on money. It was positioned as a benevolent acquisition for the good of the development community.

Sorry, why the hell would any company do this? Goodwill is measured by MBA's in pennies and they paid *billions*.

This is like that time Google acquired the .dev domain "to reserve it for developers" but then ended up selling it- like everyone said they would.

You have got to be absurdly naive to believe that Microsoft does altruistic things, if there's no direct (or indirect) business they're not doing it: they are famously not a charity.

They have to be the richest men on the planet, retire, and then they'll do some charity.. perhaps because they feel guilty about what they did on an island or something.

[hnlmorg]

This happens with almost every acquisition from Red Hat to WhatsApp.

If companies actually meant it then they’d sponsor these projects instead of buying them. The reason they choose to buy is so that they can make decisions about the direction of that project. If not immediately, then at least at some point in the future.

[delfinom]

GitHub was independent, and then AI happened.

All long term business goodwill and reputation is simply there to burn to keep the bubble going.

[thayne]

> I feel like MS went out of its way to make a point that GitHub and NPM would be independent orgs that no longer had to worry about making keep-the-lights-on money

A lot of companies say that when they acquire another, and it might be true for a few years, it might even be the actual intention of the people involved in making the acquisition, but it usually doesn't last.

[wunderlotus]

> It was positioned as a benevolent acquisition for the good of the development community. call me a skeptic, but can (and has) such a model existed in a capitalist system?

[tardedmeme]

It has never existed. Everything a business does is for power and profit, including the times when they pretend they aren't doing things for power and profit.

[wunderlotus]

* I quoted wrong. Sorry, still new here

[thinkingtoilet]

This is a general observation, no hard data, but I find there seems to be a wall at 2 years after an acquisition. By 2 years a lot of the best talent leave the company entirely or go somewhere else in the company. Things can cruise along just fine for a bit, but as the institutional knowledge slowly leaves it gets worse and worse. Couple that with the bureaucracy and insanity of a global mega-corporation, the quality fades slowly at first, then it picks up.

[_doctor_love]

> I find there seems to be a wall at 2 years after an acquisition.

It's called a vesting schedule. ;)

What I've seen is that usually the founders and heavy hitters from the original company are very BS-averse and basically just stay around to collect their money and then jet for a situation that doesn't suck.

For the rest of the gang, it tends to bifurcate: some folks stay at the big company indefinitely after the acquisition because while they can see the suck, nowhere else pays as well or is as cushy (I know people who have been thinking about leaving for 12 years). Still others excel at big company work and make a happy career out of it for a while but don't stay forever.

[bonoboTP]

This is the flipside of MBA-brain. Treating people as replaceable equivalent cogs in a machine, thinking that the company itself, as an abstraction, is where value lies, when it lies just as much in the context and nurishing environment. You can't simply move a company from one place to another like a Lego brick and expect it to go on functioning as before, not as long as people have freedom to leave.

[znpy]

> but as the institutional knowledge slowly leaves

I’d like to offer a different perspective: the “institutional knowledge” often (but not always, of course) are the old timers that have been gatekeeping knowledge in order to make themselves irreplaceable.

I’ve seen this a couple of times, even in faang-sized companies.

I’m not sure this is the case of GitHub though.

It might be due to lower quality code spit out by some llm, reviewed by some llm and shipped to production by some llm-generated pipeline.

Also, wasn’t github pushed to move to azure?

Anyways, it surely is a strong signal of engineering culture degrading.

[ngrilly]

I'm afraid this is a form of reversion to the mean. Successful startups are made of exceptional people: the founders, the initial investors, the first employees, the first clients. But when they get acquired by much larger companies, they are necessarily diluted in pool of people that are more "normal", less exceptional. This includes the customer base that is more "normal" as well. Slowly but surely, the extraordinary product/service the startup has been developing reverts to the mean. This is quite sad, because it feels inevitable. I'd like to know how to avoid it.

[jzb]

“I'd like to know how to avoid it.”

To paraphrase a popular quote from IBM: “Executives and MBAs can never be held accountable: therefore executives and MBAs must not be allowed to make decisions.”

Slightly less flippant: The only way to stop this is to stop letting companies like MSFT gobble up smaller companies. That doesn’t seem likely in the near future, though. Once the Borg assimilate something, it’s just a matter of time before it’s digested and drained of value.

[tardedmeme]

The process is necessary for both sides. Acquisition by large companies is the primary way that people get rewarded for building good things. If you take it away, there won't be many startups left - all new developments will come from the big companies that can afford them, and only the types of developments those companies' managers want to make.

[jzb]

It's only "necessary" if one accepts that the current way is the only way.

I'm not really sure what the point of encouraging new development is if the end result is "big company scoops it up and makes it shitty, but people get to enjoy it for a few brief moments before that happens."

[hilariously]

That could be A problem, but to me THE problem is that the larger companies buy these smaller companies for resource extraction, not to make the product better.

In this frame you can see that making the product worse (paying less for its upkeep) and raising prices are just two sides of the same coin - extract more resources.

Almost no big company has any reason to shepherd a product in a way that's beneficial to its users because they have so much momentum that even changing their approach either costs too much money or those in power are too insulated from the outcomes (fix it for me or I will fire you while I continue to make bad choices and under fund the product).

[bonoboTP]

It's not inevitable that the founders have to sell to big tech. They wanted money more than the excellence of the craft. They got the money, the company got to grow and made way more profit than when it was small scale but excellent. The wheel keeps turning.

[andruby]

There might be a few (debatable) counter-examples: 37 signals, balsamiq, zoho?

Afaik they never took any (serious) VC money.

[ngrilly]

I was referring to the case where the founders and investors sell the startup to larger company. Of course, if they don't sell, and the company stays founder-led, the outcome is often better. I didn't know Zoho never took (serious) VC money.

[shaky-carrousel]

I use only self hosted free software. Admittedly it's not for everyone. But solves the issue for me.

[kps]

> CA (where software goes to die)

CA got bought (ironically) by Broadcom 8 years ago, so now Broadcom is where software goes to die.

[theappsecguy]

Slack has suffered the same thing under Salesforce.

[worldsavior]

Big companies usually buy other small companies for their users, once the users move to their platform, things change.

[slopinthebag]

It's just beancounters doing what they do best, counting beans and screwing up what was previously alright.

[bonoboTP]

It's very profitable in the short term, and later they can just move on elsewhere and do it to another company. It's not mismanagement at all, it's a solid strategy from the external point of view.

[HumblyTossed]

> Everything becomes the numbers game.

Death by spreadsheet. Happens to everything.

[superxpro12]

Hey, you leave Creative Assembly out of this!

[mvkel]

> GitHub is being managed the way other services get managed once they're bought by big companies. Initially fine, then starts to decline, then eventually craters

Can you explain what you mean by this? Like what does "fine" mean? What, specifically in the management, is the "decline"? What does "craters" mean?

[fabiensanglard]

Wow. According to the current metric (87.25% uptime), github suffers a partial outage 3h/day.

https://onlineornot.com/uptime-calculator/87.25

[gen220]

In their defense, they dramatically "over"-report sev-2/3's (things like, avatar urls are not loading in saudi arabia), which makes their cumulative uptime look much worse than it is.

If you filter for major/critical outages, their uptime of core services in trailing 12 months all have two 9's.

https://isgithubcooked.com/?severities=major.critical

Also, a huge part of their cumulatively-bad availability story is copilot, which is a functionality (LLM inference) that most organizations have struggled to get two 9's of availability in for the last 9 months.

[simplyluke]

As someone who relies on it for all of my workflows at a normal job, core functionality issues result in me not being able to get work done on at least a weekly basis reliably at this point, and it's been that way for months.

The things aren't profile pictures not loading in saudi, they're botching merge jobs, git/api operations being down, pull requests not loading, etc. And that's on top of the plethora of UI bugs that have been pervasive for years that aren't blocking functionality.

[imglorp]

This. I feel like there should be a developer uptime index that measures these things that we use every work hour.

And it should not depend on their status page which seems to take a while to catch up when there's an actual outage.

[gen220]

https://isgithubcooked.com/?services=api-requests.actions.gi...

You can pick whichever services you feel fall into this category in the top.

For the bundle I chose, there have only been 3 totally clean weeks so far in 2026 :/

[fnordpiglet]

Two 9’s? You have to work pretty hard to do that badly. That’s like bragging you graduated with a C average from Harvard after your father endowed a chair to get you in.

Given GitHub has become a utility service globally this should be frankly worrisome to everyone let alone the developer community actively using it. It’s intertwined into many things now beyond simply source code hosting and PRs. And I am surprised GitHub leadership is ok with the state of things. Having worked at a lot of 5-6 9’s shops, this would have been all hands on deck, all roadmaps paused, figure it out or perish sorts of stuff.

[gen220]

Oh yea I'm not trying to defend it as amazing or tolerable, just clarifying the actual benchmark/reality of their performance!

I think at least three 9's would be the baseline. But I'm also sympathetic that they had a *post-exit* scaling of write volume of like, idk, 1000x???

Very few orgs would survive that kind of scale and retain three 9's.

[tardedmeme]

We don't have to let it be a utility service. It's not like the power and water to your house where laying new pipes is a monumental and stupid effort. $3 per month can get you a VPS to run your git hosting on - if you even need git hosting, and aren't just using GitHub because it's there.

[rightsideworry]

That is a much more reasonable look, I am glad you alleviated our wor-

Why is the graph more dense on the right side?

[zuzuen_1]

Wait, this is insane! And the method they use to classify an outage seems solid as well. Imagine being a Github dev working in this environment.

[yetihehe]

Some years ago I wondered how long will it take them to go they way sourceforge went. Once you grow too much without a proper leader, you will fall :(.

[kivle]

Sourceforge died in a very different way though. Bundling spyware/crapware in install packages for open source software was a serious breach of trust, and was pretty much the direct reason for mass migration to Github. Github is failing on the technical side, but they at least mostly have their brand value intact. I think it will still take quite a lot for a mass migration of the same scale to happen.

[fnordpiglet]

Microsoft specializes in taking successful products and pumping them full of malware, spyware, bloatware, and adware once they have a critical mass of users. It is often preceded by quality dropping significantly due to under investment and McKinsey being brought in to find a way to prop up declining revenues - of course the answer is never to invest in making it a superior product again, but monetization strategies.

[janalsncm]

Mostly, but they were injecting ads into PRs if I recall.

[pathartl]

Comparing GitHub and SourceForge as if they were cut from the same cloth is laughable to me. SF has always been a wretched hive of ads and dark patterns.

[SwellJoe]

Not always, but it was so long ago that it became that, younger folks could be forgiven for thinking so.

[xstas1]

I do remember early SourceForge. It remember it as very clean, simple and reliable, and popular.

[Steeeve]

Not popular. Core. It was the trusted place for open source software. Then it was ads. Then the day they bundled there was a MASS exodus. And the 14 people who ran their own source code interfaces scoffed and said "see. I told you." And we all said "yup" - we knew something would happen one day, but that was a worst-case-scenario that few thought was even a remote possibility.

[bsder]

> And the 14 people who ran their own source code interfaces scoffed and said "see. I told you." And we all said "yup" - we knew something would happen one day, but that was a worst-case-scenario that few thought was even a remote possibility.

And nobody learned their lesson and they all piled over to the next centralized system that offered "FREE!".

And so it goes.

[pathartl]

Idk, I'm in my mid 30's and I've never had a moment where I've been glad to see something on SourceForge.

[SwellJoe]

So you were ~10 years old. I'll assume not a heavy user of Open Source software, at that time.

Edit: 2001, I see one (1) banner ad, and that ad was seemingly for an OSDN (Open Source Developer Network) conference. https://web.archive.org/web/20010517002942/http://sourceforg...

Given SourceForge only hosted Open Source software, and had no source of revenue beyond ads and sponsors for quite a long time, AFAIR, I think they get a pass on a banner ad.

[tom_]

For whatever it's worth, which is probably not much, I'm in my late 40s and I never really liked sourceforge either. Too many clicks to do anything (still true), and I didn't like cvs (also still true, but thankfully now irrelevant).

(My SF account dates from June 2004. I expect I was thinking about using it as version control for a FOSS project I was working on at the time, though I don't know why, as it seems SF didn't support svn until 2005. Maybe I couldn't find any better options? The pre-GitHub ecosystem was pretty bad! But, luckily, I ended up not having time for any FOSS stuff from about autumn 2004, so: problem solved. And when I next looked, in early 2010, everything seemed to be git+github, and all the better for it.)

[SwellJoe]

CVS was the best option when SourceForge began, and Subversion was barely an improvement. SourceForce was critical to the growth of Open Source and Free Software in the 00s. Projects no longer needed to maintain their own revision control server, file server, forum, issue tracker, etc. SF.net wasn't great compared to any of the current generation of hosting services. And, most Open Source projects were in an uncomfortable state of looking around for alternatives by the time Github arrived in 2008, because it was slow to adopt newer technologies and was running on a skeleton crew. Most of my projects had their own forums/issue trackers, and were self-hosting git, by then. Ads stopped being a usable revenue strategy, so SF.net stopped being able to keep up with what developers wanted.

But, it had a few years where every OSS developer I knew had nothing but positive feelings toward SourceForge. It gave one of the projects I work on thousands of dollars worth of transit over the years. It's hard for folks who've only ever worked on an "everything for small developers is a loss leader" internet to understand that we used to pay for and manage our own servers. I had a $200/month bill for just my Open Source projects on a couple of colocated servers.

Yes, SourceForge went through a lot of shitty stuff. The overtly hostile stuff (adware inserted in OSS projects) happened after it changed hands. But, when the revenue of their original model dried up and they couldn't stay on top of new development (being slow to offer a good git experience was a fatal mistake).

Anyway, it's not great now (though it is now owned by seemingly decent folks, who haven't really been able to find a way to make it work), and it went through a period where it was a borderline criminal enterprise, but it started out as a genuinely helpful part of the OSS community.

[bigstrat2003]

Yeah you're too young. You need to be in your 40s (or older) to have been around in the open source community when Sourceforge was good.

[gurjeet]

(To quote a famous TV series... :-) Oh my sweet summer child

[bandrami]

Not always. Before dice bought them they didn't do the ads. I even remember early on when you had to submit a project for approval before you got a CVS repo.

[rstuart4133]

> SF has always been a wretched hive of ads and dark patterns.

No, as others have said it wasn't always that way. And more importantly it's not that way now. But yes, for a while there it was the epitome of enshittication. How that worked out is kinda hopeful in a way: it went broke, was bought out, and went back to being something usable again. In fact they added a lot of enhancements.

I know because I was one of the ones that went back to it. I didn't like having git being forced down my throat, and sourceforge was one of the few left that supports a whole pile of VCSs. I made my Makefiles [0] support it so I didn't need to deal with the UI, and ended up very happy.

Everyone wondered why I wasn't on github, and queried my sanity at the time. But I say not liking the git cli is perfectly sane. Now jj has come along that excuse has gone, but it was a good one at the time. "github sucks" has conveniently come along as a reason to stay on sourceforge.

Seriously, if you are considering ditching github, take a look at sourceforge. The current owners BizX deserve some reward for the time they've put into it, and their patience.

[0] https://sourceforge.net/p/http-proxy-tunnel/code/ci/default/...

[unclejuan]

> The unofficial status page[1] tells a horrifying story.

If it weren't bad enough, github often has issues when the unofficial status page doesn't report them, so the actual number is even worse.

[HumblyTossed]

Microslop only really cares about the enterprise customer. Those are slow to change, so once they're in github, they'll stay forever.

[jim33442]

Have those outages actually been blocking your work? Somehow I haven't even noticed, just seen complaints on HN. I'm not saying it's not real, just wondering where the gap is.

[sevenseacat]

A big part of my job is doing code reviews, and its very common that pages or diffs just don't load. Or PRs literally don't appear in the PR list, even though they exist. It's a daily occurrence to play the 'is my internet down or is GitHub just being shit again?' game.

Oh, and don't forget the cases where the diff view sometimes misses some files for unknown reasons. Both in the 'new experience' and the 'legacy view'. You just can't trust it as much anymore.

[jim33442]

Oh so it's not even CI/CD, just showing PRs. That's awful.

[SCdF]

Yes, many times. Roughly once a week this year my team or an associated team can't ship changes because PRs, GitHub Actions, or some other associated mechanism is down.

[ZeWaka]

Mostly the Actions outages, but yes.

[jen20]

> I would absolutely love to get some insider perspective on this

I'm not an insider but would put good money on the migration to Azure being the root cause of the stability problems.

[tick_tock_tick]

All of that is revisionist history at best. GitHub was a pile a shit long before Microsoft bought it has everyone forgotten when it would be a coin-flip on any given day if the site was even functional?

GitHub was in the right place at the right time to be a success despite the fact it's a massively clobbered together mess.

[thom]

While I wouldn't necessarily phrase it this way, there is a chart going around social media that tries to imply that GitHub had basically 100% uptime right up until the MS acquisition. All it takes is either 1) having been there or 2) a cursory search of HN to know that this is a complete fabrication.

[pyb]

They are mostly blaming their shift to vibe coding for their problems. https://github.blog/news-insights/company-news/an-update-on-...

[valleyer]

Hm. I read that as saying that their users are writing more code with the assistance of LLMs, thus placing more stress on their systems. I do not read it as making any comment about their own practices.

[pyb]

Oh you're right, I misread. They're actually blaming their customer's vibe coding on their problems. I which case I call BS

[Klathmon]

In our internal metrics you can see a clear increase in PRs and CI runs in general that tracks with agentic coding adoption, and it's significant, so I absolutely buy that GitHub would be struggling to take the brunt of that without big changes

[jjayj]

But GitHub's postmortems are usually related to internal rollouts rather than traffic load

[thom]

A charitable view might be that changing which fingers you're using to plug the holes in the dike is a lot harder when the volume of water on the other side is increasing exponentially.

[dark-star]

> crumble as an organization

I think that is exaggerating things a bit... GitHub is alive and well, and they're hosting more and more projects each month. A few well-known projects leaving every now and then doesn't exactly spell doom for GitHub

[jbxntuehineoh]

literally zero nines of uptime lmao, do they win an award?

[tedivm]

Even if you go service by service you're talking about critical things like `git` operations (literally what they're named for) at a single nine, and stuff that's pretty basic like static web hosting as only two nines. They literally can't even keep static webpages up.

[bonoboTP]

So what? People have to unlearn this kind of brand loyalty. Companies are not people and not your friends. They are in the business of making money. We need to be more aloof and simply use their tools when useful and not get emotionally attached. Most of the managers and likely the devs had a good deal. Good money, and if it collapses, people still have a good resume line and can move on. And we users can also move on. There are plenty of other service providers of code hosting and CI/CD.

[s-y]

i feel like scaling is rarely brought into the conversation. It’s easy to hate on ms, especially with their AI slop narratives, but they did get a sudden and then ongoing influx of users that the system was not designed to handle. It’s the kiss of death and it’s not anything new in terms of product failure scenarios

[mday27]

wow, I knew it was bad but I was gaslighting myself a bit. 0 9's is crazy.