Originally Posted by Plan9
What's the other reasons?
I've never bothered and never missed having one. But I'm curious about how others have found them useful
Well the perfect example is the Balrog build. I mean that isn't something you see everyday in the folding area. The reason people do them is because yes there is a sort of l33t factor and showing off, but more so how simple or complex a great looking or functioning build would come about. I've built 2 freenas rigs out of crappy hardware. I've stripped down server cases, modded PSU fans, and loaded them up with exactly what I wanted to run. Then the questions come in of: How did you do that? What did you do with the old xxxxxx? How much xxxx cost and does it work right? These are super common questions and when you spend your time answering about 30 or so, you get to the point of thinking that most people haven't done this or had the idea to. I prefer to keep logs now because it answers tons of questions that would be asked *and still are asked... I just point them to the build log* but I know that I rely on build logs when I start selecting components for what I want to run. I can reference them when I have a problem and see if it's common. What is a solution to getting around certain bits and cost analysis.
People who do "common" builds think this stuff is a dime a dozen. I understand that mentality, but if you ever wanted to get into a more complex area of a build *custom water loops, Pelters, Sleeving, or building a game server* , you're going to rely on people who have done it before, and those build logs would go along way to helping you do w/e it is you wanted to do.
Edited by AMD SLI guru - 7/24/13 at 4:21pm