Not really, as far as I know, Indians were real people, no theory about it.
[addsig]Posted by Orpheus on Sun Feb 27th at 3:59am 2005
Orpheus
member
13860 posts
1547 snarkmarks
Registered: Aug 26th 2001
Location: Long Oklahoma - USA

Occupation: Long Haul Trucking
Posted by Crono on Sun Feb 27th at 4:07am 2005
No. It's the order the bytes are read in an memory address. Most signifigant to least signifigant or vice versa. Those are what big and little endian are.
Nevermind.
It doesn't surprise me that you haven't heard about it, why would you ever need to know it?
Posted by Wild Card on Sun Feb 27th at 4:15am 2005
[addsig]
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Crono on Sun Feb 27th at 4:29am 2005
Well, yes, but it doesn't matter. That information isn't needed for a basic understanding. To be honest, that's really getting down and dirty. You don't need to explain how the ram its self functions, just how it functions WITH the rest of the system.
Let's put it this way: the idea of Endians is about page 34 in my architecture book. RAS and CAS are on page 459. It's pretty hard stuff to understand. Because, you're also assuming the person knows what a matrix is. And you said the paper was to edjucate people who don't know anything about computer hardware. If you want to go that deep, why not just tell them to read a book?
Does that make sense? It's good that you know that, but to be honest, you don't have any use for that knowledge unless you're using memory (such as programming in assembly). [addsig]
Posted by Wild Card on Sun Feb 27th at 4:45am 2005
edjucate eh?
The reason I talk about that, is because one of the goals is to explain how the hardware works too. So its only fair in explaining that bit on RAM. And its also to help clear things up about memory timmings and overclocking your ram.
Curious, what book are you getting this from, and do you know where I could find... perhaps a *whispers* slightly less-than-legal copy online?
I mean, if endian starts at page 40 and CAS and RAS are on page 400, than Im quite curious to read up on it, and about what's in between those pages.
[addsig]Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Crono on Sun Feb 27th at 5:11am 2005
ISBN: 0-13-034074-X
The book assumes you know C/C++ somewhat (not VISUAL C++)
It's funny though in the "Assumption about readers background" section is says:
"If your computer runs Microsoft Windows, you have two choices." Sounds, like a threat, I found it funny.
Also, I think the book cost me about $120 ... at my school's bookstore.
There are MANY others, this is just the one I have because it was needed for a class. But it's written very well.
But, my entire point was that, you shouldn't explain the inner working of everything because it isn't needed to understand how the system works in general. Seriously, if you want to go into how ram works, do it in a different paper.
One step at a time I would think! [addsig]
Posted by SaintGreg on Sun Feb 27th at 5:39am 2005
I agree with crono, for a paper explaining beginning topics, if you try to go into too much detail, you risk:
1) losing your audience. The average person who does not know much about computer hardware reading this wants to know the basics, they do not care about nitty gritties. Someone who wants to read about nitty gritties is not going to be reading an article about basic computer stuff because they want to get to the detail fast and not have the basic fluff.
2) having your paper being even longer and be more disjunct than it already is
Small details can fill volumes and volumes of text. If you really want to cover interesting topics that go into more depth go for it in a more specialized article.
I also agree that you should go into a few things in more detail. Going into the basics of what endian as is good. But you don't need too much detail. Maybe not in this article, but in a different one (up to you) or toward the end of the CPU section you should talk about different CPU technologies such as vector and superscalar processing.
One thing I really didn't like about your article was that alot of it was about computer companies and their history. You should talk about the hardware are technology and only give examples of implementions and when these were used.
[addsig]
Posted by Wild Card on Sun Feb 27th at 10:42pm 2005
[addsig]
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Gwil on Sun Feb 27th at 10:52pm 2005
Split it over a series or aim at it a defined audience. You can't have multiple target audiences with technical writings, it just *doesn't* work like that. Trust me.
And that's use of the English language, not computing. Listen to Crono, he is talking sense. If you really wanted to achieve a good, balanced article - I can't comment on the hardware details, but I can go through it with a toothcomb in regards to target audience, use of language etc etc - I studied the editing of documents for maximum "impact" in great depth, and even if I do say so myself, got rather good at it
edit: for example -
the help of calculators no bigger than the size of your stack of credit cards
If i'm blunt, phrasings like that are just poor
A document which is technically correct and full of useful info, can fall over as soon as bad grammar or repetition comes into play.
If you have it outside of .pdf i'd be happy to give it an editing over in terms of the use of English. [addsig]
Gwil
super admin
2864 posts
293 snarkmarks
Registered: Oct 13th 2001
Location: Derbyshire, UK

