Hacker Newsnew | past | comments | ask | show | jobs | submit | fock's commentslogin

that bug likely came from reinventing the wheel

this bug was introduced by clankers most likely...

and now guess who helped writing this code. the chicken are coming home to roost, but people who are happy about their youthful productivity or stock packages will not be able to notice...

the code before this PR included the check. But that was old code!


you don't get credit for that because it is clear you are not very skillful at what AI-bros value most, namely manipulating other nerds...

if you look at the commit history of OpenSSL, you can easily notice how a lot of people started contributing once their clanker got up to speed. They are very happy to rip out weird C and replace it with assembler or intrinsics. Rip out lists of characters formatted as a single string and replace them with array syntax, each char quoted.


so, war is brewing and I guess people got the memo to patch...

how do you access those, when your network is down?

Which network? These are very on-prem and networking sometimes still means things like SNA, TokenRing, etc., no IP or Ethernet.

yes, I read some java today where I wished for the clankerd to have done it...

Think system(curl) and random-if-cascades which are never reached - they removed the system(python) in this iteration though...

At this point I think AI-code is just average and probably just fine for corporate environments/SaaS (especially given what thkse produce today), but I still think infrastructure should be a) understood by humans b) produced without installing a backdoor on the dev machine and c) a human should decide what to build and be able to reign in the machine.


and the code looks very similar to all the wideband sdrs we have mostly forgotten now...

Although a 0-dependency approach from-scratch approach is likely sensible here.


"a lot of AI help" I assume...

Lots of EEVBlog members embraced the Agentic coding phenomena. They have written so much software tools for their test instrument that actually have a use for their hobby.

The reverse engineering capabilities of the new models really help in reviving and creating software for old instrument that have no documentation at all. It's like they all discovered a new hobby of software thinkering to use on their electronic hobby.


The same phenomenon in going on with synthesizers firmware. People going crazy modding previously closed hardware, adding missing features and breaking down artificial segmentation.

What difference does it make?

That the author can't maintain the project without shovelling more money into the money furnace. Or that the UI looks like slop.

Are you really sure about your facts?

I am getting really tired of seeing people shitting on other people’s hard work for no reason other than it was written by AI.

Software has always been sloppy. There are plenty of UI written by humans that look like shit, even after spending more money than likely was burned here.

If you think this effort is so bad, then show us how you could do better without AI. Otherwise, your kind of snark is not contributing constructively here (or anywhere).


well, this goes into the area, where bugs can make your workshop go up in flames (or your devices doing nothing). Kind of weird to use vibecoding for that, but ok...

Or incorrect measurements leading the user to spend weeks chasing ghosts...

"You're absolutely right, my code assumed every waveform is sinusoidal! But in my defense, I left a FIXME comment about that."

(Not about this project, just a general pattern with Claude)


> people’s hard work

> written by AI

I'm getting tired of people shitting on other people's work just because someone else did everything for them!

> Software has always been sloppy

Whatever your opinion on AI is, can we at least agree if you can tell from one look it's slop, you must have been holding it wrong?

People make mistakes, and they learn from them. This is at best training a rented SaaS, while the operator is paying for the privilege.

> show us how you could do better without AI

Believe me or not, I also have some projects in electronics, and I do disclose my AI usage, or often lack thereof. I don't happen to own a Rigol scope, and honestly don't have the skills or interest to reverse engineer my own scope.

I could probably contribute a better UI, but let's be honest, is the author interested in that contribution? Probably not.

Will anyone in good faith argue you can't levy any criticism, unless you first make a competing product? This is not even forbidding customers from criticizing a restaurant, this is you also excluding fellow chefs, just because they won't cook the same meal for you on the spot.


also that this might relatively fast lead to interesting physical effects if claude makes an error...

their employer brought me agent swarms supposed to take over my php-serving machines. whatever this is, I don't feel sorry for them.

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

Search: