Follow Slashdot blog updates by subscribing to our blog RSS feed

 



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: Non-Issue (Score 1) 386

by Kyru (#33895424) Attached to: Devs Grapple With 100+ Versions of Android
This is completely a non-issue, the majority of people are on the main builds and you can specify in your program what firmware and hardware it requires so that it doesn't show up for people that can't run it. I'm not too worried about developing for the 3 people running Bub's AOSP Magic "Original" v 0.3.3. Fragmentation is a boogie-man and nothing more.

Comment: One size turnaround time doesn't fit all (Score 1) 418

by Kyru (#21342433) Attached to: How Fast is Your Turnaround Time?
It really depends on the system, the problem and the people involved. The system we run where I work has changes put into it in production daily with turnaround times anywhere from an hour to several weeks depending on the change. We have some customers where a fix can be worked on and implemented over the course of weeks due to testing and they have no problem with that and we have customers that expect things to be fixed later today. The real question to ask yourself and your team is is it reasonable in your product or system to be able to turnaround something that fast?

Any sufficiently advanced technology is indistinguishable from a rigged demo.

Working...