When Newton(along with Leibniz) invented calculus, Was he doing physics or math? He used that new MATH to explain physical phenomena, does it belong to Math then?
I think your taxonomy could be rewritten as follows:
Science: Physics
Uses: MATH
Engineering:....
Science: Computer Science
Uses: MATH , LOGIC
Engineering:....
It's true that the Computer Science departments have born from Math departments, by the way. But they became adults a long time ago.
Computer science gives you the basic elements to become a computer scientist I.E. to research and expand the limits of current knowledge in computer design and architecture, languages, compilers, models of computation, artificial intelligence (not a la steven spielberg, of course), network design and architecture, processing of images & sounds, data mining, etc
Thirld world nations like mine (Argentina), in general are considered not very favorable to the free market (see heritage index freedom). This view often neglects the not so free markets policies that first world countries apply:
The U.S. Agricultural Department is required by law to subsidize over two dozen commodities. Between 1996 and 2002, an average of $16 billion/year was paid by programs authorized by federal legislation dating back to the Agricultural Adjustment Act of 1933, the Agricultural Act of 1949, and the Commodity Credit Corporation, among others.
If the US and Europe removed their farm subsidies, the value of African food exports would double. According to Oxfam estimates, protectionism in rich countries costs the developing world £60bn a year. The organisation cites the example of sugar. Under the current regime of quotas and high tariffs, Europe's sugar prices are set at almost three times world market levels. Each year, European consumers and taxpayers foot the bill, of roughly £1bn, while developing countries - encouraged to liberalise their markets under IMF/World Bank strictures - suffer the consequences.
But there's no language in the world that works with data as well as FP."
Well, some people hate it http://www.dbdebunk.com/index.html, but SQL is far more powerful than FP, if you agree that declarative languages are better suited to the task of manipulating data.
FP is a clone of dbase, which had nice features to handle data only if you compare it to a bare C API.
SQL is the most popular implementation (definitely not the best or purest) of tuple relational calculus.
Finally, speed is not related to a particular language but to its implementation. How a query is carried out is the task of the Query optimizer http://en.wikipedia.org/wiki/Query_optimizer. I don't know anything about rushmore technology, but I don't think it goes beyond the query optimizer concepts that predates that technology by several years.
And then choose a language and become proficient at it.
In my University, I was taught general concepts: structures, recursion, iteration, abstractions, conditions, logic, programming paradigms, etc., never tied to a specific language. In fact, we used to use a pseudo-language to express solutions to problems.
Real languages (Pascal, X86 assembler, basic, fortran, C, Java, C++, scheme, SQL) were used only in lab practices. It was pre-supposed that you already knew them or you had the basic concepts to learn them.
Whenever I see that someone has been taught an specific language at the university (sometimes a whole semester!), I tend to think that this person will not be able to fullfil his/her position, because he/she has been taugth an specific technology instead of knowledge. It's like a doctor that has been taught how to operate certain medical device instead of how the human body works.
Learn principles and then you'll be able to tell which language is the best at the job.
And as a nice side effect, you'll always be able to catch up with whatever shows up in the ever changing madness of IT.
by WhiplashII (542766) Alter Relationship on Thursday September 28, @10:07AM (#16228655)
International law (you know, the thing that applies to the US but no one else) says that a nation owns only 100 miles up, and beyond that they can lay no claims.
In University, I was taught general concepts: structures, recursion, iteration, abstractions, conditions, Logic and programming paradigms, never tied to a specific language. In fact, we used a pseudo-language to express the solution to a problem.
Using languages belonged to lab practices.
Pascal, X86 assembler, basic, fortran, C, scheme, SQL, you name it.
Learn principles, you'll be able to tell which language is right for the job.
And you'll always be able to catch up with whatever shows up in the ever changing madness of IT.
The Doomsday argument (DA) is a probabilistic argument that claims to predict the future lifetime of the human race given only an estimate of the total number of humans born so far.
It was first proposed by the astrophysicist Brandon Carter in 1983 and was subsequently championed by the philosopher John Leslie. It has since been independently discovered by J. Richard Gott and Holger Bech Nielsen. Similar theories predicting an end to the world from population statistics were proposed earlier by Heinz von Foerster, among others.
This article introduces the Doomsday argument in four ways:
* For a description of the DA without mathematics see the analogy-to-cricket section.
* For a very simplified numerical example, partially based on Korb's refutation[1] see the two-case section.
* For a general overview, with numerical examples see the next section.
* For Gott's mathematical development of the Bayesian argument (using simple calculus) see the Vague Prior section.
"The process is time-consuming. For the Mondex project, spec-writing took nearly a year, or about 25 percent of the entire development process. That was a long time to go without producing anything that looks like a payoff, concedes Andrew Calvert, Mondex's information technology liaison for the project. "Senior management would say: 'We are 20 percent into the project and we're getting nothing. Why aren't we seeing code? Why aren't we seeing implementation?' " he recalls. "I had to explain that we were investing much more than usual in the initial analysis, and that we wouldn't see anything until 50 percent of the way through." For comparison, in most projects, programmers start writing code before the quarter-way mark."
Isn't suposed that one has to give something working to the user and then correct any mistakes made?
The parent post was moderated as 5-insightful the first time, then 4, and for now, 3. Ops, now returning from preview is 2!!
It should have been moderated as OPTIMISTIC.
It gives no reasons or arguments proving or disproving the claim. That's not insightful.
"I worked with a major oil company for 2 years trying to develop a way to commercialize oil shale. Trust me on this, it ain't going to happen. Most oil companies know this. The few (one??) that don't are totally deluded.
Oil shale is not oil. Oil shale is rock that has a relatively high concentration of organic carbon compounds in it. Geologists call this a source rock. If you heat this shale to 700 degrees F you will turn this organic carbon (kerogen) into the nastiest, stinkiest, gooiest, pile of oil-like crap that you can imagine. Then if you send it through the gnarliest oil refinery on the planet you can make this shit into transportation fuel. In the mean time you have created all kinds of nasty by products, have polluted the air and groundwater of where ever you have extracted it. You have also created an enormous pile of superheated rock that will take hundreds to thousands of years to cool off."
It's news because it's turning into a giant datawhorehousing these days...
I disagree.
It is a well known fact that Telcos' DWs are the biggest ones.
I worked for a Telco in Argentina. Their DW has 1.500 millon records for long-distance calls per year and 700 millon records for local calls... per month.
I can't even imagine that number for an say american Telco. Even for an Indian or Chinese one.
Each call is associated with a name, of course.
Even they know when is the most probable time to call to offer you something, based on your calling pattern.
Slashdot Mirror
I think your taxonomy could be rewritten as follows:
Science: Physics ....
Uses: MATH
Engineering:
Science: Computer Science
Uses: MATH , LOGIC
Engineering:....
It's true that the Computer Science departments have born from Math departments, by the way. But they became adults a long time ago.
Computer science gives you the basic elements to become a computer scientist I.E. to research and expand the limits of current knowledge in computer design and architecture, languages, compilers, models of computation, artificial intelligence (not a la steven spielberg, of course), network design and architecture, processing of images & sounds, data mining, etc
It's just marketing from Apple. It intentionally positioned its computers as expensive/exclusive devices.
http://en.wikipedia.org/wiki/Agricultural_subsidie s
United States
The U.S. Agricultural Department is required by law to subsidize over two dozen commodities. Between 1996 and 2002, an average of $16 billion/year was paid by programs authorized by federal legislation dating back to the Agricultural Adjustment Act of 1933, the Agricultural Act of 1949, and the Commodity Credit Corporation, among others.
http://www.newstatesman.com/200506200001
If the US and Europe removed their farm subsidies, the value of African food exports would double. According to Oxfam estimates, protectionism in rich countries costs the developing world £60bn a year. The organisation cites the example of sugar. Under the current regime of quotas and high tariffs, Europe's sugar prices are set at almost three times world market levels. Each year, European consumers and taxpayers foot the bill, of roughly £1bn, while developing countries - encouraged to liberalise their markets under IMF/World Bank strictures - suffer the consequences.
Look how you've been modded. Now it's 3.
Another poster got a 4 right away saying that the cause of this horrible situation was that the government didn't allow people to carry guns openly.
Maybe the people in USA actually likes guns and feel entitled to carry them.
Well, some people hate it http://www.dbdebunk.com/index.html, but SQL is far more powerful than FP, if you agree that declarative languages are better suited to the task of manipulating data.
FP is a clone of dbase, which had nice features to handle data only if you compare it to a bare C API.
SQL is the most popular implementation (definitely not the best or purest) of tuple relational calculus.
Finally, speed is not related to a particular language but to its implementation. How a query is carried out is the task of the Query optimizer http://en.wikipedia.org/wiki/Query_optimizer. I don't know anything about rushmore technology, but I don't think it goes beyond the query optimizer concepts that predates that technology by several years.
In my University, I was taught general concepts: structures, recursion, iteration, abstractions, conditions, logic, programming paradigms, etc., never tied to a specific language. In fact, we used to use a pseudo-language to express solutions to problems.
Real languages (Pascal, X86 assembler, basic, fortran, C, Java, C++, scheme, SQL) were used only in lab practices. It was pre-supposed that you already knew them or you had the basic concepts to learn them.
Whenever I see that someone has been taught an specific language at the university (sometimes a whole semester!), I tend to think that this person will not be able to fullfil his/her position, because he/she has been taugth an specific technology instead of knowledge. It's like a doctor that has been taught how to operate certain medical device instead of how the human body works.
Learn principles and then you'll be able to tell which language is the best at the job.
And as a nice side effect, you'll always be able to catch up with whatever shows up in the ever changing madness of IT.
International law (you know, the thing that applies to the US but no one else) says that a nation owns only 100 miles up, and beyond that they can lay no claims.
Are you the same guy that wrote the above quote?
There is another thing regarding efficiency:
In Brazil, they harvest sugar cane twice a year. They have a proper climate the whole year.
Begginers should learn how to think, instead.
In University, I was taught general concepts: structures, recursion, iteration, abstractions, conditions, Logic and programming paradigms, never tied to a specific language. In fact, we used a pseudo-language to express the solution to a problem.
Using languages belonged to lab practices.
Pascal, X86 assembler, basic, fortran, C, scheme, SQL, you name it.
Learn principles, you'll be able to tell which language is right for the job.
And you'll always be able to catch up with whatever shows up in the ever changing madness of IT.
Since when Data Mining and OLAP belongs to the AI field?
As far as I know those technologies belong to BI (Business Intelligence).
Someone has mixed up some terms.
TFA is about "Global Temperature Trends" and "Mean"
First, the take-off. Then a few nice circles around some buildings and finally a safe landing.
Please.
http://en.wikipedia.org/wiki/Doomsday_argument
From Wikipedia, the free encyclopedia.
The Doomsday argument (DA) is a probabilistic argument that claims to predict the future lifetime of the human race given only an estimate of the total number of humans born so far.
It was first proposed by the astrophysicist Brandon Carter in 1983 and was subsequently championed by the philosopher John Leslie. It has since been independently discovered by J. Richard Gott and Holger Bech Nielsen. Similar theories predicting an end to the world from population statistics were proposed earlier by Heinz von Foerster, among others.
This article introduces the Doomsday argument in four ways:
* For a description of the DA without mathematics see the analogy-to-cricket section.
* For a very simplified numerical example, partially based on Korb's refutation[1] see the two-case section.
* For a general overview, with numerical examples see the next section.
* For Gott's mathematical development of the Bayesian argument (using simple calculus) see the Vague Prior section.
I don't know how could you use Z to validate a specification with your final users unless they have a CS degree.
Use cases are semi-formal as Alistair Cockburn puts it. And that's a real advantage.
A combination of use cases, mock interfaces, prototyping and interpreting user requeriments (based on one's experience) are my best tools.
From the IEEE article:
"The process is time-consuming. For the Mondex project, spec-writing took nearly a year, or about 25 percent of the entire development process. That was a long time to go without producing anything that looks like a payoff, concedes Andrew Calvert, Mondex's information technology liaison for the project. "Senior management would say: 'We are 20 percent into the project and we're getting nothing. Why aren't we seeing code? Why aren't we seeing implementation?' " he recalls. "I had to explain that we were investing much more than usual in the initial analysis, and that we wouldn't see anything until 50 percent of the way through." For comparison, in most projects, programmers start writing code before the quarter-way mark."
Isn't suposed that one has to give something working to the user and then correct any mistakes made?
The moderator doesn't have firm opinions about the parent post.
The parent post was moderated as 5-insightful the first time, then 4, and for now, 3. Ops, now returning from preview is 2!! It should have been moderated as OPTIMISTIC. It gives no reasons or arguments proving or disproving the claim. That's not insightful.
"I worked with a major oil company for 2 years trying to develop a way to commercialize oil shale. Trust me on this, it ain't going to happen. Most oil companies know this. The few (one??) that don't are totally deluded.
Oil shale is not oil. Oil shale is rock that has a relatively high concentration of organic carbon compounds in it. Geologists call this a source rock. If you heat this shale to 700 degrees F you will turn this organic carbon (kerogen) into the nastiest, stinkiest, gooiest, pile of oil-like crap that you can imagine. Then if you send it through the gnarliest oil refinery on the planet you can make this shit into transportation fuel. In the mean time you have created all kinds of nasty by products, have polluted the air and groundwater of where ever you have extracted it. You have also created an enormous pile of superheated rock that will take hundreds to thousands of years to cool off."
I disagree.
It is a well known fact that Telcos' DWs are the biggest ones.
I worked for a Telco in Argentina. Their DW has 1.500 millon records for long-distance calls per year and 700 millon records for local calls ... per month.
I can't even imagine that number for an say american Telco. Even for an Indian or Chinese one.
Each call is associated with a name, of course.
Even they know when is the most probable time to call to offer you something, based on your calling pattern.
No big news here.