Many years ago I was 'the kid' on a rather daunting project. I was to verify the correct implementation of an IEEE-754 lib that had been implemented on a new platform. There was also an identical implementation on a previous platform that had been in service for 4 years, and had no reported bugs against it for two years. The previous implementation was in active use, as shown by a steady stream of devs asking for clarification, assistance with bugs (in their code) etc...
So my plan was to validate the new code by putting it operation-to-operation with the old code. Since the two libraries claimed to conform to the same standard I treated the old implementation as the gold standard and developed as test system in C and assembly on the new platform that communicated with the old system to execute identical operations, and compared the results bit-for-bit, and where reasonable for execution time. Since the project was underfunded and I had other responsibilities I also made it a Montecarlo test system... sure it did a complete suite of unit and bounds tests, but after that it ran in random mode. It ran billions of test cases...
After a few weeks of run-time I noticed an consistent error. The logs were showing that when either operand in a multiply or a divide was a +2.0000... the result was off in the least significant bit of the mantissa. (eg. 2.0 * 1.0 = 2.00...01 or 2.0...0 * 2.00...00 = 4.00....02... etc)
Further analysis concluded that new implementation was returning correct results, and the old platform was returning incorrect results.
After consulting the PM I posted a bug against the old code. All hell broke loose. The Gray Beards upstairs came down on my 20 year old ass like The Wrath of God(tm) for daring to challenge their combine 120 years experience in math implementations and the fact the old implementation passed the official IEEE-754 test suite flawlessly, etc.
It got particularly ugly when I pointed out that the new code passed that test suite as well, as it was a hard requirement before I could accept an RC as testable. I had already chased that lead down and had the reports to prove that the implementation I was testing had passed the suite as well.
So it was that I my code was drug out before a committee, and reviewed thoroughly, etc with my PM and manager acting as my 'legal council' before the assembled wrath.
Eventually the issue was uncovered. The Gray Beards had closed the original bug reported as 'won't fix' and then somehow later the record was altered to 'not a bug' So I never saw it for my review when I was looking for open activity against the old code.
While the PM and my direct supervisor protected me from the blow-back... being the messenger was bad for my career at that company. I got shuffled off to less important projects until I left in disgust.
Don't anger the Gray Beards... as the 'new kid'... it will end badly for you, even if you are right.
Was a time honored tradition throughout the world until almost late-19th century. All sea faring nations practiced it at some time during their nautical histories.
It also was often coded into 'idleness' laws all over the world where one could be impressed into forced labor just for being seen on the street without clear leave to be there. Often with no judicial review at all.
And just like various forms of maritime piracy and privateering, it was legal and actively defended by government and commercial interests.
Once upon a time I was helping a friend move his glass-blowing shop. A bunch of angry 'kids' were involved. One of them managed to stick a claw-hammer through a water main in the basement of the building. I didn't care who did it, or what drugs they were on, or if they were angry, or just stupid.
I had some management experience at that point in my life and tried to be diplomatic. My time was volunteered. If anything, I was simply doing a friend a favor. That all changed when the shit hit the fan.
The water was annoying at first. Attempts were made by a few to control the water.... They failed to contain the issue, because they failed to understand the scope of the problem. In part it was beyond their imagination, and in part it was beyond their scope of experience. They were a bunch of 'kids' that showed up to help a popular glass-blower. In general I was about 10 years older than any of them, the only thing they had on me is that some of them were significantly bigger than I am.
After some time of seeing others fail I envisioned a *solution* and tried to engage a few of the senior (read: *leadership*) members of the crew in that solution... they were already Tharn. ( http://www.urbandictionary.com/define.php?term=tharn )
After a few moments reflection I went DI (Drill Instructor) on the whole crew. I ordered these people around, and shouted down anyone who opposed me. *most of whom did not know me* It was a rough few hours. The water main had been bypassed years ago the 'kids' I brow beat into finding the mains found it but the valve was inoperative. The city was called, (by convincing a kid to call his girl and have her call in a water leak report) and the city eventually shut the water off. The cops were deflected, by me and the shop owner (who had the gift of knowing when he was out of his depth) The job was completed. No one was arrested or prosecuted. Mission accomplished.
I made some powerful friends. I made some bitter enemies. I do not regret the things I said, or did. No one else present had the balls to do what needed to be done. What I did worked, and that was for that brief time period was exactly what needed to happen.
Some of those 'kids' were so pissed by my 'harsh' approach that I was threatened, publicly shamed, and it let to a few really stubborn ass-hats getting their asses kicked. Two by me personally, (when they tried to jump me) and three others by people who realized I had been for that moment the most effective leader they had seen in their short lives.
Sometimes leadership does not appear until it is needed. I'm not going to say what Linus did is right or wrong. I have read the thread, but I don't think we have all the details. IMO: That man is a gifted leader. I'd give him the benefit of the doubt. If this maintainer worked with Linus for four years, he knows the score... and knows what Linus expects. Nuff said.
If the majority involved in MY little moment of 'management under fire' had not agreed with me. I would not likely be writing this now. I'd have caught some bullets... that is the kind of crowd I was dealing with.
Most of the reason for using exotic alloys is to overcome weight vs strength problems in getting stuff out of the gravity well. If the interesting chunks of asteroid are blends of materials who cares? Dig chunks of it out, assess its bulk properties and fuse into desired shapes as is. For extra points, grind up the output of various deposits and blend the gravel to the approximately the right composition and fuse it into shape.
We don't worry very much about the exact composition of (for example) red-brick. We simply measure its bulk properties and use it accordingly.
The only time refining would be useful is if particularly valuable materials were present in the asteroid in quantities large enough to bother. In that case just carve the ore-body out of the asteroid, fuse it into bricks, and drop them back to earth in a reentry container.
Likely, only long lived radiological ores, and a few metals would be worth the hassle.
This is really in reference to both you and the GP.
Digital or Analog: it does not matter.
With some exceptions due to cheaply made audio digitizing gear, there is no reason to capture audio with anything but the cleanest path you can manage.
At 96KSPS and 24 bits you can capture everything from a cockroach fart at 50m to a F-22 raptor in full afterburner right on the mic. The real limitation is the microphone. So lets assume that some mic diaphram made of di-unobtanium-obscurium can provide perfect, flat, sensitivity for the full range. It is indestructible, it has no mass, and responds precisely and predictably from 0.1 Hz up to 48Khz in a perfect cardoid pattern with no side-lobes.
We capture a live sound-field in stereo with a nice X-Y config and low and behold we a have a pristine recording of that field. Every single pressure transient that the ears can possibly respond to is perfectly represented in the data stream.
It sounds like hammered shit. Why? Because the ears do not work the way the above recording chain does. Well, ok that is fine. What we want is all there. Everything is there. Or is it? Well, I could go into a massive digression into why a two mic stereo recording setup is not even close in terms of capturing a sound-field as a person hears it, but I am not going to write a book on psycho-acoustics here.
We had a reason for digitizing this particular sound-field. There is a woman singing in the room near the mics. She has headphones on and she is singing to a recording of the backing band that is part of the recording sessions for her next album.
In the recording of this woman's singing we have captured a lot of 'stuff' that really is not part of the performance. And though it is not 'noise' in the classic analog sense of the word, it IS 'noise' in the perceptive sense since it competes with the singer's voice for our attention.
In the older analog recording approach we avoid recording anything we don't want and there are tradeoffs in suppressing some components of the sound field and enhancing others. A large part of what a recording engineer does is sculpting the pre-recording signal chain to min-max the desired elements of the subject.
In the digital recording system we could use the same approach and get the same tradeoffs. The final result will sound like an analog recording. Because the only thing different is the point at which the Analog to digital conversion takes place. We could digress here about distortions introduced by the recording medium ad nausium and get nowhere. At 24 bits the 'noise floor' of decent recording system (and not even a very expensive one) is so low that you could not hear it even if you put isolation-headphones on and cranked the monitor amp to '11' (Do not try this at home!) the damned headphone amp would make more noise!
So we have a (nearly)'colorless' recording system with no distortion in the human hearing regime.. why does it suck ass when we listen to the unaltered output of a perfect recording-chain?
Because we have trained ourselves to accept and interpret signal distortion. Depending on our personal interests, and how we were raised, how we damaged our ears, the types of distortion and quantities of distortion we process are as unique as the shape of our skulls and the meaty bits around our ears, including the various bangles we choose to staple to to them. This, and much more, strongly influences what we hear and how we interpret what we hear.
From the sound-fields we listen to, we try to extract (quite literally) exactly what we want to hear. If what we want to hear does not exist in a recorded sound-field, well guess what⦠we don't like that recording.
So now we go back to the 96KSPS 24 bit signal chain it is as perfect as it getsâ¦. might as well be a block of marble. Because what needs to be done to it is to start chipping away anything that does not support the performance of that woma
That tone was probably the Horizontal interval. The tone is really quite loud in CRT TVs because it is caused by the deflection yoke on the tube changing shape as it is excited into creating a rather large magnetic field by the deflection amplifiers. for NTSC it is 15750 Hz for PAL it is 15625 Hz
The next generation of kids will be able to here those pitches just fine thanks to the demise of CRT display systems.
What the SE crew did to keep their site up was amazing. They got no help from their site until way late in the game.
They counted on Peer1 to handle facilities... and they dropped the ball.
I have had multiple 72 hours outage due to local power going away. Having to plan to have fuel delivered to the backup gen-set, and having to ration power (I knew the burn rates and what equipment was non-essiental)... blah blah blah.
The bottom line is that the customers are not in the NOC, so if the organization cares about its customers... what needs to be done gets done.
Peer1 abandon ship for two days and left THIER customers to fend for themselves... and then treated them poorly when they came back to restore the services they failed to maintain during a crisis that while bad was not insurmountable.
Peer1 should get shutdown for failing to cover their end of the bargain.
When making commercial dough... say for Pizza... (which I am most familiar with.)
50 lbs bag of mix is combine with a specific amount of water at 110F. This then mixed for a specific number of minutes, poured into a food grade 'garbage bag', sealed and allowed to rise for 18 hours in a 44F cooler.
By specifying the temp and volume of water the mixture is extremely consistent assuming the 'doughboy' follows the spec.
The plastics used in IC packages tend to absorb moisture from the air. Over time this moisture gets trapped in the package. If you heat a plastic IC package that has been in service to 250C there is a pretty good chance it will 'popcorn' thus destroying the chip, and often visibly rupturing the package. It can be prevented by baking the board at 50 - 80C for 12 - 20 hours, but that is going to cause other problems. No one is going to be using reflow ovens to "reset" FLASH cells.
As others have pointed out spot-heating a FLASH block to 800C would take an almost trivial amount of energy, and would only need to be done when a block fails an erase-write cycle, or as an idle task performed on blocks that have been reassigned from the 'in-use' pool to the 'dirty' pool, but have not yet been erased and assigned to the 'free' pool.
The hardware required to implement this on an existing flash design would be almost trivial.
Easier to deal with is the 2 second rule. Watch for a road feature, discoloration, crack, paint line... etc. When a noticeable feature is revealed from beneath the car ahead of you, begin counting... One-one-thousand, two--one-thousand. If the feature you are paying attention to disappears below your hood, you are too damn close. This works at all reasonable driving speeds. At very low speeds ( 6 mph) you should be able to see the road and the point where the rear tires of the vehicle in front of you contact the road. This is also true if you are stopped in traffic. Cant see their rear-tire patch? You are too damned close.
Personally I like to keep a 2.5 second gap at speeds greater than 45mph, incase the car(s) ahead of me drop something into the road. I've been doing this for so long it is automatic. I have never even come close to hitting a car in front of me, even when in on case the car ahead of me crawled up onto the Jersey Barrier... causing it to decelerate much faster than expected. I had more than enough time to check mirrors and get out of the lane.
1st gen iMacs shipped with a 56K modem installed, as well as a 10/100Mb ethernet port, IEEE-1394, USB 1.1, and audio i/o... MacOS(OSX didn't exist yet) supported all of the generic device classes except serial-stream (serial port adapters) without third party drivers.
PCs had USB on the Mobo back then (and even a few high end boards had 1394 ports) but Windows had terrible support for USB and 1394. Damn near every device required a OEM supplied driver. I still have a lot of polycarb plastic coasters from that era.
I'm going to assume that my comment was misunderstood.
When accepting new hardware it is typical to verify that it works.... THEN assemble it into the desired configuration. THEN verify that each sub-system is fully functional... at least all the I/O. These are basic functional tests... yes?
Where I have issue with the video is the lack of precautions taken during assembly...
NO grounding straps. NO signs of any ESD precautions!!!
Lacking from the video is the debugging process.
Sure they built it in 2 days... but how many nodes came ready?
I was cringing through the whole video over their lack of concern for basic ESD prevention. They don't need to be wearing bunny suits or anything that extreme, but FFS.... could ya show a little bit of respect for the hardware? Heck even clipping the freaking base-plates to ground during assembly would have been more than adequate.
That video was like watching "OW MY BALLS" for geeks!
He was designing and troubleshooting analog and digital hardware.... radio and battery systems until the day he could legally tell his employer to fuck off and collect his Navy retirement and SSI...
He knows more about practical engineering than I ever will. And we still kick ideas around. He retired but did not stop being an Engineer.
I'm 46 and still writing code, and back at school for Biz Admin. I got to go back to my roots focusing on bare metal, and more recently embedded LINUX.
I'll stop writing code when you pull my cold, dead fingers off the keyboard.
No it is not if the process for handling postal voting is well established for the majority of voters in a district. (Or in my case the whole county) But during a FEMA disaster and an increased need.... there's plenty of room for grubby paws... and I think that is the concern.
Slashdot Mirror
Many years ago I was 'the kid' on a rather daunting project. I was to verify the correct implementation of an IEEE-754 lib that had been implemented on a new platform. There was also an identical implementation on a previous platform that had been in service for 4 years, and had no reported bugs against it for two years. The previous implementation was in active use, as shown by a steady stream of devs asking for clarification, assistance with bugs (in their code) etc...
So my plan was to validate the new code by putting it operation-to-operation with the old code.
Since the two libraries claimed to conform to the same standard I treated the old implementation as the gold standard and developed as test system in C and assembly on the new platform that communicated with the old system to execute identical operations, and compared the results bit-for-bit, and where reasonable for execution time. Since the project was underfunded and I had other responsibilities I also made it a Montecarlo test system... sure it did a complete suite of unit and bounds tests, but after that it ran in random mode. It ran billions of test cases...
After a few weeks of run-time I noticed an consistent error. The logs were showing that when either operand in a multiply or a divide was a +2.0000... the result was off in the least significant bit of the mantissa. (eg. 2.0 * 1.0 = 2.00...01 or 2.0...0 * 2.00...00 = 4.00....02 ... etc)
Further analysis concluded that new implementation was returning correct results, and the old platform was returning incorrect results.
After consulting the PM I posted a bug against the old code. All hell broke loose. The Gray Beards upstairs came down on my 20 year old ass like The Wrath of God(tm) for daring to challenge their combine 120 years experience in math implementations and the fact the old implementation passed the official IEEE-754 test suite flawlessly, etc.
It got particularly ugly when I pointed out that the new code passed that test suite as well, as it was a hard requirement before I could accept an RC as testable. I had already chased that lead down and had the reports to prove that the implementation I was testing had passed the suite as well.
So it was that I my code was drug out before a committee, and reviewed thoroughly, etc with my PM and manager acting as my 'legal council' before the assembled wrath.
Eventually the issue was uncovered. The Gray Beards had closed the original bug reported as 'won't fix' and then somehow later the record was altered to 'not a bug' So I never saw it for my review when I was looking for open activity against the old code.
While the PM and my direct supervisor protected me from the blow-back... being the messenger was bad for my career at that company. I got shuffled off to less important projects until I left in disgust.
Don't anger the Gray Beards... as the 'new kid'... it will end badly for you, even if you are right.
Was there any people that was willing to educate itselves on grammar?
I don't think english is the GP's native language, and it is likely that he was using a translation tool.
Not everyone who posts here is qualified to post in English. It is called the "world Wide Web" for a reason!
Get over it.
Impressment or 'Press ganging' http://en.wikipedia.org/wiki/Impressment
Was a time honored tradition throughout the world until almost late-19th century. All sea faring nations practiced it at some time during their nautical histories.
It also was often coded into 'idleness' laws all over the world where one could be impressed into forced labor just for being seen on the street without clear leave to be there. Often with no judicial review at all.
And just like various forms of maritime piracy and privateering, it was legal and actively defended by government and commercial interests.
Once upon a time I was helping a friend move his glass-blowing shop. A bunch of angry 'kids' were involved. One of them managed to stick a claw-hammer through a water main in the basement of the building. I didn't care who did it, or what drugs they were on, or if they were angry, or just stupid.
I had some management experience at that point in my life and tried to be diplomatic. My time was volunteered. If anything, I was simply doing a friend a favor. That all changed when the shit hit the fan.
The water was annoying at first. Attempts were made by a few to control the water.... They failed to contain the issue, because they failed to understand the scope of the problem. In part it was beyond their imagination, and in part it was beyond their scope of experience. They were a bunch of 'kids' that showed up to help a popular glass-blower. In general I was about 10 years older than any of them, the only thing they had on me is that some of them were significantly bigger than I am.
After some time of seeing others fail I envisioned a *solution* and tried to engage a few of the senior (read: *leadership*) members of the crew in that solution... they were already Tharn.
( http://www.urbandictionary.com/define.php?term=tharn )
After a few moments reflection I went DI (Drill Instructor) on the whole crew. I ordered these people around, and shouted down anyone who opposed me. *most of whom did not know me*
It was a rough few hours. The water main had been bypassed years ago the 'kids' I brow beat into finding the mains found it but the valve was inoperative. The city was called, (by convincing a kid to call his girl and have her call in a water leak report) and the city eventually shut the water off. The cops were deflected, by me and the shop owner (who had the gift of knowing when he was out of his depth) The job was completed. No one was arrested or prosecuted. Mission accomplished.
I made some powerful friends. I made some bitter enemies. I do not regret the things I said, or did. No one else present had the balls to do what needed to be done. What I did worked, and that was for that brief time period was exactly what needed to happen.
Some of those 'kids' were so pissed by my 'harsh' approach that I was threatened, publicly shamed, and it let to a few really stubborn ass-hats getting their asses kicked. Two by me personally, (when they tried to jump me) and three others by people who realized I had been for that moment the most effective leader they had seen in their short lives.
Sometimes leadership does not appear until it is needed. I'm not going to say what Linus did is right or wrong. I have read the thread, but I don't think we have all the details. IMO: That man is a gifted leader. I'd give him the benefit of the doubt. If this maintainer worked with Linus for four years, he knows the score... and knows what Linus expects. Nuff said.
If the majority involved in MY little moment of 'management under fire' had not agreed with me. I would not likely be writing this now. I'd have caught some bullets... that is the kind of crowd I was dealing with.
Happy New Years!
+1
Most of the reason for using exotic alloys is to overcome weight vs strength problems in getting stuff out of the gravity well. If the interesting chunks of asteroid are blends of materials who cares? Dig chunks of it out, assess its bulk properties and fuse into desired shapes as is. For extra points, grind up the output of various deposits and blend the gravel to the approximately the right composition and fuse it into shape.
We don't worry very much about the exact composition of (for example) red-brick. We simply measure its bulk properties and use it accordingly.
The only time refining would be useful is if particularly valuable materials were present in the asteroid in quantities large enough to bother. In that case just carve the ore-body out of the asteroid, fuse it into bricks, and drop them back to earth in a reentry container.
Likely, only long lived radiological ores, and a few metals would be worth the hassle.
TL:DR: art is what you experience. YMMV.
This is really in reference to both you and the GP.
Digital or Analog: it does not matter.
With some exceptions due to cheaply made audio digitizing gear, there is no reason to capture audio with anything but the cleanest path you can manage.
At 96KSPS and 24 bits you can capture everything from a cockroach fart at 50m to a F-22 raptor in full afterburner right on the mic. The real limitation is the microphone. So lets assume that some mic diaphram made of di-unobtanium-obscurium can provide perfect, flat, sensitivity for the full range. It is indestructible, it has no mass, and responds precisely and predictably from 0.1 Hz up to 48Khz in a perfect cardoid pattern with no side-lobes.
We capture a live sound-field in stereo with a nice X-Y config and low and behold we a have a pristine recording of that field. Every single pressure transient that the ears can possibly respond to is perfectly represented in the data stream.
It sounds like hammered shit. Why? Because the ears do not work the way the above recording chain does. Well, ok that is fine. What we want is all there. Everything is there. Or is it? Well, I could go into a massive digression into why a two mic stereo recording setup is not even close in terms of capturing a sound-field as a person hears it, but I am not going to write a book on psycho-acoustics here.
We had a reason for digitizing this particular sound-field. There is a woman singing in the room near the mics. She has headphones on and she is singing to a recording of the backing band that is part of the recording sessions for her next album.
In the recording of this woman's singing we have captured a lot of 'stuff' that really is not part of the performance. And though it is not 'noise' in the classic analog sense of the word, it IS 'noise' in the perceptive sense since it competes with the singer's voice for our attention.
In the older analog recording approach we avoid recording anything we don't want and there are tradeoffs in suppressing some components of the sound field and enhancing others. A large part of what a recording engineer does is sculpting the pre-recording signal chain to min-max the desired elements of the subject.
In the digital recording system we could use the same approach and get the same tradeoffs. The final result will sound like an analog recording. Because the only thing different is the point at which the Analog to digital conversion takes place. We could digress here about distortions introduced by the recording medium ad nausium and get nowhere. At 24 bits the 'noise floor' of decent recording system (and not even a very expensive one) is so low that you could not hear it even if you put isolation-headphones on and cranked the monitor amp to '11' (Do not try this at home!) the damned headphone amp would make more noise!
So we have a (nearly)'colorless' recording system with no distortion in the human hearing regime.. why does it suck ass when we listen to the unaltered output of a perfect recording-chain?
Because we have trained ourselves to accept and interpret signal distortion. Depending on our personal interests, and how we were raised, how we damaged our ears, the types of distortion and quantities of distortion we process are as unique as the shape of our skulls and the meaty bits around our ears, including the various bangles we choose to staple to to them. This, and much more, strongly influences what we hear and how we interpret what we hear.
From the sound-fields we listen to, we try to extract (quite literally) exactly what we want to hear. If what we want to hear does not exist in a recorded sound-field, well guess what⦠we don't like that recording.
So now we go back to the 96KSPS 24 bit signal chain it is as perfect as it getsâ¦. might as well be a block of marble. Because what needs to be done to it is to start chipping away anything that does not support the performance of that woma
That tone was probably the Horizontal interval. The tone is really quite loud in CRT TVs because it is caused by the deflection yoke on the tube changing shape as it is excited into creating a rather large magnetic field by the deflection amplifiers.
for NTSC it is 15750 Hz
for PAL it is 15625 Hz
The next generation of kids will be able to here those pitches just fine thanks to the demise of CRT display systems.
What the SE crew did to keep their site up was amazing. They got no help from their site until way late in the game.
They counted on Peer1 to handle facilities... and they dropped the ball.
I have had multiple 72 hours outage due to local power going away. Having to plan to have fuel delivered to the backup gen-set, and having to ration power (I knew the burn rates and what equipment was non-essiental)... blah blah blah.
The bottom line is that the customers are not in the NOC, so if the organization cares about its customers... what needs to be done gets done.
Peer1 abandon ship for two days and left THIER customers to fend for themselves... and then treated them poorly when they came back to restore the services they failed to maintain during a crisis that while bad was not insurmountable.
Peer1 should get shutdown for failing to cover their end of the bargain.
When making commercial dough... say for Pizza... (which I am most familiar with.)
50 lbs bag of mix is combine with a specific amount of water at 110F. This then mixed for a specific number of minutes, poured into a food grade 'garbage bag', sealed and allowed to rise for 18 hours in a 44F cooler.
By specifying the temp and volume of water the mixture is extremely consistent assuming the 'doughboy' follows the spec.
... is a really, really bad idea.
The plastics used in IC packages tend to absorb moisture from the air. Over time this moisture gets trapped in the package. If you heat a plastic IC package that has been in service to 250C there is a pretty good chance it will 'popcorn' thus destroying the chip, and often visibly rupturing the package. It can be prevented by baking the board at 50 - 80C for 12 - 20 hours, but that is going to cause other problems. No one is going to be using reflow ovens to "reset" FLASH cells.
As others have pointed out spot-heating a FLASH block to 800C would take an almost trivial amount of energy, and would only need to be done when a block fails an erase-write cycle, or as an idle task performed on blocks that have been reassigned from the 'in-use' pool to the 'dirty' pool, but have not yet been erased and assigned to the 'free' pool.
The hardware required to implement this on an existing flash design would be almost trivial.
Easier to deal with is the 2 second rule. Watch for a road feature, discoloration, crack, paint line... etc. When a noticeable feature is revealed from beneath the car ahead of you, begin counting... One-one-thousand, two--one-thousand. If the feature you are paying attention to disappears below your hood, you are too damn close. This works at all reasonable driving speeds. At very low speeds ( 6 mph) you should be able to see the road and the point where the rear tires of the vehicle in front of you contact the road. This is also true if you are stopped in traffic. Cant see their rear-tire patch? You are too damned close.
Personally I like to keep a 2.5 second gap at speeds greater than 45mph, incase the car(s) ahead of me drop something into the road. I've been doing this for so long it is automatic. I have never even come close to hitting a car in front of me, even when in on case the car ahead of me crawled up onto the Jersey Barrier... causing it to decelerate much faster than expected. I had more than enough time to check mirrors and get out of the lane.
Look at a Rorschach diagram in a mirror.... and it seems to be the same... the pattern is reversible so says the math.
Reality says... not. even. close.
bub.
Color me shocked. /s
1st gen iMacs shipped with a 56K modem installed, as well as a 10/100Mb ethernet port, IEEE-1394, USB 1.1, and audio i/o... MacOS(OSX didn't exist yet) supported all of the generic device classes except serial-stream (serial port adapters) without third party drivers.
PCs had USB on the Mobo back then (and even a few high end boards had 1394 ports) but Windows had terrible support for USB and 1394. Damn near every device required a OEM supplied driver. I still have a lot of polycarb plastic coasters from that era.
Hostess is owned by a group of vulture capitalist firms FTFY
I am not a crackpot.
Me thinks thou dost protests to loudly.
Sharp painted itself into a corner. The Board and Exec staff did it, and the shareholders have to suffer with it.
Happens all the time. So what!
Making bad choices in a volatile market will hurt... and may be fatal. To quote Queen: Another one bites the dust.
I have ever seen on /.
What a fucking waste of bandwidth.
Fuck you very much.
That is all.
Sorry for the second replay.
IF you had a 2% fail on assembly in a commercial environment... you'd be looking for a new job.
no nodes came ready
I'm going to assume that my comment was misunderstood.
When accepting new hardware it is typical to verify that it works.... THEN assemble it into the desired configuration. THEN verify that each sub-system is fully functional... at least all the I/O. These are basic functional tests... yes?
Where I have issue with the video is the lack of precautions taken during assembly...
That is all.
Maybe that 2% loss was due to sloppy ESD protocol? You'd never know, unless you take proper precautions, and vet nodes before final assembly.
Hey... but that is what ya learn in school, yes? To cross all the 'T's and dot all the 'I's?
NO grounding straps.
NO signs of any ESD precautions!!!
Lacking from the video is the debugging process.
Sure they built it in 2 days... but how many nodes came ready?
I was cringing through the whole video over their lack of concern for basic ESD prevention. They don't need to be wearing bunny suits or anything that extreme, but FFS.... could ya show a little bit of respect for the hardware? Heck even clipping the freaking base-plates to ground during assembly would have been more than adequate.
That video was like watching "OW MY BALLS" for geeks!
Yeah b/c you are an Anonymous Coward.
He was designing and troubleshooting analog and digital hardware.... radio and battery systems until the day he could legally tell his employer to fuck off and collect his Navy retirement and SSI...
He knows more about practical engineering than I ever will. And we still kick ideas around. He retired but did not stop being an Engineer.
I'm 46 and still writing code, and back at school for Biz Admin. I got to go back to my roots focusing on bare metal, and more recently embedded LINUX.
I'll stop writing code when you pull my cold, dead fingers off the keyboard.
No it is not if the process for handling postal voting is well established for the majority of voters in a district. (Or in my case the whole county) But during a FEMA disaster and an increased need.... there's plenty of room for grubby paws... and I think that is the concern.
Election Night.
*starts making popcorn.