Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment Re: "probably" much higher? (Score 2) 196

I'm not saying corruption is good, I'm just saying fraud != corruption. Medicare fraud, where bills are issued and paid for services that did not take place, is not the same as corruption. The article cited even mentioned that basically all bills are paid, and that they try to find the fraud after the fact. So, no preferential treatment, no deliberate intervention by officials, not corruption. Not good, but not corruption.

Also of note, the $130 billion is not the amount of corruption, it is the cost to the economy in loss of growth.

Comment Re: Editorial bias... (Score 1) 249

Yes, 70% of browsers supported regions, but that leave 30% that don't. If you're designing a website that ~1/3 of users can not view properly, I think we can assume you're doing something wrong.

This brings us to an issue that the article doesn't seem to address, just how widely used are regions? Is the average Chrome user even going to notice the loss of support?

Comment Re: The other Side of the story (Score 1) 767

Wrong on many levels.

Chickens will respond just fine to 3k~4k fluorescents (metal halide or high pressure sodium work fine too, but I don't need that much light).

Houses built in the 30s were pretty rarely insulated, and even more rarely wrapped with a vapor barrier. This was a relatively common building practice until after WWII. (Remember, building codes and inspections didn't really begin until the 60s) The engineering necessary to circulate air using nothing but the convection currents caused by light bulbs would be daunting even with today's computing power.

Modern homes are wrapped up pretty tightly, but they rely on mechanical air movement (either forced air heating, or a whole house fan).

Comment Re: Efficiency. (Score 1) 937

But, what happens when the stupid meat-bag in the "driver's" seat decides to hit the brakes, or fiddle with the steering wheel while in a train? Or a tire blows out? By the time you're close enough to draft the car in front of you, I would imagine you are too close for even a computer to avoid an accident (mechanical limits vs. reaction times).

As much as I would love to see this, I don't think we will until there are no manual controls inside the car.

Submission + - Peakl Oil Threat Gone - Era of Cheap Biofuels finaly here?

Bodhammer writes: Pacific Northwest Nation Labs has developed a new technology that turns algae to crude in an hour. This press release http://www.pnnl.gov/news/release.aspx?id=1029 describes process and the partner they have selected for the pilot plant. The process is efficient and produces crude oil which can be traditionally refined, clean water, gas which can be burned or cleaned to make LNG, and nutrients that can go back into the process. Is this the end of the Peak Oil threat?

Submission + - No security ever built into Obamacare site: TrustedSec CEO (cnbc.com)

schwit1 writes: Dissecting the critical security problems with the website Healthcare.gov, with TrustedSec CEO David Kennedy. "When you develop a website, you develop it with security in mind. And it doesn't appear to have happened this time. It's really hard to go back and fix the security around it because security wasn't built into it. We're talking multiple months to over a year to at least address some of the critical-to-high exposures on the website itself."

Another online security expert—who spoke at last week's House hearing and then on CNBC—said the federal Obamacare website needs to be shut down and rebuilt from scratch. Morgan Wright, CEO of Crowd Sourced Investigations said: "There's not a plan to fix this that meets the sniff test of being reasonable."

When it comes to securing personal information online, Kennedy cited Amazon, Facebook, and Twitter as models for the industry. He even said the IRS website does regular testing to help "ensure that when the websites come out they're protected."

Submission + - On duty or off duty, on-call, and waiting to engage or engaged to wait 2

An anonymous reader writes: I have a question on labor law for the Slashdot crowd. My circumstances should be similar enough to others that I'd like to hear how others handle it. I work for a small, privately held company. My employment contract states that I am a full-time employee, non-exempt, hourly. My company leases equipment to smaller companies where it does not make financial sense for them to outright buy their own. My division provides field service on this equipment, as well as on equipment owned by other companies. My division is small, with a couple dozen of us spread geographically across the U.S. Essentially, the job is to await a service call that the equipment is broken, get to the site as fast as possible (some close enough for driving, some require flying to, even by the same primary) and fix it. We each have our own geographical area of responsibility (the secondary is not called unless the primary is otherwise engaged). We have "normal" business hours, M-F, 8am-4:30pm. We work after hours and on weekends as required.

I have worked in this industry for almost 20 years, though not long at this company. In every other instance, I've been paid for 8 hours per day, plus overtime is paid if I go over 40 hours for the week (or over 8 in the day for companies that adhere to CA policies). This company does not. We have been instructed to leave our time sheets blank until a service event occurs, then fill it out. At the end of the week, we are to then go back and fill "non-service hours" so that we reach 40 hours for the week, which is what they now claim is all that they guarantee. If I do not receive a single service call for the week (unfortunately, this happens), I am paid the 40 hours.

The issue is what then happens when I do have a service event. My closest site is a 3-hour drive each direction. Coupled with 5 hours of labor (very common), the day ends up being 11 hours (not counting breaks or meals). So a week with just one service event would, elsewhere, show 43 hours (40 regular + 3 OT). This company counts it as 40 regular hours. The 3 extra hours are deducted from the "non-service hours" that they have us record to get up to 40. It's even more of an issue when I work 15-hr days W-F and they go back and deduct the 16hrs from M & T.

Effectively, they're making the determination on whether or not to pay after the fact. When I talked with the VP of HR about it, they claimed that I'm an "on-call employee" (contrary to what my employment contract states, and contrary to any written policy) and they don't have to pay me unless I'm actually at a job site. I asked if I called the home office at 8am, would they tell me that I was on duty that day. They said yes. I asked if I called back at 4:30pm and asked if I was on duty that day. They said yes. So you have to pay me for those hours worked. Depends on whether or not I did "productive" work (which they define as being on-site or traveling to/from). Can I drink? No. Can I go to the lake? No. Can I go see a movie? No. Can I work a second job? No. Do I have to keep a Go Bag so I can jump on a plane at a moment's notice? Yes.

Has anyone else run into this situation? This is the first time in 20 years that I've been in this situation, and all the other jobs were just like this one (right down to immediate supervisor being over 1000 miles away), but there's never been a dispute over pay. Am I just completely misunderstanding Federal labor law?

And, yes, I am seeing an attorney who specializes in this field. I'm just curious if anyone else here has ever run into this.

Slashdot Top Deals

1 + 1 = 3, for large values of 1.

Working...