Follow Slashdot stories on Twitter


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:Data Breach (Score 1) 385

by Karnak23 (#38982083) Attached to: Ask Slashdot: How To Deal With Refurbed Drives With Customer Data?

Good point about the Data Breach Incident. Granted, NewEgg is not in the business of wiping drives but if this does qualify as a DBI then NewEgg may have some liability here. This would be similar to pawn shop owner that receives and resells stolen property. Even if the owner wasn't aware that it was stolen, they still have some liability if they didn't do their due diligence to find out.

IANAL, but you might consider sending the drive back and explaining the situation to NewEgg. If it's not a DBI, they'll wipe the drive and restock it. If it does qualify as a DBI, you might just have spared them some legal hassles.

Just my 2p.

Comment: The Curse of "Granularity" (Score 0, Flamebait) 274

by Karnak23 (#28839705) Attached to: Manager's Schedule vs. Maker's Schedule

Unfortunately, managers love the term "granularity" and have been using it as a cudgel. They've locked on to "Agile" programming and SCRUM project management as methods for driving this granularity into the development and test processes. They want tasks broken down to 15 minute increments and balk when any task takes more than a couple of hours to complete. All this so that they can achieve "visibility" and "predictability" for a given project, i.e. they get more status reports with pretty charts and graphs. I really despise the term "burn down" which springs from the whole thing as well.

Now, I may sound bitter about this but, I do understand that for all parties involved in a project, especially a large scale project; there needs to be an understanding of where team is at, where it's headed, and where the bottlenecks are located. This is not any easy problem to solve; it involves lots of guess work and dependency graphs that would make Euler weep. I suppose that's what makes it all the more irritating when managers think they have yet-another-silver-bullet for project management that they misuse causing more Maker frustration and possibly increasing the chance for failure rather than ameliorating it.

Sorry, end of rant.

What is worth doing is worth the trouble of asking somebody to do.