I wonder if the author minds that every store that he shops in and restaurant that he visits records his face on their video surveillance systems? Sure, maybe it's 2D instead of 3D, but much more pervasive.
Thank you for posting this. I've been trying to convince people they can do this for the last week and they look at me like I'm insane. They can even buy an insulin syringe carrying case for a few dollars if they need something robust.
Everyone knows global variables are bad, but when you need to ship an app soon and would have to modify a dozen classes and methods to transmit one tiny piece of information from the top level of an app all of the way down to the bottom (or vice versa), a global variable works nicely.
Turn on FileVault to encrypt the drive. Set a firmware password. Make sure there are no guest accounts. See https://support.apple.com/kb/P... and https://support.apple.com/en-u... . Turn off iCloud and don't enter an AppleID. Use an encrypted text editor on top of this with a 3rd password. This won't stop the NSA, but will stop most hack attempts. Putting documents on an encrypted SD card is not a bad idea.
Drones can be hacked. Their signals jammed or spoofed. Their satellites destroyed. Their home bases attacked or infiltrated. They work very well against low tech enemies like Iraq and Afghanistan. Against the Russians or Chinese it would be a different matter, especially when the chips in a drone originate in China. War is an ever-changing game where every move has a countermove. The nice thing about human pilots is that they understand their orders and the underlying reasons for those orders. They can change their minds quickly and use situational information that drones would lack.
I'm not sure that g-force matters all that much in an era of smarter, faster missiles. When was the last real movie-style dogfight?
On the other hand, there is no question that drones are useful and will continue to improve at a rapid pace. Eventually they will replace most of our planes. With longer flight times we might be able to replace half of our aircraft carriers with land-based drones, but the inevitable cost overruns won't magically disappear.
Date-driven development is almost always a disaster. The only way it works is to completely finish a reduced feature version of the application, add and test one feature at a time to it, and ship what you have when the date is hit.
I couldn't agree more about Apple abandoning perfectly fine, expensive hardware. My 8-core, 3GHz MacPro2,1 can still run circles around most of Apple's current lineup and yet it won't run Mountain Lion. I specifically waited for "64-bit" hardware so it would last longer. If new MacPros weren't so damn expensive or offered something more than compatibility in return it wouldn't be quite as annoying.
SPDY solves *a* problem, but not *the* problem. The root of the problem today is that loading a simple web page requires 20 or more separate connections: images, ad networks, tracking systems, social network links, 3rd party comment systems, javascript libraries, css, etc. Somehow all of that content needs to be coalesced into fewer connections.
As an old guy, I am not looking forward to a future with servers named after Harry Potter characters. If Trek was good enough for us, it's good enough for our kids!
Yes, I've cursed them for more than 25 years because trying to fit desktop application storage into relational models nearly always creates more work than necessary.
Key-value storage is merely a two-column table, for instance.
Except that the column types are fixed. What happens if keys point to different types of data (images, text, movies, urls, other tables)? Do you create one column for every type of data that may be used into the future? One table per data type? Do you misuse blob columns? One of the nice things about sqlite is that it doesn't force developers into such a restricted world view.
Just because you can haul anything in a semi truck doesn't mean that a semi truck is the optimal vehicle for hauling everything. Sometimes it's better to use 5 minivans. Do you seriously think that Google Maps are implemented in BigTable because the folks at Google were too stupid to use a relational database?
Slashdot Mirror
Mongo just pawn in game of life.
I wonder if the author minds that every store that he shops in and restaurant that he visits records his face on their video surveillance systems? Sure, maybe it's 2D instead of 3D, but much more pervasive.
Thank you for posting this. I've been trying to convince people they can do this for the last week and they look at me like I'm insane. They can even buy an insulin syringe carrying case for a few dollars if they need something robust.
Everyone knows global variables are bad, but when you need to ship an app soon and would have to modify a dozen classes and methods to transmit one tiny piece of information from the top level of an app all of the way down to the bottom (or vice versa), a global variable works nicely.
Multiple heads on each side of the platter might be a better solution, one for the inner part and one for the outer.
Turn on FileVault to encrypt the drive. Set a firmware password. Make sure there are no guest accounts. See https://support.apple.com/kb/P... and https://support.apple.com/en-u... . Turn off iCloud and don't enter an AppleID. Use an encrypted text editor on top of this with a 3rd password. This won't stop the NSA, but will stop most hack attempts. Putting documents on an encrypted SD card is not a bad idea.
Obligatory West Wing map discussion: (it's worth it if you haven't seen it) http://youtu.be/vVX-PrBRtTY
Don't forget Africa.
One spin-off can handle A-M searches and the other can handle N-Z.
K & R
Effective C++
Object-Oriented Software Construction by Bertrand Meyer
The PostgreSQL manual
People were afraid of being treated like numbers rather than human beings. It was a very different era.
This clip from The West Wing sums up map projection issues nicely: http://youtu.be/n8zBC2dvERM
"People are very open-minded about new things - as long as they're exactly like the old ones." - Charles Kettering
Drones can be hacked. Their signals jammed or spoofed. Their satellites destroyed. Their home bases attacked or infiltrated. They work very well against low tech enemies like Iraq and Afghanistan. Against the Russians or Chinese it would be a different matter, especially when the chips in a drone originate in China. War is an ever-changing game where every move has a countermove. The nice thing about human pilots is that they understand their orders and the underlying reasons for those orders. They can change their minds quickly and use situational information that drones would lack.
I'm not sure that g-force matters all that much in an era of smarter, faster missiles. When was the last real movie-style dogfight?
On the other hand, there is no question that drones are useful and will continue to improve at a rapid pace. Eventually they will replace most of our planes. With longer flight times we might be able to replace half of our aircraft carriers with land-based drones, but the inevitable cost overruns won't magically disappear.
Date-driven development is almost always a disaster. The only way it works is to completely finish a reduced feature version of the application, add and test one feature at a time to it, and ship what you have when the date is hit.
He is probably confusing lines of code with value.
I couldn't agree more about Apple abandoning perfectly fine, expensive hardware. My 8-core, 3GHz MacPro2,1 can still run circles around most of Apple's current lineup and yet it won't run Mountain Lion. I specifically waited for "64-bit" hardware so it would last longer. If new MacPros weren't so damn expensive or offered something more than compatibility in return it wouldn't be quite as annoying.
Google and Apple should respond with "We will if you will."
SPDY solves *a* problem, but not *the* problem. The root of the problem today is that loading a simple web page requires 20 or more separate connections: images, ad networks, tracking systems, social network links, 3rd party comment systems, javascript libraries, css, etc. Somehow all of that content needs to be coalesced into fewer connections.
Programmer productivity will suffer.
In general that is how it works, but Bloomberg is more of a nanny billionaire.
As an old guy, I am not looking forward to a future with servers named after Harry Potter characters. If Trek was good enough for us, it's good enough for our kids!
Now all we need is polarized contact lenses so you don't look silly.
If you had to destroy hard drives regularly, the Pure Leverage hard drive crusher looks like a nice way to do it:
http://www.youtube.com/watch?v=vY3ZssxkcsQ
But it's a bit expensive for only 10 drives -- $325.
Have you ever used a relational database?
Yes, I've cursed them for more than 25 years because trying to fit desktop application storage into relational models nearly always creates more work than necessary.
Key-value storage is merely a two-column table, for instance.
Except that the column types are fixed. What happens if keys point to different types of data (images, text, movies, urls, other tables)? Do you create one column for every type of data that may be used into the future? One table per data type? Do you misuse blob columns? One of the nice things about sqlite is that it doesn't force developers into such a restricted world view.
Just because you can haul anything in a semi truck doesn't mean that a semi truck is the optimal vehicle for hauling everything. Sometimes it's better to use 5 minivans. Do you seriously think that Google Maps are implemented in BigTable because the folks at Google were too stupid to use a relational database?
The OOP to Relational mismatch is described at: http://en.wikipedia.org/wiki/Object-relational_impedance_mismatch