Did anyone else notice that they used a football as their central "pod" for the ship in the article's graphic? It looks like a bad copy/paste job involving circa 1998 Bryce 3D, MS Paint, and a TI-83.
I couldn't agree more. I first moved to XFCE when I was looking for a lighter window manager on an older computer. This was about a year ago, and I haven't looked back. Everything just works, and failing that, is fairly simple to configure. No godawful semi-maintained nigh-mandatory extensions lists, no configurator-cum-registry, no fighting with dozens of default helper services. It's just... functional. Is that too much to ask?
I have a few too many business degrees and miscellaneous related credentials, so I have some clue what I'm talking about.
The GP is right on this one. Technical and other professional workers are generally to be left to their own devices. Micromanagement is only to be used on those with little experience and job knowledge, or specific cases of a problem employee. This has been thoroughly studied and well-known in the (educated) business community for decades.
You forgot the person that was electrocuted in Edison's new "Electric Chair" as the final demonstration of the "evil" of AC power. Yeah, it took him like 8 minutes to die as he was slowly cooking from the inside and screaming like a banshee.
If the software was never publicly published, it wasn't really open source software to begin with. You release early and you release often, also for these sort of things.
He released it to himself. I wonder if that is enough? If so, there are some strange implications for anyone coding for a living. Want to have rights to continue using your code? Add an open source license to it, even if the employer removes it later.
Somehow, I think that there may be a reason this won't work.
The poster probably saw the chart, as they seem to have actually read the article in addition to merely glancing at a picture on the last page. Right below that graph:
But under the best of conditions, hard drives typically top out at 3% by the fifth year. Suffice it to say, the researchers at CMRR are adamant that today's SSDs aren't an order of magnitude more reliable than hard drives.
So you're quoting that SSDs are not 10x more reliable than HDDs. That doesn't exactly prove a point that HDDs are more reliable.
You have obviously not come across the special breed of divalopers that we like to call Updatus Avoidus. Above and beyond the lovable characteristics of your run-of-the-mill divaloper, the Updatus Avoidus can be identified by it's shrill cries that often sound like "Don't patch! *squaaaak* My code will break! *squaaaaak*"
Lately we've also been finding out that many major websites are storing passwords as plain text and are untested against SQL injection. So it's unsurprising that they're also unpatched.
Web servers need to be actively watched, maintained and scanned for vulnerabilities. Just because it's a LAMP server doesn't mean it's rock-solid. The fire-and-forget philosophy does not apply.
The problem is generally far beyond the necessary LAMP or IIS patching: The vulnerabilities you describe are flaws in the site's design and code. You can't patch a stupid divaloper.
Walking away is an option in the implementation phase, sure. If something doesn't work right, you can just pull back and do something else.
The problem is when you get beyond implementation, and the vendor has your data by the naughty bits. You can't just "walk" without walking away from all your data. You think you have an SLA that allows you to walk away with your data? Take a look and see if it defines EXACTLY which format they export it in. Chances are, you've agreed to get a few TB of incomprehensible junk if you break contract.
The problem is that the "employer can't fire you for not doing something illegal" protections are really quite pathetic, especially in at-will states. At best, you can expect to win a couple month's pay after the 2-year court battle and attorney's fees. At worst, you're out the cost of attorneys' fees for both sides, and get nothing to show for it but a spot on the local IT blacklist.
Regardless of the law, the choice is still between a) do what you're told and b) hope you can make your mortgage without a job.
Rejoice, IT people! KingMotley has discovered that there are unlimited opportunities for employment in every job market. If you're not lazy, there are sufficiently-compensating IT jobs for every specialty available ANYWHERE!
If it's all outsourced to the cloud, guess what? *Poof*, no admin! That's the whole point, remember? Outsource anything that requires any skill or training, and keep a help desk flunky around part time to swap out broken mice.
Re:Other uses IBM found for its technology
on
IBM Turns 100
·
· Score: 2
You must have missed the part where IBM's wholly owned subsidiaries in Germany and Poland operated closely with the Nazi regime to design, create, and maintain the various census and camp-tracking systems.
Agreed. For MMO gaming, I haven't found anything that can beat the Naga. It takes a few days to get used to, but after the initial muscle memory is created you're golden. My only complaint is the ergonomics, since my hand doesn't quite fit right with the pinky-rest on the right.
You stated that " Stack Overflow does a far better job of getting quality answers these days," which was immediately followed by an assertion that EE is obsolete. The only logical conclusion to your statements is that you believe EE to be obsolete because of Stack Overflow.
My only question is regarding how Stack Overflow makes EE obsolete when EE is only comprised of about 10% programming topics.
Oh, and in what part of the world does someone need clarification on what Exchange means in this context?
Well the working directory for tcpip.sys is C:\Windows\System32\drivers. etc\hosts is accessed from that same directory. Oh yeah, and it has the same basic format, too. As does etc\services. And etc\protocol(s). And etc\networks.
I don't think that it's a happy coincidence.
So, where is the Exchange section on StackOverflow? What about Cisco? A cursory glance at the category for those two nets ~500 combined results, with almost all of them being related to C#, Java, or VB.net.
/etc/hosts is also in Windows, but it's hidden down in the windows directory as c:\Windows\system32\drivers\etc\hosts.
Fun fact: tcpip.sys used to be mostly BSD code.
Did anyone else notice that they used a football as their central "pod" for the ship in the article's graphic? It looks like a bad copy/paste job involving circa 1998 Bryce 3D, MS Paint, and a TI-83.
I couldn't agree more. I first moved to XFCE when I was looking for a lighter window manager on an older computer. This was about a year ago, and I haven't looked back. Everything just works, and failing that, is fairly simple to configure. No godawful semi-maintained nigh-mandatory extensions lists, no configurator-cum-registry, no fighting with dozens of default helper services. It's just... functional. Is that too much to ask?
I have a few too many business degrees and miscellaneous related credentials, so I have some clue what I'm talking about.
The GP is right on this one. Technical and other professional workers are generally to be left to their own devices. Micromanagement is only to be used on those with little experience and job knowledge, or specific cases of a problem employee. This has been thoroughly studied and well-known in the (educated) business community for decades.
Sexual orientation: pedophile.
Wow, you seriously just went for that, didn't you? Take it a step further. Don't hire men, because they're all alcoholics and rapists.
Wow 50 million PS3s? Increase that by another 50% and it's getting close to the number of Blackberry subscribers...
Which is, what, about 1.5% of cell phones?
You forgot the person that was electrocuted in Edison's new "Electric Chair" as the final demonstration of the "evil" of AC power. Yeah, it took him like 8 minutes to die as he was slowly cooking from the inside and screaming like a banshee.
If the software was never publicly published, it wasn't really open source software to begin with. You release early and you release often, also for these sort of things.
He released it to himself. I wonder if that is enough? If so, there are some strange implications for anyone coding for a living. Want to have rights to continue using your code? Add an open source license to it, even if the employer removes it later. Somehow, I think that there may be a reason this won't work.
The poster probably saw the chart, as they seem to have actually read the article in addition to merely glancing at a picture on the last page. Right below that graph:
So you're quoting that SSDs are not 10x more reliable than HDDs. That doesn't exactly prove a point that HDDs are more reliable.
You have obviously not come across the special breed of divalopers that we like to call Updatus Avoidus. Above and beyond the lovable characteristics of your run-of-the-mill divaloper, the Updatus Avoidus can be identified by it's shrill cries that often sound like "Don't patch! *squaaaak* My code will break! *squaaaaak*"
Lately we've also been finding out that many major websites are storing passwords as plain text and are untested against SQL injection. So it's unsurprising that they're also unpatched.
Web servers need to be actively watched, maintained and scanned for vulnerabilities. Just because it's a LAMP server doesn't mean it's rock-solid. The fire-and-forget philosophy does not apply.
The problem is generally far beyond the necessary LAMP or IIS patching: The vulnerabilities you describe are flaws in the site's design and code. You can't patch a stupid divaloper.
Walking away is an option in the implementation phase, sure. If something doesn't work right, you can just pull back and do something else.
The problem is when you get beyond implementation, and the vendor has your data by the naughty bits. You can't just "walk" without walking away from all your data. You think you have an SLA that allows you to walk away with your data? Take a look and see if it defines EXACTLY which format they export it in. Chances are, you've agreed to get a few TB of incomprehensible junk if you break contract.
The problem is that the "employer can't fire you for not doing something illegal" protections are really quite pathetic, especially in at-will states. At best, you can expect to win a couple month's pay after the 2-year court battle and attorney's fees. At worst, you're out the cost of attorneys' fees for both sides, and get nothing to show for it but a spot on the local IT blacklist.
Regardless of the law, the choice is still between a) do what you're told and b) hope you can make your mortgage without a job.
Rejoice, IT people! KingMotley has discovered that there are unlimited opportunities for employment in every job market. If you're not lazy, there are sufficiently-compensating IT jobs for every specialty available ANYWHERE!
Parochial jackass.
Or, it's a set of clustered servers that provide abstracted and elastic resources to guest applications and services.
The more I read your contributions to this story, the more it's becoming apparent that you're either a troll or a shill.
If it's all outsourced to the cloud, guess what? *Poof*, no admin! That's the whole point, remember? Outsource anything that requires any skill or training, and keep a help desk flunky around part time to swap out broken mice.
You must have missed the part where IBM's wholly owned subsidiaries in Germany and Poland operated closely with the Nazi regime to design, create, and maintain the various census and camp-tracking systems.
IBM: Let's build a smarter oven.
Agreed. For MMO gaming, I haven't found anything that can beat the Naga. It takes a few days to get used to, but after the initial muscle memory is created you're golden. My only complaint is the ergonomics, since my hand doesn't quite fit right with the pinky-rest on the right.
You stated that " Stack Overflow does a far better job of getting quality answers these days," which was immediately followed by an assertion that EE is obsolete. The only logical conclusion to your statements is that you believe EE to be obsolete because of Stack Overflow. My only question is regarding how Stack Overflow makes EE obsolete when EE is only comprised of about 10% programming topics. Oh, and in what part of the world does someone need clarification on what Exchange means in this context?
Well the working directory for tcpip.sys is C:\Windows\System32\drivers. etc\hosts is accessed from that same directory. Oh yeah, and it has the same basic format, too. As does etc\services. And etc\protocol(s). And etc\networks. I don't think that it's a happy coincidence.
Stackoverflow is for codemonkeys. It's useless for system, network, and storage administrators.
If there's a great alternative to EE that would, for example, have info on Microsoft Exchange, Cisco routers, and CLARiiON systems, I'm all ears.
So, where is the Exchange section on StackOverflow? What about Cisco? A cursory glance at the category for those two nets ~500 combined results, with almost all of them being related to C#, Java, or VB.net.
You're a subscriber.
Nope.
/etc/hosts is also in Windows, but it's hidden down in the windows directory as c:\Windows\system32\drivers\etc\hosts. Fun fact: tcpip.sys used to be mostly BSD code.
Right now, you can just scroll down. No trickery needed, even on IE.