Occupation: Student
Posted by Orpheus on Sun Feb 27th at 10:55pm 2005
Nick, i think what they are saying is, your audience doesn't need to know where the zinc, or gold was mined in order to comprehend PC's
you might lose your intent in the quagmire of your delivery.
think of it like this, how many people do you think read crono's entire posts when he goes off on one of his tangents?
*dodges boot thrown from oregon*
just making a point master crono ![]()
Orpheus
member
13860 posts
1547 snarkmarks
Registered: Aug 26th 2001
Location: Long Oklahoma - USA

Occupation: Long Haul Trucking
Posted by Crono on Sun Feb 27th at 11:08pm 2005
WC, what you're really saying is that you want to write several books.
Let's put it this way: I have a series of Intel books, they're the books they gave to incoming engineers. I have about ... 15 or so. They cover the entire X86 architecture. Top to bottom. That is just hardware and architecture. AND it only talks about their set up, it assumes you already know everything else.
There's too much information for you to do what you're saying you want to, not to mention it would take years to catalog it the way you're, apparently, thinking.
And, I've talked about pretty mundane topics here. Wait until you get to the complicated stuff ...
A SINGLE paper taking a "noob" to "not such a noob" is very easy. In fact, if I had time, I could probably write a paper that would give you the low down and blow everyone else you know out of the water in regards to general computer knowledge. (this would already be true if people listened or read my "tangents"
Now, the real question is ... how do you think this would benefit a reader? Seriously. Knowing this stuff isn't going to give you the ability to make your computer run faster. It's not going to teach you how to optimize anything, unless you're a developer. So, in that regard, why go to such detail on knowledge that person would never use?
I think it would be a better idea, just to explain basics upon basics of interconnection and give knowledge of how to put all this together when choosing computer parts and things like that. THAT would benefit many people tremendously.
I mean ... s**t ... many people don't know that when choosing a board you should really look at the chipset it has first. But most people don't really understand what the chipset is.
I guess, a valid question you should ask your self is, "What is an attainable goal with this paper?" then tell us, and we'll help you reach it. You're just trying to take way too much on at this point in time. [addsig]
Posted by Wild Card on Sun Feb 27th at 11:09pm 2005
[addsig]
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Wild Card on Sun Feb 27th at 11:15pm 2005
To give the reader just about complete knowledge on computer hardware, mainly X86, while still taking note of other architectures out there.
Target audience:
Noobies and veterans alike, who wish to know all there is to know, such as myself. So that I can visualise how my computer works. How the processor does it's 'magic' and how the RAM works. Stuff like that that is for the most part, useless, but still, I want to know. type of deal.
[addsig]
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Orpheus on Sun Feb 27th at 11:16pm 2005
1) you are asking crono's advice, yet ignoring it somewhat. not good.
2) crono i was jesting, but in such a way as to assist your cause.
nick, slow down, smell the roses. you are getting good advice, problem is its advice you don't wanna hear. you are acting like a n00b mapper fishing for compliments, you keep asking till someone says something you like.
crono is right, pick an area you want to write on and do it well, don't spread yourself so thin you look silly.
/ 2 cents.
[addsig]Orpheus
member
13860 posts
1547 snarkmarks
Registered: Aug 26th 2001
Location: Long Oklahoma - USA

