How Should I Do My Worklogs??
jedihobbit
Central Virginia, USA New
Okay ladies and gents (really like the lady part!) as one of the new kids on the block thought I put a question out to the “regulars†concerning my potential work logs. Been doing stuff for a while and have a few worklogs I’d like to share. HOWEVER…….while there is at a minimum of about 4 – 5 computer cases involved most have gone through numerous changes. That is the reason for the version numbers in my sig.
So the question is, Should I condense the builds as much as possible to show the mods or just burn up space with each revision??
<O:p
So YES means summarize, NO means show each version in detail, and DON’T CARE mean just that.
So the question is, Should I condense the builds as much as possible to show the mods or just burn up space with each revision??
<O:p
So YES means summarize, NO means show each version in detail, and DON’T CARE mean just that.
0
Comments
Have no intention to least more than just the current version if that is what you're getting at. As a matter of fact there will only be two units listed in my sig shortly. What I ment was to show a worklog for v1.0, then v2.0, etc. With the exception of just mobo/cpu changes but where there case modding to make it work.
Like I'm trying to say, sig is not the issue but worklogs showing what it took to put each version together. Brief example would be a build origianlly called BluHaz on up to BluHaz reDux v4.0. From the original skt A, through 939, and now AM2. In the time that occured the case was modified several times to add a temp cage, add hdds where there wasn't space, painted parts, etc.
As most are mATX it wasn't just a simple slap it kind of deal.
So hope I haven't clouded the issue.