As a salaried IT employee of nearly a decade, I have many times considered the bullshit to compensation ratio, and it directly applies to this question. With the bullshit:compensation ratio, each individual is impacted differently. Everybody has a different threshold of bullshit that they will find acceptable. If you are adequately compensated, you may be willing to put up with more bullshit (extra hours in this case) and will be happy with your continued employment. If the bullshit outweighs the compensation, you will be unhappy, and the stresses created will drive you or those around you to make a change. That change could be requesting higher compensation or benefits to level off the bs:comp ratio, or could be initiating your next job hunt.
The bullshit applies to those around you as well. More bullshit could mean your friends see less of you, so you may lose out on those friendships or see them suffer. Or your partner or spouse may have a different level of accepted bullshit than you, and may leave you. Or your children may see less of you and think less of you as a parent (combined with your spouse leaving you, may find an acceptable replacement step-parent). I don't speak from experience on these possibilities, but I've seen them happen.
The solution is to not let the bullshit outweigh the compensation. Seek acceptable compensation to counter the bullshit, at your current employer or at your next one. But whatever you do, don't let the bullshit outweigh the compensation. When that happens, and you accept it, you are lost and must find your way back. It's easier to not get lost in the first place.
From http://www.dricasworld.com/news/101100h9.shtml
Planetweb CEO Ken Soohoo being asked about coding on the PS2 platform...
Q: Seeing that your company has first hand experience, is there any truth to the rumor that the PlayStation2 is a pain to code on?
A: Well, it depends on what you mean by a pain. You know, it's very powerful. It's got a ton of different graphic engines, and graphic paths, and you can do so much with it. It's not like they just loaded up on a giganto CPU and said "Well here you go, isn't this neat?". They have made a lot of custom hardware inside this platform. It means that in order to get the most out of it you're going to really have to dig deep and work hard. That means that the lifetime of this product line will be very long. It means that a year, two years, three years from now, you will still see games that are getting better and better and better as people learn how to make all those paths shine, and work in parallel and all those things they were intended to do by the hardware designers. So frankly, a general purpose CPU is pretty quick. You pound the compiler at it and there you go, you're done. So it really depends on what you mean by difficult. I wouldn't characterize it as difficult. I think a classic games programmer from the last decade and a half of making games is very excited about working on the PlayStation2. It's one of the most imaginative new systems to come out from a hardware architecture perspective. I think that people who entered programming in the last four years are used to "Well, here's the C compiler, let'er rip," and they're not really used to what games used to be, which was custom hardware.
The only game that has a browser built-in right now is Sonic Adventure. The HTTP_USER_AGENT for the Dreamcast is "Mozilla/3.0 (compatible; Planetweb/1.123 JS SSL US Gold; Dreamcast US)", while for Sonic it is "Mozilla/3.0 (SonicKey)". The hostname I scanned was using the Planetweb browser and not the Sonic browser. The fact is that the guy who emailed/. didn't get accurate results. As much as everyone would like to believe it, those ports aren't open.
I checked the http server log for my site (dricasworld.com - complete coverage of the Dreamcast's online capabilities) and got a hostname of a Dreamcast user. Scanned it for open ports and none of those mentioned in the article were open. The guy either blundered and scanned the wrong IP or is full of it.
Slashdot Mirror
As a salaried IT employee of nearly a decade, I have many times considered the bullshit to compensation ratio, and it directly applies to this question. With the bullshit:compensation ratio, each individual is impacted differently. Everybody has a different threshold of bullshit that they will find acceptable. If you are adequately compensated, you may be willing to put up with more bullshit (extra hours in this case) and will be happy with your continued employment. If the bullshit outweighs the compensation, you will be unhappy, and the stresses created will drive you or those around you to make a change. That change could be requesting higher compensation or benefits to level off the bs:comp ratio, or could be initiating your next job hunt.
The bullshit applies to those around you as well. More bullshit could mean your friends see less of you, so you may lose out on those friendships or see them suffer. Or your partner or spouse may have a different level of accepted bullshit than you, and may leave you. Or your children may see less of you and think less of you as a parent (combined with your spouse leaving you, may find an acceptable replacement step-parent). I don't speak from experience on these possibilities, but I've seen them happen.
The solution is to not let the bullshit outweigh the compensation. Seek acceptable compensation to counter the bullshit, at your current employer or at your next one. But whatever you do, don't let the bullshit outweigh the compensation. When that happens, and you accept it, you are lost and must find your way back. It's easier to not get lost in the first place.
Problem solved!
Duct tape. Lots of duct tape. Sticks good on carpet, walls, ceilings, and even pets.
From http://www.dricasworld.com/news/101100h9.shtml
Planetweb CEO Ken Soohoo being asked about coding on the PS2 platform...
Q: Seeing that your company has first hand experience, is there any truth to the rumor that the PlayStation2 is a pain to code on?
A: Well, it depends on what you mean by a pain. You know, it's very powerful. It's got a ton of different graphic engines, and graphic paths, and you can do so much with it. It's not like they just loaded up on a giganto CPU and said "Well here you go, isn't this neat?". They have made a lot of custom hardware inside this platform. It means that in order to get the most out of it you're going to really have to dig deep and work hard. That means that the lifetime of this product line will be very long. It means that a year, two years, three years from now, you will still see games that are getting better and better and better as people learn how to make all those paths shine, and work in parallel and all those things they were intended to do by the hardware designers. So frankly, a general purpose CPU is pretty quick. You pound the compiler at it and there you go, you're done. So it really depends on what you mean by difficult. I wouldn't characterize it as difficult. I think a classic games programmer from the last decade and a half of making games is very excited about working on the PlayStation2. It's one of the most imaginative new systems to come out from a hardware architecture perspective. I think that people who entered programming in the last four years are used to "Well, here's the C compiler, let'er rip," and they're not really used to what games used to be, which was custom hardware.
I pinged the hostname and got a response.
The only game that has a browser built-in right now is Sonic Adventure. The HTTP_USER_AGENT for the Dreamcast is "Mozilla/3.0 (compatible; Planetweb/1.123 JS SSL US Gold; Dreamcast US)", while for Sonic it is "Mozilla/3.0 (SonicKey)". The hostname I scanned was using the Planetweb browser and not the Sonic browser. The fact is that the guy who emailed /. didn't get accurate results. As much as everyone would like to believe it, those ports aren't open.
I checked the http server log for my site (dricasworld.com - complete coverage of the Dreamcast's online capabilities) and got a hostname of a Dreamcast user. Scanned it for open ports and none of those mentioned in the article were open. The guy either blundered and scanned the wrong IP or is full of it.