An APEGBC survey reports that in British Columbia in 2002 the average salary for computer engineers was $81,254 CAD and for EEs this was $89,308. [Today US$/CA$ =.8551] Seems there are lots of jobs in Vancouver, Calgary, Ottawa, Toronto, Waterloo... Check Craig's List/Monster to see.
What about the internal, projects-specific code-naming of chips? I've heard of them being named after locations, rivers, greek gods, ski-runs, etc. How do you code-name your chips/projects?
It seems MS is in the practise of guilty until proven innocent by their bug-ridden WGA process. My dell OEM windows install fails their WGA process and their support isn't any help, they want me to back everything up and re-install from the CD, which is packed away in storage somewhere.
"The current install on your computer as identified correctly by WGA does not match your Windows license. Your current installation of Windows is not legitimate. You will not be able to validate until you perform the repair installation."
With milestones and deadlines and such who has time for this... It took me over 4 hours to secure XP and the last thing I want to do is have to mess with this. I run a couple Linux boxes with and keep XP on my laptop... If I could replace Visio, Word and camera SW I would be 100% Linux.
Dia and OpenOffice aren't quite good enough yet, but are getting closer all the time:)
Makes sense but your RAM drive is then limited to the speed of your interface rather than the access speed of the RAM or CPU bus. What you mention is certianly way simpler than what I'm talking, but I was thinking in terms of super-high speed accesses. I'm chip designer and don't really know what I'm talking about when it comes to databases.
Gamma rays will kill RAM contents... anyone know how resilient HDs are to these? Various error correction schemes/circuits can be used to limit these effects (as others have discussed).
You're restricted to 4Gig with a 32bit bus... the 64bit variety for > 4G... and big RAMs aren't that cheap!
The memory management/corruption problem could be avoided if the RAM were put on a separate data bus and controlled explicitly by some sort of a SQL controller with exclusive access to the RAM. Perhaps a chip with a processor for codeable memory indexing algorithms and a shmit load of RAM might be useful in the future.
Slashdot Mirror
Canada is not a socialist country and it has a pretty damn good economy. Here is a graph of the Toronto Stock Exchange vs. the S&P500. By your metric, if Canada is Socialist then almost every western country other than the US must be too. Checkout The Economist's factsheet for Canada. Also, Canada has the second largest oil reserves in the world.
An APEGBC survey reports that in British Columbia in 2002 the average salary for computer engineers was $81,254 CAD and for EEs this was $89,308. [Today US$/CA$ = .8551] Seems there are lots of jobs in Vancouver, Calgary, Ottawa, Toronto, Waterloo... Check Craig's List/Monster to see.
What about the internal, projects-specific code-naming of chips? I've heard of them being named after locations, rivers, greek gods, ski-runs, etc. How do you code-name your chips/projects?
It seems MS is in the practise of guilty until proven innocent by their bug-ridden WGA process. My dell OEM windows install fails their WGA process and their support isn't any help, they want me to back everything up and re-install from the CD, which is packed away in storage somewhere. "The current install on your computer as identified correctly by WGA does not match your Windows license. Your current installation of Windows is not legitimate. You will not be able to validate until you perform the repair installation." With milestones and deadlines and such who has time for this... It took me over 4 hours to secure XP and the last thing I want to do is have to mess with this. I run a couple Linux boxes with and keep XP on my laptop... If I could replace Visio, Word and camera SW I would be 100% Linux. Dia and OpenOffice aren't quite good enough yet, but are getting closer all the time :)
Makes sense but your RAM drive is then limited to the speed of your interface rather than the access speed of the RAM or CPU bus. What you mention is certianly way simpler than what I'm talking, but I was thinking in terms of super-high speed accesses. I'm chip designer and don't really know what I'm talking about when it comes to databases.
Gamma rays will kill RAM contents... anyone know how resilient HDs are to these? Various error correction schemes/circuits can be used to limit these effects (as others have discussed). You're restricted to 4Gig with a 32bit bus... the 64bit variety for > 4G... and big RAMs aren't that cheap! The memory management/corruption problem could be avoided if the RAM were put on a separate data bus and controlled explicitly by some sort of a SQL controller with exclusive access to the RAM. Perhaps a chip with a processor for codeable memory indexing algorithms and a shmit load of RAM might be useful in the future.