Comment WTF (Score 0) 355
How did this SJW propaganda get elevated to the front page? That article is sensationalist bullshit.
How did this SJW propaganda get elevated to the front page? That article is sensationalist bullshit.
Burger King are basically nothing more than Black Hat hackers showing us the devices are insecure. Anyone stupid enough to have bought into this generation of voice activated devices deserves all the accidental or malicious triggering they get because the devices just have no attempt at security at all. I mean, I hope the gen 2 devices make some attempt to authenticate that its their owner issuing commands.
Right now these devices are as secure as running routers or other iot devices with the default passwords.
"Empty seats" in the sense of the article are already profitable for the Airline, as someone has payed for the seat but didn't show. They don't "cost the airline money" except in the sense that they are a revenue opportunity to sell the seats of no-shows a second time.
Perhaps airlines should be forced to refund tickets if they manage to resell the seat - which given the way their pricing works they invariable do at a higher price anyway.
Whats the deal with nulls?
While I can attest to the accuracy of the other 8/9 issues causing extended bouts of hair-pulling stress, I've never found nulls be problematic.
I mean, sure they have been a source of errors while developing, but dealing with them is just as aspect of dealing with function boundry conditions, and whether you do it via bools, nulls, exceptions or whatever, it has to be done.
"Switches off parts of Brain" is just a very dramatic way of saying "You won't remember the route".
"Oooo, I better read the article, lest I become permanently retarded next time I use a GPS!"
Maybe they should ask low performance employees what they need!
High performance employees clearly already have what they need.
A password hasher takes a password that you can remember, the domain you need the password for and cryptographically hashes them together to generate a secure, site specific, password.
There are browser plugins that can intercept your weak-used-a-lot password on webforms and replace them on the fly with the strong, per site, password.
Nothing is ever stored, all you do is remember a few easy to recall passwords.
Ok. Some empirical science.
Suggest to your GF that, this weekend, you stay home, go no where, and have sex.
Game developers used to ask players what they wanted, and players asked for more, harder, content. Then the internet was invented, and consoles got online games. And developers got to measure the gap between what players said they did, and what they actually did. And game developers found that the more, harder, content was mostly ignored, and actually the majority of players gave up on content longer than a few hours, and stuck to easy mode. Because thats where the fun is.
i meant Starcraft I of course.
Multiplayer has never been about me and some strangers. Multiplayer is a social experience. Multiplayer is LAN gaming. Multiplayer is why the PS/2 supported 4 controllers.
There is a real dearth of PROPER Multiplayer game titles for the Wii, PS/2 and PC this last decade.
Diablo II - I played with my friends on a LAN, not on Battle.NET. The same for Starcraft II.
Games like counterstrike were big LAN titles. Champions of Norrath and Baldurs Gate were the last proper multiplayer titles on the console and I think theyre 10 years old now.
The modern focus seems to have become PvP focused games played over the internet. Not co-operative titles played with friends, on a couch.
I want multiplayer.
Reading patents with an eye to identifying "Technologies" to use is an exercise in futility:
Most are stupidly obvious. The others written in leagalease.
Reading patents with an eye to identifying "technologies" to avoid is also an excercise in futility. Again, you need the mind of a lawyer, combined with the approach of a security researcher, to "see" the ways a patent could be exploited to somehow map to your own problem domain. That you were happily solving without resorting to the giant database of solutions to micro problems no one is interested in.
Next, theres just too damned many of them. If anyone took the time out to exhaustively read and analyse each patent enough to determine if the possibility for collision existed, well they wouldn't have a problem with patents as they'd never write any code.
Lastly, it takes courts a long time to determine if a particular product does conflict with a patent. This means theres a lot of grey area around the edges of a patent to determine if a particular approach is covered or not. Which means, of necessity, that, like Chinese ISPs, developers who read a patent would have to defensively eliminate huge swathes of potential solution space from their investigations, to avoid getting "too damned close".
* Try and discuss the issue rationally, be ignored (and follow up with the remaining two options)
* Ignore the directive and continue listening to music, collect three written warnings and be fired.
* Quit now.
The sad truth is, people who think like this exist. And you CANNOT change their mind. Sometimes. But not every time. They end up in positions of management. They believe that rules, and strict control, is how to achieve productivity in their underlings and every descision they ever make will be coloured by that.
They will install firewall software to monitor and block employees web access, despite the fact that a lot of useful research material code-wise tends to occour on blogs, wiki's and other sites that fall into blacklist categories like "peer to peer", "social networking" or "network backup". Your life degenerates into a living hell of finding every topic of research ends up being a google results page full of blocked results.
The will disallow any form of gaming on company hardware (during non work hours) because they are oblivious to the team building aspects of LAN games, as well as the inspiration many programmers (especially games developers those lucky bastards) find in the work of others.
They try to measure productivity in meaningless and easy to game metrics like "number of bugs per test cycle" or "lines of code written".
Unless (and only if) you manage to make a successful stand against them, they will use the failures engenderd by their own bad policies as evidence that more draconian measures need to be introduced. Every time a critical bug reaches the world, they will react by adding more developer 'checks' and testing procedures, ensuring that the next bug is yet more expensive (and time consuming) to fix. Each time, YOU the developer will be blamed for the ever more massive costs incurred by their futile attempt to stamp out the one constant of computer science - if youre not making bugs, youre not developing features.
This will over time, sap the reason you became a programmer. your zest and zeal will die. Programming will become a 9 to 5 hellish drudge that you can only hope to escape from at the end of the day. You will feel self doubt and actually come to believe that it IS you, not them, responsible for the hellish state of affairs - where it takes over 6 months to develop and ship a single feature or upgrade.
These people read dilbert, and find it funny not sad - because theyre empathising with the PHB.
You cannot frankly discuss things with them because, while you are both speaking english, your core understandings of basic concepts is fundamentally different. As such, when you present what you belive to be a compelling argument to them, they will draw a totally different conclusion from the same data. they are not idiots. Or classically stupid.
they do however think differntly. And they live amongst us. and become our managers.
Live free or die.