Become a fan of Slashdot on Facebook


Forgot your password?

Comment Re:About time (Score 1) 241

Commute time is a personal choice. You can choose to live closer to work, and pay more in housing / get less space, or you can live further out of the business districts, get a bigger house but have a longer commute. By making commute time count as work time, we are effectively subsidizing those who live outside of city centers, encouraging longer commutes, and wasted time.

Comment Re:Changing landscape (Score 2) 367

A root of this issue is the 18th, 19th and 20th century concepts of employees / employers and an outdated set of definitions. Like so many modern issues near and dear, we will have to reassess out fundamental assumptions about all kinds of things, this being just one.

I disagree. The fundamental concepts of employee and employer are as true now as they were then. It may take some time, but modern-day legal tools are more than capable of sorting out uber's employment issues without any fundamental shift in thought.

Comment Re: Apple - What's Happening in France (Score 2) 233

It's France, they do strange things in Europe. For instance when Muslims kill French people, the French respond by harassing Jews. It's not for us to judge, it's a part of the rich European cultural heritage.

It's Slashdot, they do strange things on the Internet. For example, when a poster discusses the use of Apple computers, the trolls respond by bringing up islamophobic ideas and allude to the holocaust. It's not for us to judge, it's a part of the rich Internet cultural heritage.

Comment Re:Not Very Hard (Score 1) 285

Another hated class of bugs are library bugs. These may actually be quite easy to debug, but they force you to go into someone else's spaghetti code and spend countless hours becoming a master of some library you'll never use again.

And the worst part is that often they aren't really bugs, but programming errors as a result of crappy documentation.

Comment Re:Not Very Hard (Score 1) 285

I had a race condition in my code, my product would crash randomly once every few days or weeks. I killed myself trying to reproduce it reliably. I wrote software that would instrument the code, adding random sleep timers between each line. That didn't work. I eventually went line-by-line trying to deduce the issue, and found two potential bugs by thinking through it. I never knew which of my two fixes fixed the issue (or if either did), but I never saw the bug again.

Comment Re: Only? (Score 1, Insightful) 664

The harassment (not physical attack) is well deserved. The perception of an invasion of privacy is enough to rightfully make someone angry.

If someone held a camcorder to your face, but told you it wasn't on because the red light was not on, you would still feel uncomfortable. That person would still be a jerk.

Comment Re: Do what everyone else does in this situation (Score 1) 233

but Adobe never did understand the value of efficient data structures.

They developed the PDF standard, which was designed from the ground up to be transferred in a stream and rendered quickly. Don't hate the tech just because they're a proprietary company.

Comment Not Very Hard (Score 2) 285

Many of the "hard" bugs discussed in the article do not seem very hard. Divide by zero errors and a +Inf in an input file are straightforward issues that should be caught using standard practice techniques (bounds checking and exception handling). Two of these three hard bugs would have been easy to catch with version control and continuous integration. It seems like the article is more about dealing with other people's crappy code and poor software development practice rather than debugging nasty bugs.

The nastiest bugs are almost always race conditions, which are by their nature non-deterministic and may not be reproducible across time or certain hardware.

Comment Re: Compiler optimizer bugs (Score 1) 285

I worked in the embedded space for a few years with an in-house built compiler and came across a few compiler bugs. They were all very easy to debug. You would write some code like "int foo = bar++;" and the program would crash on that line. You'd scratch your head for a minute, but check out the assembly and see some weird optimization it was doing.

"The urge to destroy is also a creative urge." -- Bakunin [ed. note - I would say: The urge to destroy may sometimes be a creative urge.]