276 karma · joined April 24, 2012
python-- yaml--
Small point be social sourcing could generate a false positive unless you can verify said individuals interests.
Of course removing anything placed by warrant is possibly illegal irregardless of you position on it. {this isn't legal advice}
I'd also say this would take a significant amount of effort to validate and you're likely to find quasi poor information.
I rarely upvote, but I did this time.
Failures were more prominent in memory...but they did happen. We also sent equipment through environmental testing that would force failures. I don't recall of hearing of any CPU failures. Although most of our equipment was DSP & FPGA based but there were some tiny 'lil CPU's there.
Unless you have something in place, it's probably not worth much a legal action. Maybe some threatening phone calls, and letters from a lawyer. If they are BIG they will attempt to drive you to the ground.
Watch the video posted from Mule Design and take this as a hard lesson learned.
It's truly maddening that these people are just awful. I wish there were a way to get them to change their rules.
I'd spread them out, over a few locations but one is a personal and the other is small one for a couple sites that we host.
We are experiencing a power outage at NYC1 and have engaged Equinix to investigate. Mon Nov 25 02:27:11 2013
We have engaged our engineering teams to investigate temporarily scheduling delays. Mon Nov 25 02:07:32 2013
1. Get a job elsewhere 2. Hide in mediocrity because the effort to achieve a high ranking is greater than the reward by a lot.
In my personal experience with force ranking systems, is that it also drives politics within the organization. As an example:
I once was skipped a promotion because when we went to demo a unit the shipping department did a poor job packing the prototype equipment that I had just spent an entire summer building. Due to the packing job, a single RS-232 pin because slightly unseated causing intermittent behaviors for one of many features. It was still the most successful demo the company had ever given. So success we received a request for pricing the Military 24 hours later, which is unheard of. Despite this the Chief Engineer blasted me for the failure, and our inability to find the issue on site (mind you he was there too). When I brought this up at my review I was indirectly told by my boss that he didn't agree with my rating/rank but it was over his head. After that, I practiced both Items 1 & 2 but discovered that my new company also followed this practice. So it was a rinse and repeat to make sure force ranking is not within my new companies.
Thanks for posting.
I've had some thoughts at looking into FreeBSD but that's not Linux.
[1]http://reporting.sunlightfoundation.com/2013/aca-contractors...
Ugh this just makes me sad. I want to move to Portland next summer, and I've been watching for jobs in Portland. Right now I don't see any jobs but I keep seeing more, and more jobs in DC. I hate DC, I want out!
</rant>
I also see myself being in more management of programmers at sometime. It's pretty rare for me to trivialization a solution process. I've done it, but so has everyone. Making mistakes is the learning process.