Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

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:Another type that is interesting... (Score 1) 717

by Radres (#46259693) Attached to: Your 60-Hour Work Week Is Not a Badge of Honor

The problem is that it's near impossible to say with certainty whether those issues created by that developer were unavoidable as part of doing the job. Many times bugs are the fallout from dysfunctions either in the team (poor requirements, planning) or in the technology (buggy, poorly-implemented abstractions that the developer is forced to build on top of). Of course it's reasonable to blame it all on the incompetence of the developer, but in some cases it genuinely isn't his fault despite his name being attached to the bug.

Comment: Re:Die already Blackberry (Score 1) 120

by Radres (#44911039) Attached to: BlackBerry Confirms 4,500 Job Cuts, Warns of $950 Million Loss

No, he's saying that we shouldn't be rooting for companies to fail. What does the world gain from a company like RIM failing to produce great, new products? BB may be obsolete tech, but I'm sure somewhere along the line someone could have done something to diversify RIM's portfolio to keep that company afloat.

IF I HAD A MINE SHAFT, I don't think I would just abandon it. There's got to be a better way. -- Jack Handley, The New Mexican, 1988.

Working...