Hacker News Reader

Comment by oefrha | Hacker News Reader

The outrageous part of this is nowhere in the blog post or the repository indicates it's vibe coded garbage (hopefully I didn't miss it?). You expect some level of bullshit in AI company's latest AI vibe coding announcements. This can be mistaken for a classical blog post.

Although the tell is obvious if you spent one second looking at https://github.com/nkuntz1934/matrix-workers. That misaligned ASCII diagram, damn.

Why is Cloudflare paying this guy again, just to vibe a bunch of garbage without even checking above the fold content in the README?

View on HN

> Why is Cloudflare paying this guy again

Perhaps usage of AI is a performance target he's being judged against, like at many tech companies today.

> A production-grade Matrix homeserver implementation

It's getting outright frustrating to deal with this.

Fine, random hype-men gets hyped about stuff and tweets about it, doesn't mind me too much.

Huge companies who used to have a lot of good will putting out stuff like this, seemingly with absolutely zero reviews before hitting publish? What are they doing? Have everyone decided to just give up and give in to the slop? We need "engineering" to make a comeback.

https://github.com/matrix-org/matrix-rust-sdk/blob/main/CONT... is an example of engineering trying to make a comeback, on the Matrix side at least :)

As long as you take ownership, test your stuff and ensure it actually does what you claim it does, I don't mind if you use LLMs, a book or your dog.

I'm mostly concerned that something we used to see as a part of basic "software engineering" (verify that what you build is actually doing what you think it is) has suddenly made a very quick exit from the scene, in chase of outputting more LOC which is completely backwards.

I review every line of code I generate, and make sure I know enough that I can manually reproduce everything I commit if you take away the LLM assistant tomorrow.

This is also what I ask our engineers to do, but it's getting hard to enforce.

That's the only way, but I even doing that I fear I loose some competency.

If you take ownership of the code you submit, them it does not matter if it was inspired by AI, you are responsible from now on and you will be criticized, possibly you will be expected to maintain as well.

Vibing is incompatible with engineering and this practice is disgusting and NOT acceptable.

We found that reviewing AI code is bottleneck for performance so we stopped reviewing it

You jest, but I was listening to a podcast episode today by the Changelog, and this guy was effusive how AI will replace SaaS, etc. and when asked about reviewing, said no one can do it well, so they don't/won't do it for key internal software they vibecoded.

I sure hope these people don't call themselves engineers, it's so backwards from how we need to build software as everything around us turns into slop that barely works. So frustrating.

Reply on news.ycombinator.com