Forgot your password?
typodupeerror

Comment Re:It's got nothing to do with appeal (Score 1) 89

I started lurking in 4K enthusiast groups to see if they were all cracked up to be. The arguments about relative quality of various BD/4K releases isn't even the most interesting part.

It turns out that there are a lot of issues with set top boxes playing particular disks. The disks themselves also seem terribly fussy.

Comment Re:Outsourcing (Score 2) 38

Yes. lf they need to do is hire a team of crack programmers and system architects and have them start work on replacing the systems. Keep them hired as a key department of the post office and they will maintain the system. If it's good they could even license it out to others.

I've seen this happen in other contexts. E.G. in a semiconductor firm, they designed their own tools. Then they made that a whole department and spun it out as one of the chip design tool vendors which is still around today.

If you just outsource it, you will get a product that serves the needs of the vendor, not the customer.

Comment Readers of Slashdot and HN are drowning ... (Score 3, Insightful) 37

... AI stories.

We all know the emperor has no clothes. We know the "stories" are PR pieces from AI boosters. We know that autocorrect can't replace anybody whose job doesn't involve following an exact script or redoing work that already exist.

Just stop it. Stop promulgating the nonsense. There is no "I" in AI and there is no creativity in the autocorrect that they're pushing on us.

In the meantime we're paying higher electricity costs and having to hold off purchases of equipment or pay extortionate prices for RAM and disks.

All so some billionaires can add a few zeros.

I'm retired, no job to be replaced by the stochastic musings of an over-sold Excel spreadsheet. Just sick of the lies and marketing nonsense. Sick of the slop in the music and writing spheres. Sick of the "I made a C compiler from scratch" lies.

And yes, you can get off my lawn.

Comment They're Doomed (Score 1) 106

I've been using AI to write code recently. I figured I should give it a go.
Not reviewing and understanding and editing the output code is a recipe for disaster.

For example, in code for a cryptographic hash function there are padding rules to bring the data size to a multiple of the block size and add a length. So for example with SHA3, a minimum of 65 extra bits. If your data length mod the block size is 65 bits less than the block size, then add the pad bit, put the length at the end of the block and fill in between with zeroes.

If you are longer than that, then it all spills over into the next block and you add a block.

If your length exactly ends up fitting in the block size, then you add a whole extra block with just the padding bit and length and a bunch of zeroes.

The hash that claude spit out missed that last case, so creating a hard to find bug, where in one out of 512 bit sizes, the hash fails. If I had not spotted that by reviewing the code in detail, there would have been a catastrophic bug creating a security vulnerability and system failures in chips.

So read the code and fix it or be doomed.

Slashdot Top Deals

Nothing happens.

Working...