Sure, it would have taken a little bit more effort, but this sort of thing should have been built using the standard Twitter interface, just follow all politicians using multiple anonymous accounts and then note whatever they delete. Then it would have been secure against any bull the lead Twits might decide whether it be blatantly revoking their access or secretly moderating their access. And you can't really say no one expected there would be an attempt to shut it down.
Another stupid thing is expecting to be able to publish something publicly, and then keep it a secret.
Finally, the Twits thought they could shut down this service, even though lots of people wanted it and the only way to really stop it would be to shut down their own company entirely.
The business side of the house may blame developers for not moving fast enough,
Yes, but that is the most pathetic excuse ever. No one is preventing the business from hiring additional workers, if the business lied about its workers' capabilities or is managed by idiots who substitute optimism for basic estimation skills that's their own problem.
NSA -- probably already had the info India -- probably wrote their code Pakistan -- probably isn't really willing to piss off their citizens and lose a company
There's two types of "flexible working": 1) Employee may take time off or work extra at any time at their own discretion 2) Employer will force employee to work extra at any time with no warning 2a) The hours are theoretically at the employee's discretion, so long as they understand that anyone who doesn't drop whatever they're doing to work on "request, if you feel up to it" will be fired. 2b) The hours are theoretically at the employee's discretion, but there's an "emergency" every week that means you really ought to work extra hard this week.
The first kind is relaxing to anyone who does not require "external motivation". The second kind will destroy your life (though no doubt a few people would enjoy it).
Sorry, your database, and it's NULL entries, are nothing more than magic numbers. I'm discussing NULL in a database as related to the story, and you're discussing NULL in a database that isn't in the story but pretending it is because that's the database you're familiar with.
No, it's not. Don't take my word for it: play with SQL and realise that NULL doesn't behave like a number when used in operations and functions.
So if I take your SQL database, and read it with a C program that prints the file bit by bit as ones and zeros, at some point your magical non-numerical NULL entry will output something other than a number?
2) It's not always unambiguous, hence this story.
It's definitely unambiguous. Again, don't take my word for it, take e.g. a TINYINT and try to figure out which of its possible values is ambiguous with NULL. (Read: SELECT x = NULL results in True, hint: there is no such value).
The story is *not* about NULL having an ambiguous representation: it's about the programmer *not* using NULL to represent the concept of "missing information" (which is exactly why it exists in SQL) and instead (ab)using a specific numerical value.
Yeah, but if you read the database with a different program that has a different idea of which number means NULL then all your NULL entries are suddenly numbers. And maybe someone thought they'd be clever and store data more efficiently by using only 8 bits to store their TINYINT, then messed it up their handling of NULL.
42 percent say it's more important for the government to ensure Americans' safety than to protect citizens' rights, while 27 percent think rights are more important and 31 percent rate both equally.
So, 42 percent say that it's important to protect citizen's rights because it will keep them safe from the biggest threats to their wellbeing, 27 percent say that it's important to protect citizen's rights because rights are important, and 31 percent think rights need to be respected both for safety and and because rights are inherently important.
Haha, just kidding, 42% are idiots and 31% are mentally challenged, plenty to force upon us the sacrificing of our safety against real threats for the illusion of safety against statistically insignificant threats.
How you'll need to define your programming data model to accurately map all informations you read from the DB is a completely different issue and doesn't change the fact that the DB *does* provide a specific value which represent unambiguously the concept "information is unknown".
1) That specific value is a number 2) It's not always unambiguous, hence this story.
[...] And also because NULL should be NULL, not a value that might be valid to other types of code.
Blah, blah, blah, I don't care how you fancy it up, everything the computer does is dealing with numbers. NULL is just another binary number any way you slice it, and it will be a valid number in code if you're not careful keeping track of which data is NULL and which is the number used to represent NULL.
If you disagree, please by all means tell how *you* represent NULL without using some combination of ones and zeros.
A bug is not actually an insect, but a mistake in the code (which is code for the instructions written for a computer). And jailbreaking doesn't involve an actual jail. The editors need to explain these things, they can't expect us all to be nerds can they?
Slashdot Mirror
3) Cancer.
(Gene editing has a history of being imprecise, keep in mind to treat a genetic disease this also means delivering to each affected cell in the body.)
Sure, it would have taken a little bit more effort, but this sort of thing should have been built using the standard Twitter interface, just follow all politicians using multiple anonymous accounts and then note whatever they delete. Then it would have been secure against any bull the lead Twits might decide whether it be blatantly revoking their access or secretly moderating their access. And you can't really say no one expected there would be an attempt to shut it down.
Another stupid thing is expecting to be able to publish something publicly, and then keep it a secret.
Finally, the Twits thought they could shut down this service, even though lots of people wanted it and the only way to really stop it would be to shut down their own company entirely.
If she has a condition that gives her a DUI, she shouldn't be driving, ever. Sucks for her but too bad.
Maybe so, but was she under the influence?
The business side of the house may blame developers for not moving fast enough,
Yes, but that is the most pathetic excuse ever. No one is preventing the business from hiring additional workers, if the business lied about its workers' capabilities or is managed by idiots who substitute optimism for basic estimation skills that's their own problem.
NSA -- probably already had the info
India -- probably wrote their code
Pakistan -- probably isn't really willing to piss off their citizens and lose a company
Its not that big a deal, it's meaning is still clear.
I heard BlackBerry had been in quite a jam due to a thorny situation, their operations in Pakistan were about to become toast.
There's two types of "flexible working":
1) Employee may take time off or work extra at any time at their own discretion
2) Employer will force employee to work extra at any time with no warning
2a) The hours are theoretically at the employee's discretion, so long as they understand that anyone who doesn't drop whatever they're doing to work on "request, if you feel up to it" will be fired.
2b) The hours are theoretically at the employee's discretion, but there's an "emergency" every week that means you really ought to work extra hard this week.
The first kind is relaxing to anyone who does not require "external motivation". The second kind will destroy your life (though no doubt a few people would enjoy it).
TL;DR: Kids these days.
And that is usually a good idea. But where I come from, bits are numbers.
but missed the social media revolution
I thought the implication was that he founded the social media revolution and avoided the social media devolution.
Sorry, your database, and it's NULL entries, are nothing more than magic numbers. I'm discussing NULL in a database as related to the story, and you're discussing NULL in a database that isn't in the story but pretending it is because that's the database you're familiar with.
1) That specific value is a number
No, it's not. Don't take my word for it: play with SQL and realise that NULL doesn't behave like a number when used in operations and functions.
So if I take your SQL database, and read it with a C program that prints the file bit by bit as ones and zeros, at some point your magical non-numerical NULL entry will output something other than a number?
2) It's not always unambiguous, hence this story.
It's definitely unambiguous. Again, don't take my word for it, take e.g. a TINYINT and try to figure out which of its possible values is ambiguous with NULL. (Read: SELECT x = NULL results in True, hint: there is no such value).
The story is *not* about NULL having an ambiguous representation: it's about the programmer *not* using NULL to represent the concept of "missing information" (which is exactly why it exists in SQL) and instead (ab)using a specific numerical value.
Yeah, but if you read the database with a different program that has a different idea of which number means NULL then all your NULL entries are suddenly numbers. And maybe someone thought they'd be clever and store data more efficiently by using only 8 bits to store their TINYINT, then messed it up their handling of NULL.
42 percent say it's more important for the government to ensure Americans' safety than to protect citizens' rights, while 27 percent think rights are more important and 31 percent rate both equally.
So, 42 percent say that it's important to protect citizen's rights because it will keep them safe from the biggest threats to their wellbeing, 27 percent say that it's important to protect citizen's rights because rights are important, and 31 percent think rights need to be respected both for safety and and because rights are inherently important.
Haha, just kidding, 42% are idiots and 31% are mentally challenged, plenty to force upon us the sacrificing of our safety against real threats for the illusion of safety against statistically insignificant threats.
So your computer uses trinary, one, zero, NULL? My computer would store a flag bit as a number, either one or zero.
How you'll need to define your programming data model to accurately map all informations you read from the DB is a completely different issue and doesn't change the fact that the DB *does* provide a specific value which represent unambiguously the concept "information is unknown".
1) That specific value is a number
2) It's not always unambiguous, hence this story.
Who do you think classifies information?
Usually some asshole who did something to embarrass himself and doesn't want anyone to know about it.
If you treat NULL as 0, then I hope you are not a developer.
Obviously. You need to treat it as ValueOf(NULL), since it might be zero in one program or some other number in another.
So which number do you use to represent NULL in your database? (Hint: it's a binary number)
[...] And also because NULL should be NULL, not a value that might be valid to other types of code.
Blah, blah, blah, I don't care how you fancy it up, everything the computer does is dealing with numbers. NULL is just another binary number any way you slice it, and it will be a valid number in code if you're not careful keeping track of which data is NULL and which is the number used to represent NULL.
If you disagree, please by all means tell how *you* represent NULL without using some combination of ones and zeros.
I don't understand people who prefer to use magic numbers over NULL, but there appear to be many.
Last I checked, NULL is just a magic number (usually zero).
A bug is not actually an insect, but a mistake in the code (which is code for the instructions written for a computer). And jailbreaking doesn't involve an actual jail. The editors need to explain these things, they can't expect us all to be nerds can they?
Looks like Linux is better than Windows at something.
I'll be sure to park my time machine on the International Space Station.
Just make sure that the roboceptionist is sufficiently buggy. People have no trouble with "my spam filter ate the email".