In 2005 at my job we had a pretty severe problem just as unexplainable. The day after an unscheduled closing (hurricane), I started getting calls from users complaining about database connection timeouts. Since I had a very simple network with less than 32 nodes and barely any bandwidth in use, it was quite scary that I could ping to the database server for 15-20 minutes and then get "request timed out" for about 2 minutes. I had performance monitors etc. running on the server and was pinging the server from multiple sources. Pretty much every machine except the server was able to talk to the others constantly. I tried to isolate a faulty switch or a bad connection but there was no way to explain the random yet periodic failures.

I asked my coworker to observe the lights on a switch in the warehouse while I ran trace routes and unplugged different devices. After 45-50 minutes on the walkie-talkie with him saying "ya it's down, ok it's back up," I asked if he noticed any patterns. He said, "Yeah... I did. But you're going to think I'm nuts. Every time the shipper takes away a pallet from the shipping room, the server times out within 2 seconds." I said "WHAT???" He said "Yeah. And the server comes back up once he starts processing the next order."

I ran down to see the shipper and was certain that he was plugging in a giant magnetomaxonizer to celebrate the successful completion of an order. Surely the electromagnetic waves from the flux capacitor were causing rip in the space-time continuum and temporarily shorting out the server's NIC card 150 feet away in another room. Nope. All he was doing was loading up the bigger boxes on the pallet first and then gradually the smaller ones on top, while scanning every box with the wireless barcode scanner. Aha! It must be the barcode scanner's wireless features that probably latch on to the database server and cause all other requests to fail. Nope. Few tests later I realized it wasn't the barcode scanner since it was behaving pretty nicely. The wireless router and it's UPS in the shipping room were configured right and seemed to be functioning normally too. It had to be something else, especially since everything was working fine just before the hurricane closing.

As soon as the next time out started, I ran into the shipping room and watched the guy load the next pallet. The moment he placed four big boxes of shampoo on the bottom row of the pallet, the database server stopped timing out! This had to be black magic! I asked him to remove the boxes and the database server began to time out again! I did not believe the absurdity of this and spent five more minutes loading and unloading the boxes of shampoo with the same exact result. I was about to fall down on my knees and start begging for mercy from the God of Ethernet when I noticed that the height at which the wireless router was placed in the shipping room was about a foot lower than the top of the four big boxes when placed on the pallet. We were finally on to something!

The wireless router lost the line-of-sight to the outside warehouse anytime a pallet was loaded with the big boxes. Ten minutes later I had the problem solved. Here is what happened. During the hurricane, there was a power failure that reset the only device in our building that wasn't connected to a UPS - a test wireless router I had in my office. The default settings on the test router somehow made it a repeater for the only other wireless router we had, the one in the shipping room. The two wireless nodes were only able to talk to each other when there were no pallets placed between them and even then the signal wasn't too strong. Every time the two wireless routers managed to talk, they created a loop in my tiny network and as a result, all packets to the database server were lost. The database server had it's own switch from the main router and hence was pretty much the furthest node. Most other PC's were on the same 16-port switch so I had no problems pinging constantly between them.

The 1-second solution to this four-hour troubleshooting nightmare was me yanking off the power to the test router. And the database server never timed out again.

Around this whole thing, there seemed to be this aura of "teehee, it's ok, we're on the internet!"

It seems like they don't believe they could have possibly done anything wrong.

It's not that I can't imagine the glee they'd feel when they were offered the opportunity to buy the prototype. But since that glee was not followed up by any second thoughts -- for exmaple, about receiving stolen property, or trade secrets, or hey, ethics -- then they deserve what they get, legally speaking.

Anybody who thinks about it for a minute would realize that buying a prototype device that "got found at a bar" ("fell off the back of a truck"), made by a company with notoriously tight seals, and a huge legal team, and then explaining to the world that you bought it off some dude… well, that's gonna have consequences.

If bloggers aspire to be journalists, they're going to have to learn to have those second thoughts.

And learn that "checkbook journalism" just flat-out doesn't count. Even when they're paying people for interviews, instead of buying hot goods.

A lot of comments on TechCrunch revolved around being treated badly. If you’re lucky you have a boss that’s passionate about what they’re doing. If so, such bosses will get heated and yell because they care.

Yeah, right.

I don't work well while being yelled at. I don't want to deal with that. And so I refuse to work in environments where I get yelled at. Seriously, if you're my boss and you yell at me, my resume is being updated that night and I'm going to shop it around. If you're my co-worker then I'll wait until you calm down some, and raise the issue. If I don't get an apology then I'm going to either my or your boss about it depending on the political dynamics of the company. If the company doesn't agree that you were out of line, I'm going to find another job and go.

And yes, there are people I've worked with that have broken this rule which I choose not to work with ever again.

Now I understand that some people, cultures, etc differ. In some yelling is OK. That is fine. I choose not to be in those ones. And I'm far from the only person who feels this way.

So if you're a boss and you yell, take a moment to consider this. No matter what excuses you give yourself for your crappy behavior, are you losing really good employees because they don't agree with you on this issue? After you've thought about it for a while, perhaps you'll find better ways to handle stress than yelling at people below you in the hierarchy.

Well put.

Either way, your master images should be the format you first obtained or created the image in. If the image came from a camera, the master should be the raw camera image. If the image was created in photoshop, the master should be a photoshop file.

http://www.leginfo.ca.gov/cgi-bin/displaycode?section=evid&#...