Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Users don't report bugs (Score 1) 309

The meat of this answer is good... with more detail that answers some of the rebukes:

The corollary I would make is to my other life in the Sound Engineering business. My golden rule is I never tell an engineer what's wrong with their mix during a show (and only after if they specifically ask for my feedback) and similarly wish others would follow the same rule. This is because: 1) If we can't hear it we're probably not going to do a good job of fixing it. and 2) Chances are we actually already know about it and are either working on fixing it OR it's something fully broken that we're currently incapable of doing anything about.

How this ties: Terminology aside, users *should report issues. Feedback is important and a stream of information (provided you have the processes / resources to get useful information out of it) is a good thing. BUT any "work order" that goes to the devs shouldn't come from that stream of consciousness. Any "bug"/"feature request" should be verified by QA / product management (for features) before change work moves forward. For what are really "Feature Requests" this is fairly straight forward. Whomever is responsible for controlling feature creep and project scope needs to gatekeep those. For what are truly "Bugs" you similarly need to be able to triage what gets fixed and when PLUS if no one in house (QA/etc) can verify or reproduce the bug then just like my above example how are the devs expected to properly fix it. This is essentially TDD: QA creates a reproducible test that confirms the bug and the devs fix the problem until it passes the test.

SO with a proper "intake" process your devs aren't working off of some user bug that the user needs to validate. They are working on a fully qualified bug report that QA has created and verified so that once fixed QA is fully capable of validating the fix is in (and in conjunction with a proper regression suite also that it didn't break anything else along the way).

In a small shop where there aren't separate layers of QA / Prod Mgmt / etc the above functions may be consolidated into what may be a single "dev" BUT the process is the same. You can't fix what you can't see (reproduce) so go through that work first and the rest sorts itself out.

Comment Re:Should I care? (Score 1) 316

The studios are complaining because they aren't maintaining their DVD revenue in *addition to their streaming / licensing revenue. To be completely blunt I don't fucking care. They will always whine when they don't think they are making the maximum possible money. The truth is we can't tell the real economic impact with the data in the article. The only math that matters is this: If $DVD + $NETFLIX >= $DVD-ONLY then the model is working. If $DVD + $NETFLIX $DVD-ONLY then the studios have an argument for harm. We don't have enough information (right now.. I'm sure it's out there) to fill in those equations at the moment but I have a strong feeling (backed by the opening line "Studios are making millions off of streaming services" that the Studios are doing just fine they are just bitching because their DVD-specific revenue is showing a decline.

Comment Re:Not an alternative to Linux, an alternative to (Score 1) 277

Ya.. the "sea of a billion drivers to support" issue is also just as good on a Dell where they work closely enough with MS to have the same universal driver support. There are some aspects of Mac Hardware I would like better (weight and battery life being the biggest) but that is secondary to the flexibility / upgradability / ports / "real" docking station / etc that I get with my Dell hardware.

Comment Re:Cold weather? (Score 1) 198

Not necessarily out of scope but not nearly as friendly... with Tesla's current superchargers (as described in TFS) you would need to do that trip in 3 legs with a half hour stop each to recharge. With a 15% reduction you may need to make that 4 legs.

That vs your average IC care these days that could do that trip easy in one leg.

The features of Samsung's new battery brings EVs WAY closer to practical for a long-distance driver.. not on par with the range of an IC car but back to the old standard of "300 miles / tank of gas" we had before Hybrids and fuel efficiency gains bosted that number much higher. Think of it like SSD vs. Spinning Disc. Early on the price / capacity was unaffordable for most. As manufacturing and tech improved Disk Drives still have significantly more capacity / $ but not quite the gap there used to be. Hybrid cars will have better time-to-fill vs. range for the foreseeable future just because batteries take longer to charge than it takes to shove liquid into a tank but the EV cars are at least approaching "good enough" for most people to be able to make the trade-off.

