Having grown up next to a Danish first oil then coal powerplant, I can testify that some of the plants are actually dismantled while other have been converted to running on gas. One side effect of this was that many workers lost their jobs as a modern gas driven plant can be run by way fewer people.
I believe the housewives of the town are happy though. When I was a kid they were always complaining that their laundry hanging outside for drying was getting dirty by the smoke from the powerplant and the dust from the trucks driving the slag away.
The expression 'world fastest kayak' is somewhat like 'world fastest running shoes'. Race kayaking is all about the motor and to a much lesser degree about the kayak.
It makes much more sense to speak about the water resistance of various kayak designs. For some given athlete(balance skills, strength and technique) racing some given distance in some given conditions one could even speak of an optimal design. As a general example - the kayaks used for sprint racing are different from the kayaks used for marathon racing.
RSS feeds for high traffic websites lige slashdot is only semi interesting.
However for low traffic/low volume blogs/discussion fora RSS really shines. No I don't want to manually check these sites every day.
While some discussion fora support sending a mail when a new topic is created(http://newsboard.unclassified.de/ being one of them) - I find this to be too intrusive.
It seems to me that the most crucial skills of a good programmer aren't even mentioned the article - the social skills.
When working in a group it's the productivity of the group that counts - not the amount of code that a single member can dish out. And to a large degree I find the group productivity to be unrelated to the individual coding skills of its members.
A good programmer helps develop an atmosphere where:
It's encouraged to ask for and give help.
It's encouraged to ask and give design advices.
It's encouraged to be proud of something clever you made, demonstrate it at the whiteboard and expect your fellow developers to listen.
It's encouraged to criticize the work of others in a positive way.
A bad programmer then? The guy sitting in the corner who thinks he's a genius(and accordingly don't need no help from anyone) and don't want to admit he's been stuck with the same problem for days. I have zero patience for such wizkids.
Slashdot Mirror
Having grown up next to a Danish first oil then coal powerplant, I can testify that some of the plants are actually dismantled while other have been converted to running on gas. One side effect of this was that many workers lost their jobs as a modern gas driven plant can be run by way fewer people.
I believe the housewives of the town are happy though. When I was a kid they were always complaining that their laundry hanging outside for drying was getting dirty by the smoke from the powerplant and the dust from the trucks driving the slag away.
The expression 'world fastest kayak' is somewhat like 'world fastest running shoes'. Race kayaking is all about the motor and to a much lesser degree about the kayak.
It makes much more sense to speak about the water resistance of various kayak designs. For some given athlete(balance skills, strength and technique) racing some given distance in some given conditions one could even speak of an optimal design. As a general example - the kayaks used for sprint racing are different from the kayaks used for marathon racing.
On a related note genetic algorithms have been applied to the problem of finding an optimal hull given a number of constraints: http://www.cyberiad.net/library/kayaks/racing/raci ng.htm
Nothing revolutionary turned out though.
RSS feeds for high traffic websites lige slashdot is only semi interesting.
/Peter
However for low traffic/low volume blogs/discussion fora RSS really shines. No I don't want to manually check these sites every day.
While some discussion fora support sending a mail when a new topic is created(http://newsboard.unclassified.de/ being one of them) - I find this to be too intrusive.
When working in a group it's the productivity of the group that counts - not the amount of code that a single member can dish out. And to a large degree I find the group productivity to be unrelated to the individual coding skills of its members.
A good programmer helps develop an atmosphere where:
- It's encouraged to ask for and give help.
- It's encouraged to ask and give design advices.
- It's encouraged to be proud of something clever you made, demonstrate it at the whiteboard and expect your fellow developers to listen.
- It's encouraged to criticize the work of others in a positive way.
A bad programmer then? The guy sitting in the corner who thinks he's a genius(and accordingly don't need no help from anyone) and don't want to admit he's been stuck with the same problem for days. I have zero patience for such wizkids.Of cause I'm just your average XP hippie...