What's the fastest hash or CRC algorithm?

mott555

Not your job as a developer. However, as a tester, you are responsible for identifying probable failure modes and testing those.

I'm not a firmware/hardware engineer. That stuff is all way over my head. I just need to make sure the systems are stable at high but reasonable utilization, and any issues get reported to the responsible parties. I suspect the firmware runs out of processing time well before I hit the 2 Gbps line rate.

Boss: "Hey, @mott555, can you take this car up to 80 mph on the interstate and see how it handles?"

Random third-party: "But he doesn't know what alloy the piston rings are made of! He can't test without knowing that! How many teeth are on the first set of planetary gears in the transmission?"

loose

Ok, I'm done here. You design a system that outputs in a particular format / protocol that suits you. Meanwhile, the guy downstream of you is designing "an" interface, according to his best choice of format / protocol. Unless you know his format / protocol, you may as well code.

while (Hell != frozen) {
  openFile(X)
  while( FileSize < maxFileSize) {
    write(X, "U*")
  } 
  close(X)
  send(X)
}

As for testing the car, you would at least want to know is the tank full? Or will I be insured? You may want to know if it is manual or automatic, LH or RH Drive. If only to plan your strategy. Otherwise you may just as well put a blindfold on and get into it.

flabdablet

@mott555 said:

If I can break things through the API, I go to the firmware engineer and say "I broke your network layers and protocols, you fix it."

To be fair, lighting up the black box a little can help you devise better tests. It's easier to break things if you know where the seams are.

flabdablet

@mott555 said:

Boss: "Hey, @mott555, can you take this car up to 80 mph on the interstate and see how it handles?"

Random third-party: "But he doesn't know what alloy the piston rings are made of! He can't test without knowing that! How many teeth are on the first set of planetary gears in the transmission?"

He might also not know that the ECU has been programmed to cause impressive-looking belches of flame when you rev the ring out of it from idle, a fact possibly of interest to the rental company.
https://www.youtube.com/watch?v=KNsjvZk8nT0
https://www.youtube.com/watch?v=8qCHqEIRC2c

loose

In a similar fashion: 30 years ago my then boss got done for speeding in his Porche 911. I overheard him saying that the "...damn rear spoiler pops up automatically when you go over 70 mph..."

On another occasion, he was moaning that the tyres cost £150.00 per corner.

His previous car was a Lotus (forget which, but it was an expensive one) It was a lovely car in all respects. Except for the one where it spent more time back in the Workshop than it did outside his office.

I got to ride in both (one occasion on the "rear seat"), 'cos he and I, on occasion, had to drive the 20 miles or so to the Computer Bureau wot we woz rentin time from for the CADCAM stuff I was doing at the time. He was an inspired man, a sort of 2nd Class Clive Sinclair (contemporary too)

dkf

@NedFodder said:

Adler and Fletcher are each just 4 lines of code. WTF do you need a library for?

So you get it done right? If correctness isn't a concern, you can speed things up a lot more than by just inlining the Adler/Fletcher checksum algorithm…

NedFodder

@dkf said:

So you get it done right?

I was mostly joking with my comment, but are we really concerned about getting 4 lines of code wrong? This isn't rocket surgery...

dkf

@NedFodder said:

I was mostly joking with my comment

Thought so, but sometimes I can't help myself.