Pat_Palmer
Forum Participant
 
Posts: 106
|
 |
« Reply #2 on: May 15, 2007, 02:07:07 PM » |
|
Robert,
Let me try to explain the approach I've taken so far, after first stating that I tend to write in an experimental style. So the article as it now stands (if I were writing it alone) would almost certainly change form hugely several times in the process of my working with the material. It seems that a lot of authors are different in their process: they write it once, then never touch it again. That makes me not the easiest of collaborators when authoring; I realize it.
I've been a bit of a bully lately in trying to keep each blurb in the "history of computing" article short. I am concerned about this particular article becoming unmanageably large (60 years of action-packed progress to cover). I consider the article in an experimental stage. My intention has been to, INITIALLY AT LEAST, create some kind of timeline of important landmarks. I intended for the timeline to point off to detailed articles for the people, concepts, computers and technology involved at that point.
With that approach, we've only made it to the early 1950's and the timeline is still missing many important things. Often, each item on the timeline generates an argument, such as the Shannon blurb (where he linked boolean algebra to logic design). If other authors didn't know that (and I hadn't put in the reference yet), it gets challenged.
Herman Hollerith deserves his very own article, written by someone who knows a lot more about him than I do and who will do his memory justice. It would be a shame to duplicate that effort right smack dab in the middle of another article ("History of computing"), but I have no problem at all with having "History of computing" point off to the Hollerith article as often as it needs to, which would be (in my opinion) whenever the "history of computing" article needs to flag a development along its timeline of many many many developments.
I urge you to edit the sentences you don't like, but request also that you: 1) keep ONLY to the topic of the heading that it's under 2) keep to no more than 8-10 lines per heading
In the approach we're now taking, longer things need to be subarticles.
Unless of course we scrap the "timeline" approach and give in to section creep...
I've taken this approach because "history of computing" is a very large subject. Many books, and even entire museums, approach it, often with startlingly different contents. So I don't want "history of computing" to BE the history, but just to be a timeline, and you drill into the timeline's subarticles to get the juicy bits.
There are alternate approaches possible. Some museums take a "biography" approach; we can do that also (at the bottom of the article is a placeholder for that, which can be developed some day). Others take a "list of breakthrough concepts" approach--there is a placeholder for that also.
I've felt some urgency about getting this article going because a lot of people want to get their Computers Workgroup articles approved, but whenever I've looked at them, the history part isn't ready. If we can get people to break their articles into, just for example, [[computer network]] and [[history of computer networks]], that serves two purposes: 1) it makes it easier to bring [[computer network]] to a state ready for approval 2) it makes it easier to link in [[history of computer networks]] with all the other history-related parts (centered around "history of computing" as the hub of the wheel, so to speak)
The urgency of this is also about prevent some of the Duplication of Effort that I've been seeing. It can easily work out that "history of computing" holds a bunch of stuff about history of networks or Herman Hollerith or whatever, and then subarticles ALSO DUPLICATE the same information in another form. I guess that offends me as a programmer; it usually is a bad idea to duplication information, as it invariably starts to contradict itself :-)
If you would like to propose an alternate approach, please do (as long as you have a reason for thinking it will do a better job in the long run).
If we find, over time, that the timeline thing is appallingly bad, I'm willing to abandon it.
If you want to take the "history of computing" article over now, I'm alright with that too. I really should be doing other things. Just wanted to try to explain why I removed the Hollerith stuff temporarily.
What I was planning to do is, after the timeline gets relative near completion, then step back and look it all over and see about creating a more coherent narrative. But without all the information at least tabulated first, I could not think of a way to end up, someday, with a balanced approach.
Please do take it over if you want to!
|