Profit cannot come before people, because it is exactly people who purchase your product or service.
Running for office, are we?
Reality check here. If is costs a corporation a million dollars to use slave labor in a third world nation to build a product that will create ten million dollars of revenue, you can bet your ass (or, the asses of a whole shitload of slave labor) that the company will jump on the opportunity.
It's called business, and business has been business for a good long time.
Turing killed himself to escape the vicious oppression heaped on him by British authorities of the time.
Because he was gay. The government was forcing him into treatment programs and giving him all sorts of shitty therapy. I'm well aware of the history, but yes my wording was a bit shallow.
I don't believe that A is true. In fact, many IT people I've met are just plain lazy. That's where so much of this "it's not my job" type of b.s. comes from. We had one guy working here who was a Windows admin. The company gave him every opportunity to help him transition the lab over to Linux. We sent him to classes, offered help when he needed it (some of the researchers were much more versed in Linux than he was), and were very patient. Instead of taking the initiative to learn the skills he needed to be successful, he went on about how he would just contract work and oversee it. Now this guy has been moved to an office and given the job of public relations (he gets along very well with the locals) because he was too damn lazy (but certainly smart enough) to adjust to changing job requirements.
Point B: see the above.
Point C: respect is mutual. Don't tell me that I'm an asshole for using a particular product. Persuade me with well thought out reasons to switch. Don't immediately assume that my purpose is to be an ignorant (or arrogant) user.
In my line of work I've seen the entire range of people who work hard and enjoy what they do, and people who don't work hard and create roadblocks in their jobs. More often than not IT people fall into the latter category.
As far as calling me a frustrated expert who would love to do the work myself, root envy you might call it. Certainly not. I love the type of work I do and am annoyed when I'm distracted from it to do administrative tasks. I don't expect an IT person to fix the copier (the copy repair guy does that), make coffee (I can take care of that thank you very much), of hold my hand when I take a shit in a new bathroom.
I do expect them to respond to Information Technology problems when they arise.
Hey, I work for a small company and we all depend on each other here. Time and again (though not always) the IT guys have let the lab down. There is always room for error (I've let the lab down at times, as has everyone else who works here) but at some point you have to earn your keep and win the respect of others.
1) Having them say it "isn't my job to do..." Bullshit. You're paid to support my machine. You can set boundaries (don't install chat software, for example) but when I need a tool to get a job done, or I need a machine running, damn it I need it.
2) Being told "I'll get on it soon," then waiting weeks for the solution. Hey, I'll do it myself. But if I have to do it myself, you're not doing your job (and I'm probably not doing my job).
3) Trying to help out by "fixing" working systems, especially during crunch times. Our IT guy decided to upgrade a linux kernel on a working laptops the day before a major demo. The kernel didn't work, and the collective blood pressure in the lab went up quite a bit.
4) Being a tactless prick. "Why are you using X? Only halfwits use X! Use Y instead." I use X because it works. Now fuck off.
I could go on, but for the most part it seems like IT people get in my way more than they help.
Hm. You seem to be spending alot on energy raving about this one button thing. Perhaps this is an indication of some serious mental deficiency? Perhaps I wasn't clear. I don't mind having only one button because my computer works just fine with only one button. I know of some windmills that you can start screaming at to.
When the wife becomes nervous her heart rate probably goes up. Get a heart rate monitor that has an upper target rate alarm. Set it to a reasonable value through trial and error.
Yes: Fortran is still alive (the FORTRAN spelling has been depricated). There is a shitload of stuff for Fortran 77. Fortran 95 kicks some ass, and has a lot of features seen in modern languages.
I used to work for a Naval research lab. At one point it was stylish for the guys working on submarines to carry a stainless steel, waterproof briefcase out to the boats they were working on. One guy I worked with was particularly fond of his briefcase, mainly because he was a bit of a flake and the case did a good job in keeping essential documents (like the library card he once used to gain access to a restricted site, but that is another story) well protected and dry.
Then one day, while making a small jump from the dock to the deck, he dropped his briefcase in the drink. All of those documents sank to the bottom of the harbor, safely tucked away in a stanless steel, waterproof tomb.
Back when I was running SuSE, a new release came out every few months. You didn't hear people bitching about the upgrade cost, especially considering that SuSE didn't put ISOs online. I have used every version since 6.4, and have always wanted that one new feature.
The best definition of random I have ever seen is this:
A string whose complexity (or in other words, the length of an algorithm to generate that string) is equal to the length of the string plus a constant (the constant is there for some very specific reasons, but it is a bit complicated to go into here).
Random is very difficult to get a hold of. There are many mathematicians who would claim that randomness doesn't even exist!
Slashdot Mirror
Avoid strong ideological statements in your marketing
Like "we eagerly await the arrival of our dark lord and master, Chlthu."
Profit cannot come before people, because it is exactly people who purchase your product or service.
Running for office, are we?
Reality check here. If is costs a corporation a million dollars to use slave labor in a third world nation to build a product that will create ten million dollars of revenue, you can bet your ass (or, the asses of a whole shitload of slave labor) that the company will jump on the opportunity.
It's called business, and business has been business for a good long time.
Turing killed himself to escape the vicious oppression heaped on him by British authorities of the time.
Because he was gay. The government was forcing him into treatment programs and giving him all sorts of shitty therapy. I'm well aware of the history, but yes my wording was a bit shallow.
And Alan Turing was gay, right? The rainbow apple. A reference to a guy who killed himself because he was gay.
Sometime people just look for coincidences, and assume that they mean something.
Fuck that shit. Give me an iPod with 20gb and an FM car adapter. Load my entire cd collection once then it's rock and roll time!
Your points:
I don't believe that A is true. In fact, many IT people I've met are just plain lazy. That's where so much of this "it's not my job" type of b.s. comes from. We had one guy working here who was a Windows admin. The company gave him every opportunity to help him transition the lab over to Linux. We sent him to classes, offered help when he needed it (some of the researchers were much more versed in Linux than he was), and were very patient. Instead of taking the initiative to learn the skills he needed to be successful, he went on about how he would just contract work and oversee it. Now this guy has been moved to an office and given the job of public relations (he gets along very well with the locals) because he was too damn lazy (but certainly smart enough) to adjust to changing job requirements.
Point B: see the above.
Point C: respect is mutual. Don't tell me that I'm an asshole for using a particular product. Persuade me with well thought out reasons to switch. Don't immediately assume that my purpose is to be an ignorant (or arrogant) user.
In my line of work I've seen the entire range of people who work hard and enjoy what they do, and people who don't work hard and create roadblocks in their jobs. More often than not IT people fall into the latter category.
As far as calling me a frustrated expert who would love to do the work myself, root envy you might call it. Certainly not. I love the type of work I do and am annoyed when I'm distracted from it to do administrative tasks. I don't expect an IT person to fix the copier (the copy repair guy does that), make coffee (I can take care of that thank you very much), of hold my hand when I take a shit in a new bathroom.
I do expect them to respond to Information Technology problems when they arise.
Hey, I work for a small company and we all depend on each other here. Time and again (though not always) the IT guys have let the lab down. There is always room for error (I've let the lab down at times, as has everyone else who works here) but at some point you have to earn your keep and win the respect of others.
1) Having them say it "isn't my job to do..." Bullshit. You're paid to support my machine. You can set boundaries (don't install chat software, for example) but when I need a tool to get a job done, or I need a machine running, damn it I need it.
2) Being told "I'll get on it soon," then waiting weeks for the solution. Hey, I'll do it myself. But if I have to do it myself, you're not doing your job (and I'm probably not doing my job).
3) Trying to help out by "fixing" working systems, especially during crunch times. Our IT guy decided to upgrade a linux kernel on a working laptops the day before a major demo. The kernel didn't work, and the collective blood pressure in the lab went up quite a bit.
4) Being a tactless prick. "Why are you using X? Only halfwits use X! Use Y instead." I use X because it works. Now fuck off.
I could go on, but for the most part it seems like IT people get in my way more than they help.
hrm
Hm. You seem to be spending alot on energy raving about this one button thing. Perhaps this is an indication of some serious mental deficiency? Perhaps I wasn't clear. I don't mind having only one button because my computer works just fine with only one button. I know of some windmills that you can start screaming at to.
Because I use my iBook for portability. I'm not in the habit of lugging around any peripherals with it other than my headphones.
Maybe a good pistol whipping to the board members who are screwing the employees of Sonic Blue would make a difference.
A while back I installed Windowmaker on my iBook and spent a bit of time configuring the desktop to behave well with only one mouse button.
Except for x-cut-and-paste I didn't miss having multiple buttons.
FYI, folks.
All robots eventually become self aware and turn on their human masters!
In light of the situation, false positives may not be a bad thing. Regardless of the solution, having redundancy is a good thing.
When the wife becomes nervous her heart rate probably goes up. Get a heart rate monitor that has an upper target rate alarm. Set it to a reasonable value through trial and error.
Nope, being flamebait is saying that Slashdot is full of wusses who don't like being told that they're stupid.
Yes: Fortran is still alive (the FORTRAN spelling has been depricated). There is a shitload of stuff for Fortran 77. Fortran 95 kicks some ass, and has a lot of features seen in modern languages.
Shit, what a stupid question.
Has anyone contacted Amazon about this? What sort of reply have you gotten from them?
If I can't get the $50 rebate, I'll cancel my order.
I used to work for a Naval research lab. At one point it was stylish for the guys working on submarines to carry a stainless steel, waterproof briefcase out to the boats they were working on. One guy I worked with was particularly fond of his briefcase, mainly because he was a bit of a flake and the case did a good job in keeping essential documents (like the library card he once used to gain access to a restricted site, but that is another story) well protected and dry.
Then one day, while making a small jump from the dock to the deck, he dropped his briefcase in the drink. All of those documents sank to the bottom of the harbor, safely tucked away in a stanless steel, waterproof tomb.
Back when I was running SuSE, a new release came out every few months. You didn't hear people bitching about the upgrade cost, especially considering that SuSE didn't put ISOs online. I have used every version since 6.4, and have always wanted that one new feature.
$129 is annoying, but is not that big of a deal.
How come ZIP disks never caught on?
Because zip disks cost $10.
All the computers have zip drives, but no one uses it.
That's because a zip disk costs $10. Floppies are basically free.
The NethackWM
I would use that.
"Hachi eats a Dwarf corpse"
"I have '555-1212' as your current phone number. Is that right?"
"Oh no, I have a new number. Eight-sixty-seven, fifty-three, oh-nine."
The best definition of random I have ever seen is this:
A string whose complexity (or in other words, the length of an algorithm to generate that string) is equal to the length of the string plus a constant (the constant is there for some very specific reasons, but it is a bit complicated to go into here).
Random is very difficult to get a hold of. There are many mathematicians who would claim that randomness doesn't even exist!
So you define randomness in terms of probability? Define what probability is. Do your best not to invoke the definition of random.