Those are all things I did as a CS undergrad, but there was also huge importance put on proofs. Everyone is talking about writing good code doing useful things quickly, but (and this is especially important in real time applications, such as autopilot on planes), if you can't prove that the code you have written is going to do what you want 100% of the time or its not 100% accurate, then really what is its worth.
Maths is vital (ok not if your connecting up a website, although it does have applications in scaling and databases) and should be being used in the design phase even before the programming starts, that way people might be able to cut out buggy crappy software.
I'm not sure how many people on my course got to grips with it, not many I think as most of then changed over to software engineering in our final year. I know I never did and I regret it.
Slashdot Mirror
Is this the same sort of light that was seen above Norway not long ago?
http://news.bbc.co.uk/1/hi/world/europe/8406633.stm
Robots is interesting with a bit of AI thrown in too.
But also have a look at http://diybio.org/ for some biology related projects
Guess my minesweeper time is going to be wiped as soon as that page, the shame.
don't want to be antagonistic but..... (499*1.175)/1.468 = 399.40 so you're both wrong.
"Enhance....Enhance" "Just print the damn thing!" "Enhance.."
....how are they going to know who's driving the car and then who to issue the tickets too?
I definitely owe at least half my degree to my people skills, rather than to my academic ones.
CS actually makes this really easy to do.....
Fair point, but how do you know its working on your machine? If one part of an algorithm is spitting out the wrong answer the whole thing is flawed
Those are all things I did as a CS undergrad, but there was also huge importance put on proofs. Everyone is talking about writing good code doing useful things quickly, but (and this is especially important in real time applications, such as autopilot on planes), if you can't prove that the code you have written is going to do what you want 100% of the time or its not 100% accurate, then really what is its worth. Maths is vital (ok not if your connecting up a website, although it does have applications in scaling and databases) and should be being used in the design phase even before the programming starts, that way people might be able to cut out buggy crappy software. I'm not sure how many people on my course got to grips with it, not many I think as most of then changed over to software engineering in our final year. I know I never did and I regret it.
I don't understand why the break-even time on solar has to be on the order of a handful of years for it to be economically feasible.
because often the life span on solar is not that long (relatively).