What happened to common sense?
-
I know it died, I've read the obit posted here before... but what happened? I am a software person, not hardware... but it seems I know more about putting together a silly computer than the hardware building folks.... Not that the world needs one more checklist, but I have been asked to make one for building a machine... including such obvious ones as: make sure the mounting bracket fits the CPU used (using the correct one), make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets). oh there were others... but the smaller issues are too numerous to list anyhow. One, a performance "preferred" solution rather than a manditory one (put your OS on a different I/O channel), still is not done even though I have pounded it home on every single build we have ever done.... did learning die as well? What happened? did this old softy graduate to hardware? I didn't think so, but I am beginning to wonder. I design them, I build the prototypes, and then I end up correcting almost every single machine built after the prototype. how hard is it to face fans toward the back so they blow air to the back of the case and outside? Is this THAT difficult understand? Do I need to start drawing arrows on the chassis and fans as they are purchased so that they can be installed right? I don't think yet another checklist will help, but dagnabbit what the heck will???
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
You wonder how we ever got to space, or trust our military computers, or our medical computers, and so forth. I find this sloppy work everywhere. I've worked with people that feel that getting one task done a day is sufficient to make management happy, even if that task took 10 minutes. It befuddles the imagination. I'm not sure it even has to do with common sense. I think it's more an issue of pride and interest in doing a good job. Marc
-
I know it died, I've read the obit posted here before... but what happened? I am a software person, not hardware... but it seems I know more about putting together a silly computer than the hardware building folks.... Not that the world needs one more checklist, but I have been asked to make one for building a machine... including such obvious ones as: make sure the mounting bracket fits the CPU used (using the correct one), make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets). oh there were others... but the smaller issues are too numerous to list anyhow. One, a performance "preferred" solution rather than a manditory one (put your OS on a different I/O channel), still is not done even though I have pounded it home on every single build we have ever done.... did learning die as well? What happened? did this old softy graduate to hardware? I didn't think so, but I am beginning to wonder. I design them, I build the prototypes, and then I end up correcting almost every single machine built after the prototype. how hard is it to face fans toward the back so they blow air to the back of the case and outside? Is this THAT difficult understand? Do I need to start drawing arrows on the chassis and fans as they are purchased so that they can be installed right? I don't think yet another checklist will help, but dagnabbit what the heck will???
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
El Corazon wrote:
make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets).
Or away from each other and creating black holes. :suss:
-
I know it died, I've read the obit posted here before... but what happened? I am a software person, not hardware... but it seems I know more about putting together a silly computer than the hardware building folks.... Not that the world needs one more checklist, but I have been asked to make one for building a machine... including such obvious ones as: make sure the mounting bracket fits the CPU used (using the correct one), make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets). oh there were others... but the smaller issues are too numerous to list anyhow. One, a performance "preferred" solution rather than a manditory one (put your OS on a different I/O channel), still is not done even though I have pounded it home on every single build we have ever done.... did learning die as well? What happened? did this old softy graduate to hardware? I didn't think so, but I am beginning to wonder. I design them, I build the prototypes, and then I end up correcting almost every single machine built after the prototype. how hard is it to face fans toward the back so they blow air to the back of the case and outside? Is this THAT difficult understand? Do I need to start drawing arrows on the chassis and fans as they are purchased so that they can be installed right? I don't think yet another checklist will help, but dagnabbit what the heck will???
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
El Corazon wrote:
Do I need to start drawing arrows on the chassis and fans
All the fans I've purchased in the past fifteen years have had an arrow molded into the plastic case to show which way the air flows. You just can't fix stupid... BTW - In my lifetime, at least, common sense has always been an oxymoron, with as much substance as the Easter Bunny. I'm hopeful that, in my 53 years, I gained some small measure of it, but I still have my days...
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
I know it died, I've read the obit posted here before... but what happened? I am a software person, not hardware... but it seems I know more about putting together a silly computer than the hardware building folks.... Not that the world needs one more checklist, but I have been asked to make one for building a machine... including such obvious ones as: make sure the mounting bracket fits the CPU used (using the correct one), make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets). oh there were others... but the smaller issues are too numerous to list anyhow. One, a performance "preferred" solution rather than a manditory one (put your OS on a different I/O channel), still is not done even though I have pounded it home on every single build we have ever done.... did learning die as well? What happened? did this old softy graduate to hardware? I didn't think so, but I am beginning to wonder. I design them, I build the prototypes, and then I end up correcting almost every single machine built after the prototype. how hard is it to face fans toward the back so they blow air to the back of the case and outside? Is this THAT difficult understand? Do I need to start drawing arrows on the chassis and fans as they are purchased so that they can be installed right? I don't think yet another checklist will help, but dagnabbit what the heck will???
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
El Corazon wrote:
What happened to common sense?
Aww sorry, I forgot to wake her up today in the morning. :-O
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighist -
You wonder how we ever got to space, or trust our military computers, or our medical computers, and so forth. I find this sloppy work everywhere. I've worked with people that feel that getting one task done a day is sufficient to make management happy, even if that task took 10 minutes. It befuddles the imagination. I'm not sure it even has to do with common sense. I think it's more an issue of pride and interest in doing a good job. Marc
Marc Clifton wrote:
how we ever got to space
We got to space because my parents' generation had balls, goddammit. They weren't going to let the freakin' commies get to the moon first. It didn't matter if we had to line up slingshots from Anchorage to St. Augustine and use them to throw astronauts at the damn thing. The goal was to GET THERE, not suck all we could at the government teat. Ironically, a lot of the people and companies involved got rich at it.
Software Zen:
delete this; -
I know it died, I've read the obit posted here before... but what happened? I am a software person, not hardware... but it seems I know more about putting together a silly computer than the hardware building folks.... Not that the world needs one more checklist, but I have been asked to make one for building a machine... including such obvious ones as: make sure the mounting bracket fits the CPU used (using the correct one), make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets). oh there were others... but the smaller issues are too numerous to list anyhow. One, a performance "preferred" solution rather than a manditory one (put your OS on a different I/O channel), still is not done even though I have pounded it home on every single build we have ever done.... did learning die as well? What happened? did this old softy graduate to hardware? I didn't think so, but I am beginning to wonder. I design them, I build the prototypes, and then I end up correcting almost every single machine built after the prototype. how hard is it to face fans toward the back so they blow air to the back of the case and outside? Is this THAT difficult understand? Do I need to start drawing arrows on the chassis and fans as they are purchased so that they can be installed right? I don't think yet another checklist will help, but dagnabbit what the heck will???
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
I just read a Norwegian test specification for set top boxes and one of the first steps is to make sure it has a tuner. If there is no tuner then that test step fails :sigh:
Visit http://www.notreadytogiveup.com/[^] and do something special today.
-
I just read a Norwegian test specification for set top boxes and one of the first steps is to make sure it has a tuner. If there is no tuner then that test step fails :sigh:
Visit http://www.notreadytogiveup.com/[^] and do something special today.
You just know that that step's there because someone, somewhere, delivered an STB for testing that didn't have a tuner.
DoEvents: Generating unexpected recursion since 1991
-
El Corazon wrote:
make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets).
Or away from each other and creating black holes. :suss:
Brady Kelly wrote:
Or away from each other and creating black holes.
In my business, if I could casually create those, they would give me a bonus.... assuming I survived the experience....
-
El Corazon wrote:
Do I need to start drawing arrows on the chassis and fans
All the fans I've purchased in the past fifteen years have had an arrow molded into the plastic case to show which way the air flows. You just can't fix stupid... BTW - In my lifetime, at least, common sense has always been an oxymoron, with as much substance as the Easter Bunny. I'm hopeful that, in my 53 years, I gained some small measure of it, but I still have my days...
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
I've bought a few cheaper no name fans that didn't have an arrow. Fortunately a scrap of tissue will indicate the flow direction of even the lowest speed fans.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
You wonder how we ever got to space, or trust our military computers, or our medical computers, and so forth. I find this sloppy work everywhere. I've worked with people that feel that getting one task done a day is sufficient to make management happy, even if that task took 10 minutes. It befuddles the imagination. I'm not sure it even has to do with common sense. I think it's more an issue of pride and interest in doing a good job. Marc
Marc Clifton wrote:
I find this sloppy work everywhere. I've worked with people that feel that getting one task done a day is sufficient to make management happy, even if that task took 10 minutes. It befuddles the imagination. I'm not sure it even has to do with common sense. I think it's more an issue of pride and interest in doing a good job.
Agreed. In my shop I have to go behind folks all the time fixing "fixes". It gets really old after a while- to the point that I've begun letting them fail so they will (maybe) see the err of their ways, mostly due to a lack of attention to detail. I, on the other hand, have an interest and desire to ship a good product, call me crazy.
-
I know it died, I've read the obit posted here before... but what happened? I am a software person, not hardware... but it seems I know more about putting together a silly computer than the hardware building folks.... Not that the world needs one more checklist, but I have been asked to make one for building a machine... including such obvious ones as: make sure the mounting bracket fits the CPU used (using the correct one), make sure your fans are blowing the same way (rather than toward each other and creating stale air-pockets). oh there were others... but the smaller issues are too numerous to list anyhow. One, a performance "preferred" solution rather than a manditory one (put your OS on a different I/O channel), still is not done even though I have pounded it home on every single build we have ever done.... did learning die as well? What happened? did this old softy graduate to hardware? I didn't think so, but I am beginning to wonder. I design them, I build the prototypes, and then I end up correcting almost every single machine built after the prototype. how hard is it to face fans toward the back so they blow air to the back of the case and outside? Is this THAT difficult understand? Do I need to start drawing arrows on the chassis and fans as they are purchased so that they can be installed right? I don't think yet another checklist will help, but dagnabbit what the heck will???
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."
Taking a somewhat contrary view.... There is no over estimating the stupidity of the average shop worker. Nor can you over estimate the ingenuity they will use to force a square peg in a round hole. Therefore it is the responsibility of the “smart” engineer to make it very difficult or impossible for the shop to screw it up. Post simple pictorials of the correct assembly at each work station as a reminder. Don’t bother with written instructions, assume they can’t read. i.e. a picture of a paper strip being blown by the fan in the correct direction and another one with a red “no” symbol of it blowing in the opposite direction. Stamp or mould in pictorial guidance whenever possible. It’s cheap at the front end and saves a ton of problems later. Look at any PC board and try to emulate those ideas. Make parts that are reversible, i.e. can be installed in multiple orientations and still work. If possible, only use one size screw everywhere. Select or design in keyed connectors, both mechanical & electrical that can not be assembled backwards. Select electrical pin locations such that power is mated to an empty location if the connector is reversed. Color code mating parts (especially if a similar part can be forced into that location). If the parts can not be color coded, then at least color code the stock bins and production paperwork. i.e. Always use red parts when building this configuration. In one company, they hired an automotive assembly line consulting firm to help them speed up production. After a $100K study the recommendation was simple color coding. We all laughed at the wasted money just to be told to use colored dots on the parts bins. But amazingly it worked even better than the consultants had promised. Help the quality people design a set of simple checks that hopefully can be done at the assembly station or an automated test station at the end. For example, putting power to the case fans while the case is sitting next to a set of hanging strips to verify fan operation and direction. Not all these ideas are applicable in every situation, but there are tons of similar ideas out there that are cheap and effective in reducing production problems. The key is usually to design them in at the front end so you can still hire McDonald’s rejects to assemble your product. Takes a bit more thought, but that’s what engineers do best! If you are saying to yourself, that’s not my problem, ask yourself who management is going to keep or promote in the next round. The guy who
-
Marc Clifton wrote:
how we ever got to space
We got to space because my parents' generation had balls, goddammit. They weren't going to let the freakin' commies get to the moon first. It didn't matter if we had to line up slingshots from Anchorage to St. Augustine and use them to throw astronauts at the damn thing. The goal was to GET THERE, not suck all we could at the government teat. Ironically, a lot of the people and companies involved got rich at it.
Software Zen:
delete this;Now we have cost-plus contracts. :) no encouragement to get it done, because the longer and more expensive it is, the more you get out of it and the bill still gets paid.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb) John Andrew Holmes "It is well to remember that the entire universe, with one trifling exception, is composed of others."