Occupation: Long Haul Trucking
Posted by Crono on Sun Feb 27th at 11:17pm 2005
Isn't that the problem?
Sorry.
the help of calculators no bigger than the size of your stack of credit cards
There's many things wrong with it, I don't remember the surrounding text, but, based on this: your word ordering is weird ... it doesn't flow very well if you said this outloud. You also identify the reader, don't do that.
"... the help of calculators, which vary in size, some of which are no bigger then a stack of credit cards ..." would be a better way to put it, for example.
[EDIT]
Orph, I know.
and I thought Gwil was specifically talking about WC's grammar ... oh well, either way I suppose. [addsig]
Posted by Gwil on Sun Feb 27th at 11:21pm 2005
You have to trust on this like Orpheus says, because as it stands, while the document isn't terribly written, or technically rubbish it isn't hitting your target audiences (bad, anyway! bad bad bad! one audience! focus!) nor is it an attainable goal.
Sorry to say it Wild Card, but it really needs serious work, cut backs and some heavy editing in places.
If you want my help doing this, i'm happy to - but you have to accept changes and suggestions, otherwise asking for feedback and help is a moot point from the outset
edit: Exactly Crono - you hit the nail on the head. Awkward phrasing and "bad flow" scuppers a document from the start, regardless of how accurate the facts/information within is.
I'm speaking purely from a writing standpoint, your article baffles me technology wise - and that can't be a good thing, as I don't feel I understand any better a lot of the processes you are trying to explain.
But not - it isn't grammar i'm talking about, Wild Card - part of my studies on my English Language course was the editing of documents to make them effective and relevant to the target audience - from baking instructions to a description of an exhibition in a gallery.
I was citing that as an example, and how close it was to the start - I am saying, I have the knowledge (and dare I say it, the skill) to edit the document to make it more relevant, e [addsig]
Gwil
super admin
2864 posts
293 snarkmarks
Registered: Oct 13th 2001
Location: Derbyshire, UK

Occupation: Student
Posted by Wild Card on Sun Feb 27th at 11:22pm 2005
As for statement there, well, its my way of typing I guess. But even now re-reading it I dont see anything wrong with it. Crono just added "Which vary in size" And I dont see how that identifies the reader either. ?
[addsig]
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Posted by Orpheus on Sun Feb 27th at 11:26pm 2005
OK then.. i am the worse person to ask when it comes to "text delivery"
i get into trouble way to often to give advice on that topic, since its obvious i never learn from my mistakes.
[addsig]Orpheus
member
13860 posts
1547 snarkmarks
Registered: Aug 26th 2001
Location: Long Oklahoma - USA

Occupation: Long Haul Trucking
Posted by Gwil on Sun Feb 27th at 11:26pm 2005
As it stands it's fairly badly written, tries to cover too much, is laden with unexplained jargon and waffle which renders it unreadable, and therefore, not very useful at all for people wanting to know "all they can about computers"
Sorry to sound so harsh, but it is the truth. [addsig]
Gwil
super admin
2864 posts
293 snarkmarks
Registered: Oct 13th 2001
Location: Derbyshire, UK

Occupation: Student
Posted by Wild Card on Sun Feb 27th at 11:27pm 2005
-Gwil
I dont mind the help, and actualy would like it. I just fail to see how it is terribly written and repetitive.. I guess its just my style or writing. (which got me a 97 in English last year
The other thing I was looking was also mainly on the technical side. As I havent exactly proof-read the document yet. Which is maybe why it looks so messy? Sort of. I just though of something and wrote it down.
Gwil, again, if you are willing to correct grammar and whatnot in a 25-page article, firstly, I must salute you, and secondly I must ask... Are you crazy? lol.
[addsig]
Wild Card
member
2321 posts
339 snarkmarks
Registered: May 20th 2002
Location: Ontario, Canada

Occupation: IT Consultant
Snarkpit v6.1.0 created this page in 0.1448 seconds.

