Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Blaming every downtime on "vibecoding, probably" is so weird and lazy. As if these places never had downtime previously
 help



Lazy maybe, but not weird at all. Probably true most of the time.

You have no evidence for that. You just wish it was AI's fault because you hate AI and hope it comes back to bite them.

Surely if you use LLMs to write code the evidence that they cause problems is all around you every day? Don’t you see it in every PR?

> Don’t you see it in every PR?

PRs without problems don't really grant any credit against those with problems. I see it it a fraction of PRs. Seeing it sometimes is enough to establish evidence.


No because I have competent co-workers

Indeed, given that there was a post this spring by ex-Microsoft employee on the poor state of Azure.

"The team had reached a point where it was too risky to make any code refactoring or engineering improvements. I submitted several bug fixes and refactoring, notably using smart pointers, but they were rejected for fear of breaking something."

https://news.ycombinator.com/item?id=47616242


Sure, those takes are mostly lazy (some of my comments here included TBH). Although I have very weird feeling, that current zeitgeist is about "coding is solved", etc and the same time we have evidence that didn't help much regarding boring thing such as reliability

Well reliability isn't coding, it's operations.

Trying to control the narrative this way by preemptively talking about vibecoding is so weird and lazy.

> You have to wait for Microsoft to find a competent employee who wasn't let go to try and fix what was broken by some inept leftover who was deluded enough to think that Copilot can do everything.

From the submitted blog post.


Right but according to some here AI is creating vast amounts of high quality code that should have given us 100% uptime in every service

Right?

As opposed to a pile of unmaintainable shit


Doesn't matter how good your code is you'll still have downtime. Operations is vastly more complex than just code

AI does what you ask of it, so, just like when humans wrote the code by hand, some will take time to carefully build systems to validate their work and others will do anything to get the job done as quickly and lazily as possible. It is all but certain that some people will have AIs producing good, reliable code, with others producing mountains of garbage.

And how are people (specially juniors) going to learn what's good code and what's bad without ever writing a line of code

In the olden days some never learned, but those that did tried things, failed, and then build systems to prevent making the same mistakes again.

I don't see what's different today. Some will never learn, but of those who do they'll try things, fail, and then build systems to prevent making those same mistakes again.

AI thrives within those systems.


MSFT stated that they went all in on AI and had a key metric of generating more than a million LOC per developer at MSFT.

Now they have an outage that should honestly result in people going to prison, at some point we have to question leadership's ability to... well lead because unless something drastically changes I don't think society wants to deal with a massive transnational trillion+ corporation with various monopolies that controls many aspects of our lives if they're going to continue to give us shit service.


This is hardly the first time they've had an outage this bad. And it won't be the last.

I'm blaming the enshitification of absolutely everything. AI or not, it's all just become bloated piles of code.

Using AI is lazy. Lazy creators get lazy responses.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: