I think you missed the point. You don't own the battery, your power-provider does.
It becomes their problem to ensure that spent batteries are appropriately down-cycled from the system... and that is what makes this idea beautiful.
I've been developing software for the medical industry (diagnostics and therapeutics) for eight years, much of that using ObjectiveC under OpenStep.
I'd certainly be interested in discussing contract work of this type.
I once worked at a device company that was in a similar position. When the business changed direction and we determined that we needed regulatory approval, it took us two years of paper pushing to get ourselves prepared.
Doing it right the first time can be the difference between being the first and the third into a market.
I have used SourceNavigator several times to become familiar with a new code-base. The interface is a bit awkward, but a few minutes with the manual will leave you with a very valuable tool.
My favourite feature... the X-ref tool which gives you a navigable/expandable reference tree. Windows -> Add View -> Editor and you are good to go.
I believe this is a critical point of discussion and one that is lost on most students entering University. Pure Computer Science revolves around development of solutions to well constrained and highly technical problems. Improving routing, devising optimal peer-to-peer algorithms, rapid search algorithms, etc.
Good CS programs (predominantly math and science based) focus on these skills. These programs DO NOT teach how to develop complex systems, because that is Engineering and there is a separate faculty for that. However, the common understanding is that CS == application development and this is a fallacy.
The result of this confusion is many many students entering the wrong program and complaining when it is too hard... they wanted to be code mechanics not mathematicians. Usually, the program begins to soften, further blurring the lines and you end up with CS grads who can neither build a system nor solve an algorithmic problem.
What industry needs is MANY well-trained Computer Engineers and a very few, extremely talented Computer Scientists.
As a fourth generation Canadian, I too have met a large number of Canadians. While I have no intention of defending the AC, I resent the absurd generalization that Canadians are uneducated and racist. With any large sampling of people, you will encounter the good and the bad. I am sorry to discover that you have clearly encountered only the bad, yet you are a sample of one.
I work at a company with fifteen employees, representing eight distinct nationalities and we operate in perfect harmony. This place is not anomalous; I have lived through several similar situations at other companies.
Does this trend pose difficulties? Certainly. However, were such a policy not embraced by the majority of Canadians, it certainly would not persist. The tolerance is real. Join us and see for yourself.
Here's another pretty cool design. I used to live near things guy. He consistently comes up with weird and wonderful things.
http://www.williamlishman.com/underground.htm
He also happens to be the "real" person behind the Fly Away Home story.
http://www.canoe.ca/JamMoviesToronto96/sep8_flyawa y.html
I agree completely,
With its support for numerical analysis (and similarities with Matlab-y constructs) it is ideal for algorithm prototyping and in some cases even algorithm deployment.
I certainly turn to Python first, rather than coding up new ideas in c++.
This argument just doesn't seem constructive to me.
When I'm looking to hire a programmer, I'm looking for one thing. Adaptability.
In my job, I've used C++, Objective-C, COM, C#, Lisp and Python. The theme here is utility. I try to use the best, most natural language for the task at hand.
I don't need to work beside evangalists, I want people who see programming languages as what they are... components in a toolbox. You choose the one appropriate for the job.
I think the problem is that Software Development != Computer Science.
90% of the jobs out there are development positions. These require basic programming skills, understanding of the newest buzz technology and an eye for asthetics.
10% of the jobs are computer science jobs. These usually entail designing/optimizing algorithms or interfacing with "sciency" types like engineers(gasp), physicists and chemists.
A good COMPUTER SCIENCE degree is designed to prepare you for 10% category. If what you want to do is build java apps and database applications then go to college and learn those skills instead of all of the theory involved in a CS degree.
Slashdot Mirror
I'll second the endorsement for powder ... I was playing it on my netbook on the way to work today.
I think you missed the point. You don't own the battery, your power-provider does. ... and that is what makes this idea beautiful.
It becomes their problem to ensure that spent batteries are appropriately down-cycled from the system
I've been developing software for the medical industry (diagnostics and therapeutics) for eight years, much of that using ObjectiveC under OpenStep. I'd certainly be interested in discussing contract work of this type.
Kelly.
I once worked at a device company that was in a similar position. When the business changed direction and we determined that we needed regulatory approval, it took us two years of paper pushing to get ourselves prepared.
Doing it right the first time can be the difference between being the first and the third into a market.
I have used SourceNavigator several times to become familiar with a new code-base. The interface is a bit awkward, but a few minutes with the manual will leave you with a very valuable tool.
... the X-ref tool which gives you a navigable/expandable reference tree. Windows -> Add View -> Editor and you are good to go.
My favourite feature
Kel.
I believe this is a critical point of discussion and one that is lost on most students entering University. Pure Computer Science revolves around development of solutions to well constrained and highly technical problems. Improving routing, devising optimal peer-to-peer algorithms, rapid search algorithms, etc.
... they wanted to be code mechanics not mathematicians. Usually, the program begins to soften, further blurring the lines and you end up with CS grads who can neither build a system nor solve an algorithmic problem.
Good CS programs (predominantly math and science based) focus on these skills. These programs DO NOT teach how to develop complex systems, because that is Engineering and there is a separate faculty for that. However, the common understanding is that CS == application development and this is a fallacy.
The result of this confusion is many many students entering the wrong program and complaining when it is too hard
What industry needs is MANY well-trained Computer Engineers and a very few, extremely talented Computer Scientists.
As a fourth generation Canadian, I too have met a large number of Canadians. While I have no intention of defending the AC, I resent the absurd generalization that Canadians are uneducated and racist. With any large sampling of people, you will encounter the good and the bad. I am sorry to discover that you have clearly encountered only the bad, yet you are a sample of one.
I work at a company with fifteen employees, representing eight distinct nationalities and we operate in perfect harmony. This place is not anomalous; I have lived through several similar situations at other companies.
However, I am also a sample of one. Let us look at statistics. Immigration accounted for two-thirds of Canada's population growth in 2006/2007 (http://www.statcan.ca/Daily/English/070927/d070927a.htm/) and has always been a significant contributor to our population (http://www40.statcan.ca/l01/cst01/demo03.htm?sdi=population%20growth/).
Does this trend pose difficulties? Certainly. However, were such a policy not embraced by the majority of Canadians, it certainly would not persist. The tolerance is real. Join us and see for yourself.
http://www.williamlishman.com/underground.htm
He also happens to be the "real" person behind the Fly Away Home story.a y.html
http://www.canoe.ca/JamMoviesToronto96/sep8_flyaw
I certainly turn to Python first, rather than coding up new ideas in c++.
When I'm looking to hire a programmer, I'm looking for one thing. Adaptability.
In my job, I've used C++, Objective-C, COM, C#, Lisp and Python. The theme here is utility. I try to use the best, most natural language for the task at hand. I don't need to work beside evangalists, I want people who see programming languages as what they are ... components in a toolbox. You choose the one appropriate for the job.
-
90% of the jobs out there are development positions. These require basic programming skills, understanding of the newest buzz technology and an eye for asthetics.
-
10% of the jobs are computer science jobs. These usually entail designing/optimizing algorithms or interfacing with "sciency" types like engineers(gasp), physicists and chemists.
A good COMPUTER SCIENCE degree is designed to prepare you for 10% category. If what you want to do is build java apps and database applications then go to college and learn those skills instead of all of the theory involved in a CS degree.