|
QuarkJets posted:For sure, that's garbage fire design. But I don't know of any SQL engine that's immune to garbage fire designers
|
#
¿
Nov 13, 2017 15:50
|
|
|
|
| # ¿ May 16, 2024 18:02 |
|
|
Dr. Stab posted:How do you tell that two passwords are similar based on their hashes? You don't. You make the user enter their old password when they're changing it to a new one so the comparison can be done client-side.
|
|
#
¿
Jun 20, 2018 14:36
|
|
|
While I guess the whole point of this thread is that no one deserves the benefit of the doubt, I would hope that the system is actually "You can't reuse passwords ever (because we store the hashes for all your old passwords) and you can't use a password that is too similar to your current one (because we compare them before we compute and save the hash)."
|
|
#
¿
Jun 20, 2018 15:25
|
|
|
QuarkJets posted:A giant jackass to whom? It's meaningless text on a website, not a binding contract A giant jackass to people who think that a CoC is a useful tool in the quest to not have the software development industry dominated entirely by giant jackasses.
|
|
#
¿
Oct 25, 2018 16:27
|
|
|
Volguus posted:https://slashdot.org/poll/3103/what-do-you-make-of-programming-languages-and-open-source-organizations-adopting-a-code-of-conduct
|
|
#
¿
Oct 25, 2018 19:48
|
|
|
Ola posted:Well if person A won't do it for person A's convenience, person B has to do it for person A's convenience. Is that more reasonable? If there is a big demand for it, performance boosts, sure. But the way Stroustrup explained it, it was a pretty niche group and they didn't have great reasons for it. And it's perhaps not the greatest example. Anyway, Stroustrup seemed like a guy with serious mass email flame war PTSD.
|
|
#
¿
Mar 18, 2019 14:40
|
|
|
ToxicFrog posted:As noted, while that's worse than producing an error message it's definitely better than silently emitting invalid code. IMO, silently doing the wrong thing is the worst possible failure mode for a compiler. Right, but in Suspicious Dish's case, it didn't emit invalid code, it just didn't do exactly what they thought it would do because the feature spec is slightly confusing.
|
|
#
¿
Mar 25, 2019 14:18
|
|
|
Hammerite posted:[snip] Whereas "private stuff is private" is a pretty easy rule to understand.
|
|
#
¿
Sep 16, 2019 19:20
|
|
|
OddObserver posted:Yep. https://www.khronos.org/registry/vulkan/specs/1.1-extensions/pdf/vkspec.pdf page 1425: It helps a little bit that there is a space in front of the footnote superscripts and not in front of the exponent superscript, but in general that's pretty loving stupid.
|
|
#
¿
Oct 11, 2019 14:02
|
|
|
Volte posted:"Getting hit by a car being driven by a person" and "getting hit by an unmanned machine gone haywire" are in fact two different things. That said, you are probably correct that if the breakdown of deaths is significantly different, then we'll have to, as a society, decide if the trade-off is worth it. As an extreme example, if autonomous cars got rid of all traffic fatalities except for kids at school bus stops, which quintupled, would that be a trade-off we'd be willing to make? Is going from 35k+ deaths (including ~1,200 children) to ~100 deaths a year, but all children, a choice our society would make?
|
|
#
¿
Nov 8, 2019 16:35
|
|
|
You say that like it's not working as intended.
|
|
#
¿
Nov 19, 2019 22:45
|
|
|
ratbert90 posted:My team lead just tried to tell me that you shouldn't have the expectation of who get's what tickets beforehand before they get assigned a point value.
|
|
#
¿
Jan 23, 2020 19:41
|
|
|
|
| # ¿ May 16, 2024 18:02 |
|
|
Tei posted:I have heard multiple times about "identity thief" in USA - Is not a problem here in europe have The basic idea is that the USA doesn't have an official, universal, federal identification. The Social Security Number (SSN) was originally just the identifier for one's Social Security account (the government backed "retirement" account). But then it was repurposed as an individual's taxpayer identification. And from there it became the de facto Federal identification number, used for things like military ID. But because it wasn't designed as a universal federal identifier, it has some problems. First, the SSN card itself has no identifying information, just the name and number, so anyone could take an SSN card and say "yep, this is me", and people accepting the card would be none-the-wiser, unless they checked for supporting ID, which could sometimes be fraudulently obtained using the SSN. Second, the SSN was, originally, just the ID number for your Social Security Account, not a particularly interesting piece of info, so it wasn't treated as a big secret. It was printed on all sorts of stuff, stored in plain text in ancient mainframe databases, and re-used in all sorts of other places (like employee numbers and bank customer ids; many states even used it as your driver's license number). And it wasn't particularly random, so if you knew some information about a person, like the place and date of birth, you could guess the first 5 digits pretty reliably, meaning if you had the last four digits you had the whole number. So, a number that initially had a single purpose became used as a universal identifier, and also organizations treated it as if it were a secret that only an individual would know, when no one ever put much effort into keeping it secret. This, as you may have guessed, was a recipe for disaster.
|
|
#
¿
Jan 31, 2020 18:25
|
|