My only hitch with Samsung is that 5 years off is a long time in the tech world.. I would hope such specs would be available sooner than that (purely in terms of the batter gains we've made in the past 5 years)

Comment Re:its a white dragon. (Score 1) 414

Not even "pilot" ... look behind the scenes at any given McDonalds and they are automating processes all over the place. There is plenty of human interaction still but they are slowly squeezing the humans into the smallest space in the process they can.

Honestly I see all of this as a "Good Thing". The problem lies in how our society is slowly degrading the safety net that makes this "Good Thing" work for all. If we automate away all of the jobs that machines can do you *should end up with workers heading in 3 directions: 1) The people who make the machines. 2) The people who service / run the machines. 3) People who are not skilled enough to do either. In a society with a proper safety net that third category can survive on their (low but adequate) safety net and don't need to do some menial task to justify their sustenance pay. If they want more out of life they can strive to better themselves but I don't really care if someone instead chooses to sit around and do squat. It's their life to waste.

Comment Apples and Spotifies and Oranges (Score 1) 220

Their comparison between what Spotify has paid them and what YouTube is paying them is a pretty poor comparison. On Spotify, the vast majority of the music played incurs some for of royalty. On YouTube, although there is a lot of copywritten material out there for sure, the bulk of the content does not necessarily incur royalty costs.

The comparison maybe would have been valid if they had qualified it with "For the same about of copywritten material viewed on YouTube vs played on Spotify, Spotify paid us double the royalties."

It's loosely equivalent to some Minneapolis politician complaining about how much less toll revenue they get compared to Chicago when a large number of Chicago's freeways are tollways and Minneapolis only charges for express lanes (when you're not a carpool).(I know the analogy is a bit of a stretch but it's been a long day.. gimme a break!! ;)

Comment Re: Sack of salt (Score 1) 103

You realize that most of the 240Hz TVs that were sold were designed for 3D capability? 120Hz for a mono image is a nice round number because it can support both primary content frame rates evenly. For a stereo image (how most 3D TVs work) you get half of the available frame rate per eye so to get that optimal 120Hz per eye you need a 240Hz TV.

Comment Re:Maybe we should mimic civil engineering (Score 2) 280

PS. To answer the original question: No.
In the sense of how the question was asked, I have never produced any software that I'm ashamed of what it is used *for.

BUT there is plenty of code I wrote when I was younger / less experienced that I'm kinda ashamed I wrote... I could write it SO much better today :)

Comment Re:Maybe we should mimic civil engineering (Score 1) 280

Your example isn't as far off as you think:

One of the biggest conspiracy theories around 911 (Please not getting into that argument just an example) is that the building were *designed to withstand an airliner impact and so should not have collapsed. Lawsuits after the fact take such things into consideration:
If your building is not designed to such standards and a plane flies into it it is expected to fall and liability fall almost entirely with the terrorist. (I know there are exceptions... just in a "sanish" world.) BUT if your building is designed to withstand an airline impact and the building still falls because of faulty design then chances are more likely you'll win a lawsuit against the design firm and maybe the construction firm, etc.

Here in MN we had another excellent example: The 35W bridge that collapsed. There were *tons of lawsuits after that one and culpability fell on many groups. The bridge was designed to withstand a certain amount of weight but was also many decades old. It was a poor design in-general which is called "fracture critical" where a single failure can lead to total collapse. At the time it fell there were 100s of tons worth of construction trucks all being parked on the bridge along side regular rush hour traffic (think of these trucks much like the terrorist in the first example). You also had state inspectors who had been (or maybe not so much as they should have) regularly checking the bridge to validate its safety. *ALL of these groups were found liable to some extent and had to pay out settlements.

If you sell software or a service that has a contractual promise of a certain level of security or stability and that software doesn't live up to that spec there are all sorts of lawsuits involved. If you are in a software business where lives are on the line (Health Care, Weapons / Aerospace Tech / etc) then you can be damned sure they'll be coming after you if someone's life is lost. There isn't some magical bubble that keeps us developers from liability for the tools that we produce. The IS however a more acceptable level of lack of perfection given the natore of how complex the systems we create are and, frankly, how much did you pay us to build it right.. what promises did you pay me to live up to.

Comment Lies, Damned Lies and Statistics! (Score 1) 165

"citing a poll commissioned by London & Partners, the mayor's economic promotional company"

As Slashvertisements go this one is a bit more like news BUT it's still PR. Of course the Mayoral commissioned poll is going to show whatever the Mayor needs it to show. And of course the papers are going to let the Mayor get in all of his sound bites as he scrambles to lessen the impact Brexit will have on his people (bottom line).


Slashdot Top Deals

"Gotcha, you snot-necked weenies!" -- Post Bros. Comics