Shouldn't we be preparing for the worse yet? Instead of deciding whether or not it's really happening ? Always a good idea to prepare for the worse.
Whe know it is happening. We know the reasons. What upsets me most about the discussion is that people stick stubbornly to stupid and inefficient technologies and habits. If we prepare for the worse we'll have to develop technology which is robust, smart (not necessarily high-tech), and efficient in terms of energy-consumption. Had we started on that earlier we'd now have less of a problem.
yeah, in the early days of this planet there were years which were damn hot.
I think you take the word 'ever' a bit too serious. It is overstating, but we can be quite shure about the last couple of hundred years.
While I will agree with nearly all of it, the one point that MAY be wrong is that this is man-made. It is possible for this to be a natural phenomenon. Now, with that said, I would rather err on the side of caution and assume that this is man-made and at least try to back out our damage. The claim that the current climate change may not be man-made always sounds funny to me. I've never heard a scientist over here (germany) claim that in recent years. One difference between the current change and previous changes is that it affects both hemispheres, whereas previous changes (ice-ages, for example) seem to have affected either the southern or the northern hemisphere.
Well, you might say that an xxl-sized shirt fits all, but only if you say that if you can get in, it fits you. For most of my s-uses, postgres offers far more than I need (still, postgres is my default).
I use it. Vi (or better: vim) is really sweet if you have to look at textfiles of >100mb. Also, if you have to edit a file on a different machine.
On the other hand, when working in a graphical environment anyway or as a suggestion to new users, I often recommend kate.
Right, the money is in the treatment. That's why they would be happy to cure cancer. The reason simply is that people who die on cancer just die to early. You can earn much more money on old people and their diseases.
Some years ago a swiss insurance company made the math: Who is more profitable in health-insurance, smokers or non-smokers? definitely the smokers, they die early on cheap cancer and don't cause all the cost old people cause. And many of them die while still paying full rate.
>Foreign keys don't speed anything up, they just add an extra layer of checks on your database.
Right, they even make the dbms slower. But the dbms certainly does it faster than the application you write. So, to rely on the checks being made in the application results in a waste of speed on the application side. If I don't care about the speed in the application, why make a fuss about the speed of the rdbms? By the way: I rather have things reliable than fast.
Subselects are something I also heavily use (and thus mainly stay away from MySQL) although I think it's better to use views for queries performed more than once in a while.
Probably one of the main reasons for the spread of MySQL is the fact that is is frequently pre-installed.
Foreign keys are more than nice, they are essential. Unless, maybe you don't care about the integrity of your data or want to make the necessary checks in their application. The latter should keep their eyes down and their mouth shut if the talk is about 'speed' of any rdbms, off course.
Another aspect (and often even cheaper) is the simple fact that they should be treated with respect. This is true for all employees. Simple matters of politeness and fairnes. If then you give them a reason to be loyal (no, it's not about the salary) you've evoided much trouble.
If on the other hand you play games on your employees, they will fight back. I can't even blame them on that.
Ever thought of the power, a Secretary has? Most of (her/his) Bosses Information first go through the hands of the Secretary. The secretary can pass information earlier or later, can spread rumors or give information to other companies. Those people, which managers tend to treat as invisible have far more power than you think.
On balance, if I like the team I'm working with, I prefer working in the cube farm.According to my personal experience, the most efficient team-size is up to five. If you group your teams in offices, there is no need for cubes. Big pro of non-cube: you see where the noise comes from. I find that less disturbing/hate producing. Having your teams in offices, a good placement of coffemaker and xerox machine makes inter-team communication easier. Corridor-drums are very efficient.
Well, I'm rather ignorant if it comes to Physics (No idea what a Van De Graff generator is) but when it comes to sparks and old tv-parts then I have probably played with more than 40.000 volt. Lucky me that I didn't know it.;-)
OK, congrats that this seems to have worked. But a teen experimenting at home with 40.000 volt and Deuterium - am I the only one who thinks this is frightening?
Shure, everybody wants highly qualified programmers. But looking for the superstars might be the wrong idea.
In the last 'further training'-class I did, there were a number of newbies with a non-IT-background and also quite a number of well trained and skilled and experienced professionals. Guess who finished the final project with the best result? A team of newbies who had worked as architect, linguist, etc. The key obviously was that they had the best cooperation. The skilled guys proved to be competetive divas and some of their teams didn't even finish the project.
Conclusion? Find well skilled people with a team-spirit that fit into or improve the existing team.
Who won the war? you did, if you are American (or french, or Russian, or British...) Thanks for that.
Who wrote the constitution? you did not. you gave your ok maybe, but you did not write it.
Slashdot Mirror
Instead of deciding whether or not it's really happening ?
Always a good idea to prepare for the worse.
Whe know it is happening. We know the reasons. What upsets me most about the discussion is that people stick stubbornly to stupid and inefficient technologies and habits. If we prepare for the worse we'll have to develop technology which is robust, smart (not necessarily high-tech), and efficient in terms of energy-consumption. Had we started on that earlier we'd now have less of a problem.
yeah, in the early days of this planet there were years which were damn hot.
I think you take the word 'ever' a bit too serious. It is overstating, but we can be quite shure about the last couple of hundred years.
Well, you might say that an xxl-sized shirt fits all, but only if you say that if you can get in, it fits you. For most of my s-uses, postgres offers far more than I need (still, postgres is my default).
I have the HP-ad here, advertising the integration of OpenSource with Linux. Not bad either.
Well, it happens that I have to make little changes here and there...
Correction:
"Idha khatabahum eljahiluna qalu salama" Oh, I've only seen it transcribed like this. I'll check your correction, thanks.
I use it. Vi (or better: vim) is really sweet if you have to look at textfiles of >100mb. Also, if you have to edit a file on a different machine. On the other hand, when working in a graphical environment anyway or as a suggestion to new users, I often recommend kate.
Right, the money is in the treatment. That's why they would be happy to cure cancer. The reason simply is that people who die on cancer just die to early. You can earn much more money on old people and their diseases. Some years ago a swiss insurance company made the math: Who is more profitable in health-insurance, smokers or non-smokers? definitely the smokers, they die early on cheap cancer and don't cause all the cost old people cause. And many of them die while still paying full rate.
Oh yes, I'd also be happy to get one. Perfect for traveling on trains.
>Foreign keys don't speed anything up, they just add an extra layer of checks on your database. Right, they even make the dbms slower. But the dbms certainly does it faster than the application you write. So, to rely on the checks being made in the application results in a waste of speed on the application side. If I don't care about the speed in the application, why make a fuss about the speed of the rdbms? By the way: I rather have things reliable than fast. Subselects are something I also heavily use (and thus mainly stay away from MySQL) although I think it's better to use views for queries performed more than once in a while. Probably one of the main reasons for the spread of MySQL is the fact that is is frequently pre-installed.
Foreign keys are more than nice, they are essential. Unless, maybe you don't care about the integrity of your data or want to make the necessary checks in their application. The latter should keep their eyes down and their mouth shut if the talk is about 'speed' of any rdbms, off course.
Another aspect (and often even cheaper) is the simple fact that they should be treated with respect. This is true for all employees. Simple matters of politeness and fairnes. If then you give them a reason to be loyal (no, it's not about the salary) you've evoided much trouble. If on the other hand you play games on your employees, they will fight back. I can't even blame them on that.
Ever thought of the power, a Secretary has? Most of (her/his) Bosses Information first go through the hands of the Secretary. The secretary can pass information earlier or later, can spread rumors or give information to other companies. Those people, which managers tend to treat as invisible have far more power than you think.
In the press-release there is no mention of still bargaining with Microsoft. Clearly, free (libre) Software is what the decision is about. (see http://www.assemblee-nationale.fr/presse/divisionp resse/m01.asp#TopOfPage)
On balance, if I like the team I'm working with, I prefer working in the cube farm.According to my personal experience, the most efficient team-size is up to five. If you group your teams in offices, there is no need for cubes. Big pro of non-cube: you see where the noise comes from. I find that less disturbing/hate producing. Having your teams in offices, a good placement of coffemaker and xerox machine makes inter-team communication easier. Corridor-drums are very efficient.
Well, I'm rather ignorant if it comes to Physics (No idea what a Van De Graff generator is) but when it comes to sparks and old tv-parts then I have probably played with more than 40.000 volt. Lucky me that I didn't know it. ;-)
OK, congrats that this seems to have worked. But a teen experimenting at home with 40.000 volt and Deuterium - am I the only one who thinks this is frightening?
Shure, everybody wants highly qualified programmers. But looking for the superstars might be the wrong idea. In the last 'further training'-class I did, there were a number of newbies with a non-IT-background and also quite a number of well trained and skilled and experienced professionals. Guess who finished the final project with the best result? A team of newbies who had worked as architect, linguist, etc. The key obviously was that they had the best cooperation. The skilled guys proved to be competetive divas and some of their teams didn't even finish the project. Conclusion? Find well skilled people with a team-spirit that fit into or improve the existing team.
I'm talking about the constitution of FRG. Wanna see the list of original authors? ckeck here: http://de.wikipedia.org/wiki/Liste_der_Teilnehmer_ des_Verfassungskonvents_auf_Herrenchiemsee
To say that 'you' wrote it is historically wrong. Period.
Who won the war? you did, if you are American (or french, or Russian, or British...) Thanks for that. Who wrote the constitution? you did not. you gave your ok maybe, but you did not write it.
Among the very first Linux installations was the computer of the Mayor (Christian Ude). He's very happy with it, so they'll for shure continue.
I am worried. 'real fire'? How virtual must your reality be to shout 'real fire'?
well, in terms of numbers (of languages), even "european language" would be no match
Yeah, good to see there is a chance for me to get filthy rich.