The basic problem is that people (ie managers) assume that one hour is as good as any other hour. The way I work, one hour on Friday may be worth 4 hours on Monday. If you just look at total lines of code commited to CVS. Fridays are by far my most productive days while Mondays are the worst. Which days are the best qualitatively, I have no idea. But something causes Fridays to be my most productive in terms of raw output. This may because there are fewer meetings or because there are fewer interuptions. I have a feeling that I may be able to work 24 hours straight at times and have very good correct output but at other times I only get one good hour of code out of a day. Part of this comes from the fact that coding is a blend of art and science. If I am simply reproducing the same types of solutions over and over again the number of hours has much less of an impact than if I am constantly confronted with problems that I have never solved before. In any case I know that my actual rate of productivity (ie problems solved correctly) is very spotty and comes in spurts. The idea of working 9 to 5 only is an antiquated one. It could be that only accomplish 1 hours of work at the office in a day but solve a weeks work of problems in a couple of hours driving in my car thinking about them.
Why didnt they go after the american services?
on
Sklyarov Indicted
·
· Score: 1
The indictment said ElcomSoft was culpable because it sold the program for $99 in the United States through an online payment service based in Issaquah, Wash., and with a Web site hosted in Chicago.
If Napster is culpable, why arent the "online payment service" and the hosting company culpable?
Slashdot Mirror
The basic problem is that people (ie managers) assume that one hour is as good as any other hour. The way I work, one hour on Friday may be worth 4 hours on Monday. If you just look at total lines of code commited to CVS. Fridays are by far my most productive days while Mondays are the worst. Which days are the best qualitatively, I have no idea. But something causes Fridays to be my most productive in terms of raw output. This may because there are fewer meetings or because there are fewer interuptions. I have a feeling that I may be able to work 24 hours straight at times and have very good correct output but at other times I only get one good hour of code out of a day. Part of this comes from the fact that coding is a blend of art and science. If I am simply reproducing the same types of solutions over and over again the number of hours has much less of an impact than if I am constantly confronted with problems that I have never solved before. In any case I know that my actual rate of productivity (ie problems solved correctly) is very spotty and comes in spurts. The idea of working 9 to 5 only is an antiquated one. It could be that only accomplish 1 hours of work at the office in a day but solve a weeks work of problems in a couple of hours driving in my car thinking about them.
The indictment said ElcomSoft was culpable because it sold the program for $99 in the United States through an online payment service based in Issaquah, Wash., and with a Web site hosted in Chicago.
If Napster is culpable, why arent the "online payment service" and the hosting company culpable?