http://groups.google.com/group/alt.os.linux.slackware/msg/7ce5765c3900529e?pli=1
Hat Tip - Megan McArdle
Wednesday, December 9, 2009
Sunday, December 6, 2009
First Draft - Science - Idealistic Versus Signaling
This is a rough draft - I just had the idea this morning and spent a little time working on it. Please leave any comments - I am ordering several books which should provide more information - this essay will be further refined - but probably not for at least a month, maybe more, depending on my reading and your feedback.
The responses to the recent leaking of the CRU's information and emails, has led me to a changed understanding of science and how it is viewed by various people, especially people who claim to be scientists.
Among people who actually do or consume science there seem to be two broad views - what they "believe" about science, rather than what they normally "say" about science when asked.
The classical view, what I have begun thinking of as the idealistic view, is science as the search for reliable knowledge. This is the version most scientists (and many non-scientists) espouse when asked, but increasingly many scientists actually hold another view when their beliefs are evaluated by their actions.
This is the signaling and control view of science. This is the "social network" view that has been developed by many sociologists of science.
For an extended example of the two views in conflict, see this recent thread of 369 comments Facts to fit the theory? Actually, no facts at all! . PhysicistDave is the best exemplar of the idealistic view, with pete and several others having extreme signaling and control viewpoints.
I wonder how much of the fact that there hasn't been any fundamental breakthroughs in the last fifty years has to do with the effective takeover of science by academics and government - that is by the signaling and control view. Maybe we have too many "accredited" scientists and they are too beholden to government, and to a lesser extent other grant-making organizations - and they have crowded out or controlled real, idealistic science.
This can also explain the conflict between those who extol peer review, despite its many flaws, and downplay open source science. They are controlling view scientists protecting their turf and power and prerogatives. Anyone thinking about the ideals of science, the classical view of science, immediately realizes that open sourcing the arguments and data will meet the ends of extending knowledge much better than peer review, now that it is possible. Peer review was a stop gap means of getting a quick review of a paper that was necessary when the costs of distributing information was high, but it is now obsolescent at best. Instead the senior scientists and journal editors are protecting their power by protecting peer review.
Bureaucrats, and especially teachers, will tend strongly toward the signaling and control view.
Economics and other social "sciences" will tend toward signaling and control view - for examples see Robin Hanson's and Tyler Cowen's take on the CRU leak with their claims that this is just how academia really works and pete, who claims a Masters in economics, in the comment thread linked above.
Robin Hanson's It's News on Academia, Not Climate
And Tyler Cowen in The lessons of "Climategate",
As I discussed earlier, those who continue to advocate the general use of peer review will tend strongly toward the signaling and control view.
Newer scientists will tend more toward the classical, idealistic view; while more mature scientists as they gain stature and power (especially as they enter administration and editing) will turn increasingly signaling and control oriented.
The responses to the recent leaking of the CRU's information and emails, has led me to a changed understanding of science and how it is viewed by various people, especially people who claim to be scientists.
Among people who actually do or consume science there seem to be two broad views - what they "believe" about science, rather than what they normally "say" about science when asked.
The classical view, what I have begun thinking of as the idealistic view, is science as the search for reliable knowledge. This is the version most scientists (and many non-scientists) espouse when asked, but increasingly many scientists actually hold another view when their beliefs are evaluated by their actions.
This is the signaling and control view of science. This is the "social network" view that has been developed by many sociologists of science.
For an extended example of the two views in conflict, see this recent thread of 369 comments Facts to fit the theory? Actually, no facts at all! . PhysicistDave is the best exemplar of the idealistic view, with pete and several others having extreme signaling and control viewpoints.
I wonder how much of the fact that there hasn't been any fundamental breakthroughs in the last fifty years has to do with the effective takeover of science by academics and government - that is by the signaling and control view. Maybe we have too many "accredited" scientists and they are too beholden to government, and to a lesser extent other grant-making organizations - and they have crowded out or controlled real, idealistic science.
This can also explain the conflict between those who extol peer review, despite its many flaws, and downplay open source science. They are controlling view scientists protecting their turf and power and prerogatives. Anyone thinking about the ideals of science, the classical view of science, immediately realizes that open sourcing the arguments and data will meet the ends of extending knowledge much better than peer review, now that it is possible. Peer review was a stop gap means of getting a quick review of a paper that was necessary when the costs of distributing information was high, but it is now obsolescent at best. Instead the senior scientists and journal editors are protecting their power by protecting peer review.
Bureaucrats, and especially teachers, will tend strongly toward the signaling and control view.
Economics and other social "sciences" will tend toward signaling and control view - for examples see Robin Hanson's and Tyler Cowen's take on the CRU leak with their claims that this is just how academia really works and pete, who claims a Masters in economics, in the comment thread linked above.
Robin Hanson's It's News on Academia, Not Climate
Yup, this behavior has long been typical when academics form competing groups, whether the public hears about such groups or not. If you knew how academia worked, this news would not surprise you nor change your opinions on global warming. I’ve never done this stuff, and I’d like to think I wouldn’t, but that is cheap talk since I haven’t had the opportunity. This works as a “scandal” only because of academia’s overly idealistic public image.
And Tyler Cowen in The lessons of "Climategate",
In other words, I don't think there's much here, although the episode should remind us of some common yet easily forgotten lessons.Of course, both Hanson and Cowen believe in AGW, so these might just be attempts to avoid facing anything they don't want to look at.
As I discussed earlier, those who continue to advocate the general use of peer review will tend strongly toward the signaling and control view.
Newer scientists will tend more toward the classical, idealistic view; while more mature scientists as they gain stature and power (especially as they enter administration and editing) will turn increasingly signaling and control oriented.
Friday, November 27, 2009
Many Ideas or One Idea - or Both
I read Present one idea at a time and let others build upon it after finding it linked in Hacker News. My first response to the title, even before I clicked on the link, was that it was probably going to be a restatement of the amateur SF writer's error of trying to dole out ideas in their stories. Ideas are plentiful, trying to not put them in stories, apparently because they believe there should be only one or a few ideas per story is one reason most amateurs have a hard time writing good science fiction.
On reading the essay, I realized Sivers had an excellent point, but it was a point about feedback. Presenting one idea at a time makes it easier for readers to give good feedback, and they are therefore more likely to provide it.
I wonder if there is any way to combine the two views? To provide more background and context, with the necessarily larger numbers of ideas being presented, while still getting useful feedback from readers.
Added: I linked to this on LW and added this in the comments there:
One idea at a time is great for getting feedback. It is not so good for a reader trying to develop understanding. And the "sequences" don't really help much, trying to read/reread several to try to get context for understanding something is too choppy. I don't know what the best trade-off may be, but I can hope things will improve.
On reading the essay, I realized Sivers had an excellent point, but it was a point about feedback. Presenting one idea at a time makes it easier for readers to give good feedback, and they are therefore more likely to provide it.
I wonder if there is any way to combine the two views? To provide more background and context, with the necessarily larger numbers of ideas being presented, while still getting useful feedback from readers.
Added: I linked to this on LW and added this in the comments there:
One idea at a time is great for getting feedback. It is not so good for a reader trying to develop understanding. And the "sequences" don't really help much, trying to read/reread several to try to get context for understanding something is too choppy. I don't know what the best trade-off may be, but I can hope things will improve.
Labels:
blogging,
creativity,
science fiction,
writing
Thursday, November 5, 2009
Rules Destroys Intelligence
Size alone does not a bureaucracy make, though it always helps (or hurts, looking at it from a rational perspective). Rules exist in the first place to benefit the group and its production. A bureaucrat is someone who has forgotten that simple fact, and worships the rules as ends in themselves, rather than means to getting the job done. This is one reason large organizations are more bureaucratic than smaller ones, the distance of most workers from the actual job.
The ultimate in rule-bound work is automated work.
A Web example:
On September 30 I was reading a well-established post on a web site I generally like, that already had lots of comments. Since it has a [reply] button, I naturally replied to comments that warranted it. I didn't even realize how many I had posted until I had gone back to the homepage and found I had 9 of the top 10 comments. I knew from a discussion a year before that the site owners "would prefer" people not post more than 3 of the latest 10 comments - but that was before one of them left and before the reply button, so I didn't know if it would be a problem, and it really didn't even occur to me as I was replying to those comments.
Apparently it did. On October 11, I tried to comment on a new post, my first comment since the 30th, and got an error page with "You are posting comments too quickly. Slow down." Outstanding stupidity on the part of the web site. What an outstandingly stupid contradiction between the site's name and action.
The ultimate in rule-bound work is automated work.
A Web example:
On September 30 I was reading a well-established post on a web site I generally like, that already had lots of comments. Since it has a [reply] button, I naturally replied to comments that warranted it. I didn't even realize how many I had posted until I had gone back to the homepage and found I had 9 of the top 10 comments. I knew from a discussion a year before that the site owners "would prefer" people not post more than 3 of the latest 10 comments - but that was before one of them left and before the reply button, so I didn't know if it would be a problem, and it really didn't even occur to me as I was replying to those comments.
Apparently it did. On October 11, I tried to comment on a new post, my first comment since the 30th, and got an error page with "You are posting comments too quickly. Slow down." Outstanding stupidity on the part of the web site. What an outstandingly stupid contradiction between the site's name and action.
Friday, October 30, 2009
Innovation and Blogging Software
I don't have anything against innovation - provided it's more useful than the inconsistency it introduces. Tools, including software, are used for other ends, they are not ends in themselves except for a few people who specialize in them, or are otherwise particularly interested in them.
Part of the problem is that different people value different things and, consequently, want different things in their tools. This inevitably introduces complexity, both in the variety of tools available and in the tools themselves.
When browsing the internet and blogs, I am interested in finding interesting or useful content, not in learning to manage a dozen different software systems. There are too many different blogging/commenting systems. For someone interested in finding useful or interesting content rather than in "communing", it is seriously annoying to keep track of how they work.
Standardize somewhat on the blogging/commenting systems. Reducing the number of different systems will lessen the complexity a lot more than adding features to one or another would increase it. Reduce the number of systems by making it easier for current sites to transfer to another system. Reduce forking of projects by making it easy to patch systems to a consistent standard.
Part of the problem is that different people value different things and, consequently, want different things in their tools. This inevitably introduces complexity, both in the variety of tools available and in the tools themselves.
When browsing the internet and blogs, I am interested in finding interesting or useful content, not in learning to manage a dozen different software systems. There are too many different blogging/commenting systems. For someone interested in finding useful or interesting content rather than in "communing", it is seriously annoying to keep track of how they work.
Standardize somewhat on the blogging/commenting systems. Reducing the number of different systems will lessen the complexity a lot more than adding features to one or another would increase it. Reduce the number of systems by making it easier for current sites to transfer to another system. Reduce forking of projects by making it easy to patch systems to a consistent standard.
Labels:
blogging,
creativeness,
design,
programming,
tools,
usability
What Is a Model?
A model is a simplified, abstracted representation of an object or system that presents only the information needed by its user. For example, the plastic models of aircraft I built as a kid abstract away everything except the external appearance, a mathematical model of a system shows only those dimensions and relationships useful to the model's users, a control system is a model of the relationships between the stimuli and the response desired by the designer and user of the larger system being controlled (evolution as designer and organism as user in biological analogy). A control system doesn't make a model of a system, to a large degree it is the designers' model of the system it controls.
At the simplest end are one-dimensional models, that we call measurements.
The most complex models are not explicit, they are too complex to be explicitly known, much less communicated; the model of the world that each person carries within his own mind.
At the simplest end are one-dimensional models, that we call measurements.
The most complex models are not explicit, they are too complex to be explicitly known, much less communicated; the model of the world that each person carries within his own mind.
Labels:
decision making,
design,
futurism,
planning,
problem solving
Thursday, October 29, 2009
The Relationship of Software Engineering, Computer Science, and Programming
Computer science underlies programming rather like physics underlies engineering. You can do some programming or practical engineering with rules of thumb and copying from references, but they will ony take you so far.
What is needed for software engineering to become a reality, rather than a glorified name for programming, is a set of reliable principles for designing and building effective software, that is software that works as expected. Prototyping is the currently most effective way of building software, but it is not software engineering; it is an admission that there is not yet a discipline of software engineering.
From what I have read, even the large scale, high reliability programs are built more by careful programming, testing, and debugging than by detailed up-front design, the way large scale engineering projects are.
The main reason is the incredible complexity of software projects. The only physical products that approach software in complexity are large scale integrated circuits.
Software engineering will be an engineering discipline when the development of a new operating system, the associated utilities, and APIs is as predictable and stable as the design and construction of a new skyscraper.
This is all from general reading and memory, if you agree or disagree with me, please leave links to any sources you may have in comments.
What is needed for software engineering to become a reality, rather than a glorified name for programming, is a set of reliable principles for designing and building effective software, that is software that works as expected. Prototyping is the currently most effective way of building software, but it is not software engineering; it is an admission that there is not yet a discipline of software engineering.
From what I have read, even the large scale, high reliability programs are built more by careful programming, testing, and debugging than by detailed up-front design, the way large scale engineering projects are.
The main reason is the incredible complexity of software projects. The only physical products that approach software in complexity are large scale integrated circuits.
Software engineering will be an engineering discipline when the development of a new operating system, the associated utilities, and APIs is as predictable and stable as the design and construction of a new skyscraper.
This is all from general reading and memory, if you agree or disagree with me, please leave links to any sources you may have in comments.
Subscribe to:
Posts (Atom)