3 ms·
> I remember grepping the source for pthread_mutex or pthread_cond and slowly realizing that whoever wrote the code didn't even see the need for locks. To be fa
by _pmf_ 13y ago
> I remember grepping the source for pthread_mutex or pthread_cond and slowly realizing that whoever wrote the code didn't even see the need for locks. To be fair, I later heard it was some poor hardware guy who knew some C who got roped into writing the software as an afterthought to show off the awesome hardware, a common problem with hardware companies.
"Oh, you wrote a quick demo for the sales people? Well, now it's a product sold for some ten thousand!"
- rdtsc 13y agoYou joke, but in military contract world that is totally fine. Everyone already got paid and bugs will certainly not stop the acquisition process in the future. It is all about who knows who and more about jumping around red tape certifications, ATOs, ATCs, rubber stamps and so on. That is often why soldiers on the ground end up with overpriced yet crappy tools and weapons.
- astrodust 13y agoThis is also why automatic weapons with fully autonomous control is probably a very bad idea. The good news is that if Skynet ever happens, it will probably crash before it can take over the world.
- rayiner 13y agoTo be fair, it's not just red tape. If you are the Army and your one of the kind custom spec piece of hardware has software bugs, what exactly are you going to do? Buy the compatible version produced by the competing vendor?
- rdtsc 13y agoIdeally you have prototypes and tests before hand that should discover these issues. Then in the future you would pick a different vendor. You can also set up your contract to account for maintenance and for penalties for serious bugs. A lot of things are possible but they are not happening the incentives are just not there.