One of the reasons I don't play multiplayer PvP type games anymore is because I don't have the time to play continuously, only now and then. So I don't have the skills that 14 year olds who do nothing but play all day (and who have all the lastest exploits and robot hacks running), who do nothing but trash talk and rnu around blasting everything that moved.
So to sum it up: I go there for enjoyment, not to listen to crap and get 'powned' by L33T uber hackers without a life. Probably the vast majority of FPS players feel the same way.
I've been coding since 1970, I think I've probably written more than my fair share of code. I've also designed circuits and other hardware devices (I started in Robotics).
The problem is something like 80 percent of all software programmers have never been exposed to any kind of engineering course in their lives, know nothing about how to design or build stuff, and probably 50 percent of them don't even have a degree in a related field! (I work at a fortune 500 company and I think only 20 percent of the programers here have college degrees in CS, and this is pretty much the standard in silicon valley).
My comparison is apt because whether you are building a bridge, a circuit board, a chip, or anything, the same rules apply. You design it first, you look at your design, you test your design, then you build it, then you check your finished product. Unlike 99 percent of programmers out there who just start writing code without a clear design in their head. Any monkey can write code, writing code is -simple-. It's the design of the program and the system that is the hard part, and that design should be -completely- fleshed out before the first line of code is even generated.
I've worked on tactical nuclear bombers. Haven't seen us accidentally NUKE anyone in the last twenty years have you? No I know a lot about writing code, because I'm an expert in the field. People put up with crappy code and crappy programmers because they don't know any better. But as in all fields this will change with time, once the people keeping the books realize you do in fact get what you pay for.
The real difference between the engineer building a suspension bridge and a large scale software project is one of complexity and resourcing. Software developers are building much more complex systems in a much shorter period of time and with much less in the way of resources. That's why corners are cut, because our clients demand it.
Building said bridge is a lot more difficult than coding anything you can think of. Because you can always rewrite your code and patch it. You only get -one- chance to build your bridge. People are much more lackadasical about writing code because they can make changes whenever they want, and even then most coders rarely ever test any of their stuff. It's the old joke of the Engineer and the Programmer riding in a car all over again.
Ah yes, good old rationalization. You're a non-techinical manager, aren't you? By your logic then when I worked on those strategic weapon systems years back, if I made a mistake and a lot of people died, well, who cares? They outlived thier original planned lifetimes anyway.
Other industries do better than this, stop making excuses for poor management at NASA.
What is really needed is to get RID of Computer SCIENCE and move it over to the Engineering department and give us Computer ENGINEERING. Scientists don't build stuff, they investigate things, they don't -care- about better ways to build things, better ways to avoid mistakes, it's not their job. Engineers however are all about building the same damn bridge 100 times and making it better and safer each time.
There is no discipline in Computer Programming these days, because Computer Programmers don't know how to engineer stuff. The simplest program is done differently by every programmer where if engineers were doing it they'd all be taught to do it the exact same way. Standardization is how you get rid of most errors. You'll notice that nobody is making new bolts or nails anymore, they're all standardized.
I tell you, you see all these ridiculous failures at NASA, it's pretty obvious that they either don't do QA, or that the QA teams are literally hamstrung. These things are the stuff that good QA and Test programs find, making people check bolts on a tilt table before ruining a 50 millon dollar satellite are what process and checklists are all about.
These aren't 'normal workplace errors' that you have to live with, they're -stupid- errors, made because of stupid managers.
Dont waste your money. Nokia is not technically competant to get the software right, and has a lot of problems with hardware development. Then there is the fact that their support SUCKS, and that they treat their customers like crap.
I bought a 770, I spent a lot of money to buy one and what is nokia doing to me? Screwing me royally. There will be no further updates, and the current software has as many bugs in it as the original release. Many releases of code had even more. Nokia themselves aren't even writing code anymore, it's a bunch of amateurs who aren't very good at it, Nokia gave up on actually having their people write code over six months ago, and even then they had maybe one programmer working on it.
Then there is the complete lack of any programs that will do anything you want to do. Text editors? Nope! anything that works with any MS program out there? Nope. Blue tooth devices? Nope. USB? Nope.
The list goes on and on and on. Save your money, pony up the extra cash for any MS windows CE based device. If I had done that instead of buying the 770 I would be ahead of the game, because now I have a worthless 350 dollar device that isn't even a year old!!!!
I will never buy anything by Nokia again. They sold me a piece of shit that they knew was shit, and now they're abandoning all of their early adopters.
Nokia so endeared all of the early adopters of the 770 by dropping all support of the platform and screwing all those customers out of the 300 to 400 dollars they spent. Do you really think they'll treat the people who buy the 800 any better?
The 770 was plagued by poor code, a lot of bugs, updates that had even more bugs than the code it was patching, no customer support and hardware that was broken fresh out of the box at least 50 percent of the time. In short nokia ran a beta test on the market and made the people pay for it, and then offered them nothing in return but a pretty worthless peice of crap.
Anything with windows CE in it is a better option (as much as it pains me to say it), because then youhave something that will actually work with other devices. This was a good idea, but Nokia doesn't have the technical know how, or programming experience to bring it to market. So don't waste your money.
Maybe he just reads Business Week a lot and finds their articles interesting and so he comments on them in these forums. There are -a lot- of people who really only read one news source and then spread what they see there all over the place.
And if he is working for Business week and being paid to do this, so what? Slashdot has editors and -they- are the filter/gate through which all articles must pass. If they don't approve it, it doesn't get posted. This isn't a site like digg where just anyone can post an article to the webpage.
There is actually a big difference between 'kill' and 'murder'. Killing someone in a war is still killing, but it is not murder. Killing someone in self-defense is still killing, but it is not murder.
That's why the semantic difference is important. Under the ten commandments there are times you can kill, and still be okay in God's eyes.
Because once we start sending 'only robots' like you want, you'll then move on to 'why are we wasting money on this? It's not like we're going to send people!' Just remember, that if a robot had been flying the Eagle, it would have crashed on the moon. Armstrong had to override the system and manually land it because the 'robot' was about to crash it into a boulder.
I've used the sims back in my AF days. They're really not that bad and can give you a lot of experience in dealing with the kinds of things you won't usually experience, as well as helping you get used to the more mundane tasks involved with flying. The only major differences are that: 1) Landings in a simulator are not really like real landings. They're close, but not exact. (This is because simulators are limited in the amount of force they can apply). 2) Your sensation of Aircraft motion in certain flight regimes is not the same. This is because a simulator cannot simulate actual centrifical effects (G Forces) or weightlessness which can cause confusion in a pilot.
Of course this is in the better simulators. Cheaper simulators have even more limitations. But even the expensive ones are still cheaper than an actual aircraft for training.
And Christian arrogance teaches you that your god is the correct god, while all the other thousands of gods and goddesses in the history of the human species are just silly fantasies.
Dude, if he didn't believe that his God is the correct God, why would he worship him? Your own arrogance is really only outshined by the absolute stupidity of your reply.
Women entered the work force during (and after) WWII (early 40's). And the higher tax rates following the war really helped to keep them there. Prior to WWII the average person had little to do with taxation. (And I'm not even going to get into the 16th amendment never having been ratified argument).
But after WWII taxation on the average person increased drastically (like your '54 tax rate quote shows) also there were a lot more things people wanted to buy (like housing, cars, TV's) that there hadn't been a demand for previously. I still believe that if there was a major tax drop (like switching over to a 5 percent flat tax), we'd see a lot of women leaving the work force and not returning. Because economically, both members of a couple wouldn't have to work to be able to afford the things they want.
Really, wages did not fall; taxes increased. Look at the tax load these days (~30 percent) and the tax load then. Also look at how much more people buy these days versus those days.
But if you had a sudden wage increase of what you pay in taxes, you could easily afford to not have both people work.
Noise canceling headsets can damage your ears. The sound pressure in a loud environment is still there, even if you can't hear it. If you are in a loud environment, one loud enough to damage your hearing, wear earplugs!!!
So while turning up the power on the headset will make the noise you can hear 'go away' the damage is still being done.
There are a lot of places out there, though they sell the camera bodies bare bones. If you don't need the battery or charger or av cables it's a good deal.
Slashdot Mirror
One of the reasons I don't play multiplayer PvP type games anymore is because I don't have the time to play continuously, only now and then. So I don't have the skills that 14 year olds who do nothing but play all day (and who have all the lastest exploits and robot hacks running), who do nothing but trash talk and rnu around blasting everything that moved.
So to sum it up: I go there for enjoyment, not to listen to crap and get 'powned' by L33T uber hackers without a life. Probably the vast majority of FPS players feel the same way.
I've been coding since 1970, I think I've probably written more than my fair share of code. I've also designed circuits and other hardware devices (I started in Robotics).
The problem is something like 80 percent of all software programmers have never been exposed to any kind of engineering course in their lives, know nothing about how to design or build stuff, and probably 50 percent of them don't even have a degree in a related field! (I work at a fortune 500 company and I think only 20 percent of the programers here have college degrees in CS, and this is pretty much the standard in silicon valley).
My comparison is apt because whether you are building a bridge, a circuit board, a chip, or anything, the same rules apply. You design it first, you look at your design, you test your design, then you build it, then you check your finished product. Unlike 99 percent of programmers out there who just start writing code without a clear design in their head. Any monkey can write code, writing code is -simple-. It's the design of the program and the system that is the hard part, and that design should be -completely- fleshed out before the first line of code is even generated.
I've worked on tactical nuclear bombers. Haven't seen us accidentally NUKE anyone in the last twenty years have you? No I know a lot about writing code, because I'm an expert in the field. People put up with crappy code and crappy programmers because they don't know any better. But as in all fields this will change with time, once the people keeping the books realize you do in fact get what you pay for.
That we're all wishing we'd taken business courses and gotten jobs as brokers on wallstreet instead of our fancy technical degrees! :-)
I mean, who knew? I wish someone had told me about his back in High School, stupid guidence counseler!!
Building said bridge is a lot more difficult than coding anything you can think of. Because you can always rewrite your code and patch it. You only get -one- chance to build your bridge. People are much more lackadasical about writing code because they can make changes whenever they want, and even then most coders rarely ever test any of their stuff. It's the old joke of the Engineer and the Programmer riding in a car all over again.
Ah yes, good old rationalization. You're a non-techinical manager, aren't you? By your logic then when I worked on those strategic weapon systems years back, if I made a mistake and a lot of people died, well, who cares? They outlived thier original planned lifetimes anyway.
Other industries do better than this, stop making excuses for poor management at NASA.
What is really needed is to get RID of Computer SCIENCE and move it over to the Engineering department and give us Computer ENGINEERING. Scientists don't build stuff, they investigate things, they don't -care- about better ways to build things, better ways to avoid mistakes, it's not their job. Engineers however are all about building the same damn bridge 100 times and making it better and safer each time.
There is no discipline in Computer Programming these days, because Computer Programmers don't know how to engineer stuff. The simplest program is done differently by every programmer where if engineers were doing it they'd all be taught to do it the exact same way. Standardization is how you get rid of most errors. You'll notice that nobody is making new bolts or nails anymore, they're all standardized.
I tell you, you see all these ridiculous failures at NASA, it's pretty obvious that they either don't do QA, or that the QA teams are literally hamstrung. These things are the stuff that good QA and Test programs find, making people check bolts on a tilt table before ruining a 50 millon dollar satellite are what process and checklists are all about.
These aren't 'normal workplace errors' that you have to live with, they're -stupid- errors, made because of stupid managers.
Dont waste your money. Nokia is not technically competant to get the software right, and has a lot of problems with hardware development. Then there is the fact that their support SUCKS, and that they treat their customers like crap.
I bought a 770, I spent a lot of money to buy one and what is nokia doing to me? Screwing me royally. There will be no further updates, and the current software has as many bugs in it as the original release. Many releases of code had even more. Nokia themselves aren't even writing code anymore, it's a bunch of amateurs who aren't very good at it, Nokia gave up on actually having their people write code over six months ago, and even then they had maybe one programmer working on it.
Then there is the complete lack of any programs that will do anything you want to do. Text editors? Nope! anything that works with any MS program out there? Nope. Blue tooth devices? Nope. USB? Nope.
The list goes on and on and on. Save your money, pony up the extra cash for any MS windows CE based device. If I had done that instead of buying the 770 I would be ahead of the game, because now I have a worthless 350 dollar device that isn't even a year old!!!!
I will never buy anything by Nokia again. They sold me a piece of shit that they knew was shit, and now they're abandoning all of their early adopters.
Nokia so endeared all of the early adopters of the 770 by dropping all support of the platform and screwing all those customers out of the 300 to 400 dollars they spent. Do you really think they'll treat the people who buy the 800 any better?
The 770 was plagued by poor code, a lot of bugs, updates that had even more bugs than the code it was patching, no customer support and hardware that was broken fresh out of the box at least 50 percent of the time. In short nokia ran a beta test on the market and made the people pay for it, and then offered them nothing in return but a pretty worthless peice of crap.
Anything with windows CE in it is a better option (as much as it pains me to say it), because then youhave something that will actually work with other devices. This was a good idea, but Nokia doesn't have the technical know how, or programming experience to bring it to market. So don't waste your money.
Maybe he just reads Business Week a lot and finds their articles interesting and so he comments on them in these forums. There are -a lot- of people who really only read one news source and then spread what they see there all over the place.
And if he is working for Business week and being paid to do this, so what? Slashdot has editors and -they- are the filter/gate through which all articles must pass. If they don't approve it, it doesn't get posted. This isn't a site like digg where just anyone can post an article to the webpage.
There is actually a big difference between 'kill' and 'murder'. Killing someone in a war is still killing, but it is not murder. Killing someone in self-defense is still killing, but it is not murder.
That's why the semantic difference is important. Under the ten commandments there are times you can kill, and still be okay in God's eyes.
Contrary to your belief, Comedy films do not accurately portray American History.
Also, Stripes is not an accurate depiction of the US Army either. Just FYI.
I rest my case.
We'd still be in Europe.
Because once we start sending 'only robots' like you want, you'll then move on to 'why are we wasting money on this? It's not like we're going to send people!'
Just remember, that if a robot had been flying the Eagle, it would have crashed on the moon. Armstrong had to override the system and manually land it because the 'robot' was about to crash it into a boulder.
I've used the sims back in my AF days. They're really not that bad and can give you a lot of experience in dealing with the kinds of things you won't usually experience, as well as helping you get used to the more mundane tasks involved with flying. The only major differences are that:
1) Landings in a simulator are not really like real landings. They're close, but not exact. (This is because simulators are limited in the amount of force they can apply).
2) Your sensation of Aircraft motion in certain flight regimes is not the same. This is because a simulator cannot simulate actual centrifical effects (G Forces) or weightlessness which can cause confusion in a pilot.
Of course this is in the better simulators. Cheaper simulators have even more limitations. But even the expensive ones are still cheaper than an actual aircraft for training.
Wow, talk about a signal to noise ratio.
I was calling your reply stupid, but after seeing this from you I suspect that maybe I should have called you stupid as well.
Actually it says: "Thou shalt not commit murder"
Which is completely different.
Dude, if he didn't believe that his God is the correct God, why would he worship him? Your own arrogance is really only outshined by the absolute stupidity of your reply.
Um, dude, we as a race are just not that powerful. Sorry to burst your bubble there.
Women entered the work force during (and after) WWII (early 40's). And the higher tax rates following the war really helped to keep them there. Prior to WWII the average person had little to do with taxation. (And I'm not even going to get into the 16th amendment never having been ratified argument).
But after WWII taxation on the average person increased drastically (like your '54 tax rate quote shows) also there were a lot more things people wanted to buy (like housing, cars, TV's) that there hadn't been a demand for previously. I still believe that if there was a major tax drop (like switching over to a 5 percent flat tax), we'd see a lot of women leaving the work force and not returning. Because economically, both members of a couple wouldn't have to work to be able to afford the things they want.
Really, wages did not fall; taxes increased. Look at the tax load these days (~30 percent) and the tax load then. Also look at how much more people buy these days versus those days.
But if you had a sudden wage increase of what you pay in taxes, you could easily afford to not have both people work.
I have. And few work perfectly at this time, so there is an effect on your ears.
Wow, so much for trying to warn people about ruining their hearing.
Noise canceling headsets can damage your ears. The sound pressure in a loud environment is still there, even if you can't hear it. If you are in a loud environment, one loud enough to damage your hearing, wear earplugs!!!
So while turning up the power on the headset will make the noise you can hear 'go away' the damage is still being done.
There are a lot of places out there, though they sell the camera bodies bare bones. If you don't need the battery or charger or av cables it's a good deal.