Forgot your password?

typodupeerror

Comment: Re:Inexperienced drivers are inexperienced (Score 3, Interesting) 217

by Capt.Albatross (#40056341) Attached to: Quantifying the Risk of Texting Drivers

Whatever the youth are interested in will be demonized.

As texting while driving is clearly dangerous, this is irrelevant.

The ability to prove exactly how the guy was goofing off is supposed to invoke moral outrage in me.

No, it is the act of putting others in grave danger for no good reason that is considered immoral.

Comment: Commenting vs. Review: A False Dichotomy (Score 1) 188

by Capt.Albatross (#39693797) Attached to: Documentation As a Bug-Finding Tool

Several commentators have said that reviews are better than comments, but this is no argument against commenting, as they are complementary and synergistic activities. I have found in practice that reviews without prior documentation are almost worthless, and generally not cost-effective.

1) Having the author write down an explanation of her code saves the time of half a dozen reviewers trying to figure it out. This, alone, is justification enough for pre-review documenting.

2) The alternative, having the author try to improvise an explanation in a review meeting, and have the reviewers follow along, leads to incorrect assumptions going overlooked or unchallenged, and may degenerate into confusion.

3) As others have pointed out, the author is likely to find some errors as a result of documenting the reasoning behind her work, leading to fewer failed reviews, and consequently, fewer repeats.

4) If the reviewers don't fully understand the whys and what-ifs of the code being reviewed, the exercise degenerates into a search for coding standards violations.

5) Comments, if both relevant and correct, save a lot of time in future whenever that code needs to be understood. While this is not the most important case where this matters, it includes when reviewing changes to that code, and any other work where its correctness is conditional on the prior code. Having the commented code and other documentation being part of reviews helps meet the relevant and correct criteria.

Comment: Re:Indeed (Score 1) 188

by Capt.Albatross (#39693261) Attached to: Documentation As a Bug-Finding Tool

Explaining your work by writing it down is fine, but if noone reads what you have written, it isn't as useful anymore. Hence, it is not the documentation part but rather the reviewing part that helps.

My experience is that when I write out an argument, I quite often notice weaknesses, incompleteness or outright errors that had not occurred to me before, so writing it down is very useful even if no-one else reads it. This is particularly true for nontrivial arguments that have several cases, lemmas etc. Based on what I have seen of other peoples' work, there are quite a few people for who this is so. In short, writing it down forces you to review and allows you to handle complexity.

Righthaven Redux... With a Difference->

Submitted by Capt.Albatross
Capt.Albatross writes "At Boing Boing, Rob Beschizza reports that, in an act of delicious irony, Swiss ISP Ort Cloud [sic] has acquired Righthaven's domain name and has relaunched Righthaven.com as a web hosting service diametrically opposed to the practices of its original owner, a notorious but ultimately unsuccessful copyright troll. The new owners, in partnership with first amendment lawyer Marc Randazza (who was instrumental in the original Rigthhaven's demise), promise "infrajuridsictional infrastructure" — uptime that would require international cooperation to bring down. "Frivolous plaintiffs will find little comfort here" says Ort Cloud's Stefan Thalberg.

The domain name became available in a court-ordered auction of Righthaven LLC's assets, to pay its creditors."

Link to Original Source

Comment: Re:There may be more than is apparent here. (Score 1) 943

by Capt.Albatross (#37929470) Attached to: Theologian Attempts Censorship After Losing Public Debate
Trust a theologian to prefer fanciful ideas which conform to his a priori prejudices, over an alternative which better explains the observations in the light of what is already known. Given Haught's actual engagement in the debate, and his prior endorsement of recording it, it strains one's credibility to believe that he is embarrassed to be caught swatting at gnats. A simple common-sense understanding of human nature, and a shave by William of Ockham (there's a rational theologian for you, at least for one brief moment) leaves embarrassment at being outwitted as the most plausible explanation for his stance, by a wide margin. Of course, it is not entirely plausible that you put much weight in the gnat argument, either. Rather, it looks like a contrived excuse for you to make snide remarks about atheists, just as your first suggestion looks like a contrived excuse for making snide remarks about Catholics. You should note that if it wasn't for a host of theologians using deceitful methods in an attempt to suppress real science, there wouldn't be anyone, neither scientists nor atheists, talking about the issue. The creationism/evolution debate, for rational minds, was settled in the nineteenth century.

Have a taco. -- P.S. Beagle

Working...