"Red Hat Enterprise Linux 7 is unaffected, for example."
So is Devuan.
33132 publicly visible posts • joined 16 Jun 2014
"Once the project was complete, the development team handed it over to support and support would refuse to accept the project as finished and supportable if the code was properly documented."
This!
Development is the process of launching the product into the maintenance cycle. If it's not maintainable that fails. Better still, however, one team owns the product throughout so documentation is self-defence.
"Comments don't have to be updated when code is. When things have to be done quickly because money is being lost then updating the comments doesn't help get the fix into production quickly."
You comment the changes as part of check in. You do have a version control system to check it into, don't you?
"Always write at least two lines of documentation for every function (Or, even every line of code)."
Specifying quantity without quality doesn't necessarily help.
Hypothetical example:
Function name: AddTwoNumbers
Documentation:
Takes two numbers as argument
Returns sum
Yes, we can work that out from the function name. Now tell us something we can't - why you used this algorithm, why you didn't use something else, what the limitations are.
"training new programmers"
That's the key phrase. Their issue is not with the difficulty, it's because it involves spending money training people and then paying them. What's worse those are the sort of people who have to know what they're doing whilst they themselves have been getting away without that for years.
"Blame that on the "ICT" curriculum"
Not in this case. One of the authors is well into her 80s & the other is in his 70s IAFAIK).
I think it's more likely that if you drag an image into Word or whatever and then crop it there's nothing to tell the user that it's not actually cropping it, just framing it. It's only when you click on Edit with external tool and Gwenview shows you what's actually there that such little UI shortcomings are exposed.
I just checked to see if he was also the Tony Lewis who played for England and later became a cricket journalist. He wasn't. However the Wonkypedia entry for the player shows him as having died on April 1st as well. Outstanding coincidence or wonky editor? I'll settle for the latter whilst wondering of the statistician could have estimated the probability of the former.
"Why do you believe that paying for a product makes it secure?"
What the OP said was If you are not paying for a guaranteed, security based, purpose built piece of software
It's the bit's which you missed out that should give some degree of confidence about security. It may still fail, of course, but being paid for with a guarantee gives the purchaser some degree of come-back that might persuade the vendor to do their est to make it so.
What happens if those dual use products also have a use in medical equipment, say ventilators, which get exported to the US? One of the effects of globalisation is that it's not a big world any more. Or, to put it another way, it's difficult to shoot somebody else without your own foot getting in the way.
We're not quite the same - House name, Road name, Post town about 2 miles away. At least post code works for us. The other day I tried ordering something over the phone from the local pharmacist - their merchant S/W required a house number to verify a card payment over the phone.
And what's this "City" field so many forms have? I haven't lived anywhere that ranked as a city for the last third of a century.
OTOH they're the most reliable here. I've had all manner of problems with other carriers who seem to either lose stuff in their systems, deliver to the wrong house or simply not see a house name carved in 6" high letters on a block of stone. Under normal circumstances I prefer to get Amazon stuff delivered to a locker. Vendors' systems that can't cope with a house not having a number are another problem.
The posties, however, know us, would be able to deal with a misaddressed parcel and also know enough to link us and our daughter who lives a mile away and have been known to leave her parcels with us when they didn't have anywhere handy to leave it there. It's the sort of thing that happens out in the country!
"The five-year contract with IBM nestles well with BT's intention to close the public switched telephone network by 2025."
I wonder. Applying the basic law of project timelines "close the PSTN by 2025" translates to "close the PSTN starting in 2025 at the earliest". When that happens we can reasonably expect customer support calls to go up just as the contract for supporting this system supporting customer service ends. From IBM's PoV the renewal nestles well with that, maybe from the BT side not so much.