Fair point, just looked it up and it seems to be illegal to do that. But in my experience, many probably still do it, or people don't trust that hospitals will follow the law...it may be more of that latter part, not knowing whether they will or won't ask you for money, or whether they will or won't take your insurance. So I think that uncertainty can mean having to be prepared for it anyway.
Who is going to write tests? But I like the fact that this approach implicitly approves of the stochastic parrot model. I mean, given enough computing power and sufficiently well made tests, I could just generate random strings of increasing length until one compiles into a program that passes all tests, mission accomplished. Like one million apes typing on one million typewriters.
Instead of having an open port in my router and sending data in plain text, I would use an ssh tunnel or a vpn. Or probably put the entire web site on the VPS.
If a significant share of your employees optimise in the sense of doing the least of work possible, without getting fired, you have a huge problem anyways. Usually, given the right conditions, people have intrinsic interest in doing a good job. Even if their motivation is more of the extrinsic type, there is more to it than getting paid.
I have worked a fair share of that kind of jobs in the past. The colleagues on my level who cared about more than being paid and not getting fired where the absolute majority. People want to belong. They want to work. The ones who are the exception of the rule can be seeded out pretty quickly. You do not work for an organisation for 10+ years, wake up one day and switch to pure opportunism.
As for incompetent management, that problem can not be solved by churning workers. It can only be solved by better career paths and selection processes for management roles. The most intelligent people in an organisation are often more interested in getting things done than getting more power.
All true, but it is still bad style. There is no need to keep decrypted passwords in memory the user hasn’t even used in the session (or after they logged in to a certain website).
What I don’t need doesn’t need to live unencrypted in my RAM. Of course I do. It is standard behaviour of iOS, and of a lot of password managers. If someone grabs my laptop and runs, at least they can’t capture my hn account.
The Swiss cheese model is what people use to sell you more 'security' related software systems that inherently involve more problems. (Also cheese is not very durable, even the kind without holes.)
That is redundancy in my book. I don’t expect holes in my GNSS devices. And if you want to be sure, bring three, because two GNSS units with different readings are not very helpful.
I don't expect holes. But both devices are exposed--something could happen to one of them. And since I like going out in the middle of nowhere I assume I either have to get myself out, or if that's impossible summon help. I don't want a single point of failure on either of these.
Our local discord questions the use of 2.4ghz for longer than 50 feet, between WiFi and Bluetooth, microwaves, and millions of "2.4 GHz (nonspec) wireless devices", the spectrum is just trashed.
Plus mechanical release mechanisms of heavier machinery were often designed in a way that the clutch snaps at a certain point (also in order to reduce wear in the clutch).
Also because farm machines usually need max torque fast to break loose from static friction. You want a clutch to bite hard when pulling things through mud.
reply