This first post
should be about goals and how I’ll measure goals and achievements. To begin, my
goal for the end of the project is to build a small computer. This will require
tons of research and a constant monitoring of the “small things”. Specifically,
I think that my time will be parsed out in a piece-by-piece fashion. For
example, one week, I’ll research the aspects of the processor. Another week, I
may research the aspects of the motherboard, and so on and so forth. The
specific aspects that will occupy my time are probably going to be things like “how
to pick the parts so that they work with each other”, and then “how to optimize
the parts, in relation to each other”. This will allow me to learn much more
about the parts themselves and how they work together in a system. It will also
gradually teach me how I can apply those concepts of electronic cooperation to
my later computer-related endeavors.
In the first day
of each cycle, I will begin researching the history and evolution of each
product. For example, in researching the processor, I would research what the
first processor was, how they were applied to old computers, and how they have
evolved since then. By doing this research for each specific component of the
system, I will be able to more effectively choose the parts for my build and
truly make sure that each one is optimized for all of the others.
In the second to
fourth days of the cycle, I will do my research on the component I have chosen
to focus on that week. This research will include watching YouTube videos,
reading customer reviews of products, and reading specification outlines of
various products in each component category made by the manufacturers
themselves. This process takes the longest because many of these reviews and
outlines are either videos that last up to 45 minutes, or papers that can be up
to 5 pages long. By reading the product outline, I will gain insight into the
inner workings of the component, and learn about what it’s actually doing while in a computer system. On the
other hand, by reading customer reviews, I will be able to see what the
customers think, and how their personal experience went after they purchased
the product. This knowledge, although not very consistent, will aid me in
choosing the parts for my final product, as optimization and durability are
key. In the middle are the professional reviews. These reviews are done by
people working for internet companies, such as Newegg.com and NCIX.com, as well
as each of their YouTube channels. The people that review the products have
knowledge of the inner workings that far exceeds that of the average consumer,
but not so much that they know everything the manufacturer does. Often times,
the reviewer will give advice on why you should/shouldn’t buy a specific product,
as well as which scenarios it would be best suited for. This category of
research will probably be my most valuable source because all of the
information is there, with a bit of advice thrown in.
During the fifth
day of each cycle, I will apply the knowledge that I have acquired through
research to my actual build. Using a handy website called Pcpartpicker.com, I will
gradually add one part after another to the build. For example, in cycle 1, I
will add a processor. In cycle 2, I will add a corresponding motherboard, etc.,
etc. Eventually, this process will lead me to have a complete list of parts by
the last week of the project. After this, I will order the parts, and build the
machine. Seeing as I already know a good deal about computers, I will not be
heavily researching the components that stay the same when building a smaller
machine than normal, such as hard drives, optical drives, and things of that
nature. These parts will be pre-configured on Pcpartpicker.com, as they are
universally compatible. Also during the fifth day of the cycle, I plan to outline
my blog post, so that I do not have to rush to get it done on day 6.
On the sixth day
of the cycle, I will complete my blog post, outlining my experience for the
week. I plan to include important historical findings, applicable/fascinating
facts that I learned, as well as a link and/or picture of the progress of my
configuration.
My primary goal
for the project is to have everything flow smoothly. I do not want to be backed
up on research or any other aspect of the project during any one cycle. Another
goal that I have is to simply learn more about computers and their parts.
Seeing as this is a passion of mine, I am very excited to find out as much as
possible about how I can make the computers I configure better.
Wow! It really seems like you have your work cut out for yourself. On the bright side, you obviously are passionate about the project and all told you'll probably enjoy all of the research and work you will put in across the weeks. My one questions would be if everything would be thrown off if you missed one day of research or building? Once the mini computer is built, how would it run in comparison to regular computers? Would it run just as smoothly and normal or be very slow while still working? Other than that, I think this is a very ambitious yet still achievable project that you of all people will do very well with. Lastly, about how big will the computer be when it's all finished?
ReplyDelete~Max
Hola Isaac,
ReplyDeleteJust wondering, but what are you designing the computer for? I remember you telling me that you wanted to present off of the computer, but I can't tell if you've ditched that idea.
Also, I was under the impression that you already knew a heck of a lot about building computers--that's what I understood from your process analysis essay. I thought that you would already know all about each part of a basic computer. Either way, I'm sure you'll still learn much more from this endeavor.
Oh, and if you get around to answering questions, how many computers have you built?
Ethan,
ReplyDeleteYes, I do know all of the parts of a computer already. However, I merely know how to put them together, as well as their basic functions. Over the course of this project, I really want to learn exactly how the parts do what they do. For example, how a processor processes, and how RAM is so fast, etc., etc. Also, to answer your question, I have only built one computer so far, but I have configured dozens both in my own personal time, as well as for friends.
I'm sure you know what you're doing as far as the inner workings and construction, but it seems like it will be hefty as far as the hardware. What kind of previously-owned-materials/budget are you working with in order to construct it? If you can present off of it, I think it'd be fantastic. Perhaps you would only reveal that as the last line or so of the presentation. Just a thought.
ReplyDelete