Aug 15 2010 2:17pm from IGnatius T Foobar @uncnsrd
The conundrum of data center operations:
Reliability requires redundancy.
Redundancy introduces complexity.
Complexity reduces reliability.
Solution: self-reinforcing simplicity
Ah, yeah, I could see that being annoying.
the waledac botnet was just killed by microsoft and some other parties...
they switched off the DNS via judge and captured the control servers...
They should probably ask themselves why they're still using tape media :)
I just could not turn down this deal: http://www.newegg.com/Special/ShellShocker.aspx?nm_mc=EMC-SD042910&cm_mmc=EMC-SD042910-_-email-_-E0-_-13-131-398
Time to build a new box. As if I don't have enough to do around here.
No cats around here..I'd start sneezing if there were. As for the dirty lens...that should make the sensor less sensitive. I am wondering about transient voltage spikes or breakdown of the semi-conductors in the sensor.
Trust me, there is nothing more fun than getting up in the middle of the night to investigate an alarm at a remote location.
Is his name Mel?
Only one thing might be better than eclipse for writing Java, and that's JIDEA. Lispers, I suspect, don't need that Refactor menu, because they already have good language support for referential transparency, and a dynamic type system. Not the case in Java, where changing structure can cause so much carnage that in a nontrivial program it has to be automated.
Since I'm the family IT-guy, I've had to do a lot of these tasks before, and this technology will definitely make it easier.
Heh. Amazon EC2 is having a major outage. It's been going on since
around 2:00am. Super major brokenness all over.
So much for elastic.
This brings to mind the recent discovery of the flaw in just-in-time assembly line production.
Just in time works just fine until japan as a whole goes off line and nobody's got any stockpile of parts anywhere in any warehouse and suddenly the entire manufacturing process of anything using parts coming from japan comes to a quick and grinding halt.
So now people are starting to rent warehouses not because they need to stockpile parts, but they need a buffer in case of disaster.
It looks like the amazon customers are learning this same lesson today.
make it a game...
no problems apart from that its an interpreted language where everybody wants to talk away the fact that this will be slower than native code.
just because of you store a pre-parsed copy of the interpreted code, thats no compiler. No body would call the zend-cache a JIT
Where I sit (and most people aren't like this, I'll admit) I'm tired of it all, I just want it to work.
why not? everything is a file. block devices are random access.
HA! That's funny. I hate fk constraints almost as much as I hate
stored procedures, but try explaining to a territorial dba (read: all
of them) that their fancy dancy constraints are fucking everything up.
The funny thing is, we don't use them at $workplace, as far as I can tell, we never have. This probably goes back to the dawn of time when HJM wrote all the code and did the DBA stuff himself. So it's become standard practice here, and now the DBAs are defending it because it's become defacto standard, and they don't want any inconsistency, or extra work, or to change the status quo, and they probably realize the advantages by now.
One of the reasons why I *like* our DBAs. (Well... sometimes ;) And it goes to show: if you don't like what your DBAs are doing, the solution is simple: be the Creator.