Untill battery tech can offer me a smartphone that lasts a week of average use I'll be sticking with a "dumbphone". Having used a smartphone for a year and then reverted to a dumbphone it was nice to be able to neglect plugging it in every night and not having to worry about it dropping dead midday.
I would tend to agree more with the article linked below. Human traders have little or no input into trades nowadays, the big money is in high frequency trading on the margins, when this programs go wrong the impact is quite massive.
http://www.ritholtz.com/blog/2010/05/high-speed-trading-glitch/
Get a job in a bank or insurance company. They'll train you in and you should be up on your own as an operator in about a year. Its really not to complicated. Only cavet is its mostly shift work, people don't tend to last long at it and don't stay with it for more than 10 years unless they really love working nights. The trick is to get good enough as a mere operator to get into consulating, thats where the real fun stuff is and the money
I'm 24 and work in the banking and insurance industry. I spend most of my day looking at green text on a black screen and its not going to change anytime soon. We have two big hulking IBM zseries mainframes running batch jobs all night. We also have a good few servers running unisys, unicentre and techscheduler. I know by far I prefer OPC running on the mainframes, if something breaks its just a bit of bad code or input from inhouse. The hardware itself just never gives any trouble. The users don't care what is running on the background, we have csi's running against cics sessions so all they see is a nice little website with no clue what going on in the background and they shouldn't care anyway. Noones going to go to the expense of replacing all the cobol in the background as long as IBM keeps developing and supporting mainframes. They just work.
Would this be useful? "Eleven months later and it looks like the British team have found their answer. In results just published in the journal Plasma Physics and Controlled Fusion, they have devised a system no bigger than a large desk that uses the same energy as an electric kettle." Read more: http://www.universetoday.com/20671/ion-shield-for-interplanetary-spaceships-now-a-reality/#ixzz2GqilqIy1
Untill battery tech can offer me a smartphone that lasts a week of average use I'll be sticking with a "dumbphone". Having used a smartphone for a year and then reverted to a dumbphone it was nice to be able to neglect plugging it in every night and not having to worry about it dropping dead midday.
I would tend to agree more with the article linked below. Human traders have little or no input into trades nowadays, the big money is in high frequency trading on the margins, when this programs go wrong the impact is quite massive. http://www.ritholtz.com/blog/2010/05/high-speed-trading-glitch/
Get a job in a bank or insurance company. They'll train you in and you should be up on your own as an operator in about a year. Its really not to complicated. Only cavet is its mostly shift work, people don't tend to last long at it and don't stay with it for more than 10 years unless they really love working nights. The trick is to get good enough as a mere operator to get into consulating, thats where the real fun stuff is and the money
I'm 24 and work in the banking and insurance industry. I spend most of my day looking at green text on a black screen and its not going to change anytime soon. We have two big hulking IBM zseries mainframes running batch jobs all night. We also have a good few servers running unisys, unicentre and techscheduler. I know by far I prefer OPC running on the mainframes, if something breaks its just a bit of bad code or input from inhouse. The hardware itself just never gives any trouble. The users don't care what is running on the background, we have csi's running against cics sessions so all they see is a nice little website with no clue what going on in the background and they shouldn't care anyway. Noones going to go to the expense of replacing all the cobol in the background as long as IBM keeps developing and supporting mainframes. They just work.