itwbennett writes: Proponents of Mob programming, an offshoot of Pair programming in which the whole team works together on the same computer, say that it increases both quality and productivity, but also acknowledge that the productivity gains might not be readily apparent. "If you measure by features or other classic development productivity metrics, Mobbing looks like it's achieving only 75 to 85 percent of individual or Pair output for, say, a team of six or seven working for a week," says Paul Massey, whose company Bluefruit Software is a heavy user of the Mob approach. So, where does the productivity come from? Matthew Dodkins, a software architect at Bluefruit says the biggest gains are in code merges. "In a day spent using traditional collaboration, you would have to first spend time agreeing on tasks, common goals, deciding who's doing what... and then going away to do that, write code, and come back and merge it, resolve problems," says Dodkins. By bringing everyone into the same room, "we try to merge frequently, and try to do almost continuous integration." Matt Schartman, whose company Appfolio also uses Mobbing and wrote about his experience, gave Mobbing high marks for producing a quality product, but didn't find that it improved productivity in any measurable way.
No need to read further than the poster's ID
Is this due to the website detecting your OS through a message from the browser, and telling you to fuck off, or some kind of actual incompatibility in the browser software on that OS?
there'd be no need for tinkers
pev writes: I'm working on an embedded project that will need to be maintainable for the next 25 years. This raises the interesting question of how this can be best supported. The obvious solution seems to be to use a VM that has a portable disk image that can be moved to any emulators in the future (the build environment is currently based around Ubuntu 14.04 LTS / x86_64) but how do you predict what vendors / hardware will be available in 25 years? Is anyone currently supporting software of a similar age that can share lessons learned from experience? Where do you choose to draw the line between handling likely issues and making things overly complicated?
The future favours cross-platform apps
An anonymous reader writes: The Atlantic has an article asking whether autonomous cars need windows. If there's no driver, will the passengers want to look outside? In the summer, will anyone want to endure the relentless heat from the sun? The robot cars offer us a great opportunity to rethink the platform which is largely devoted to supporting the driver. But if a computer is in charge and it sees with dozens of cameras ringing the car, what else can we change? What else don't we need? What can improve?
snydeq writes: InfoWorld's Paul Solt argues that It's high time to make the switch to the more approachable, full-featured Swift for iOS and OS X app dev. He writes in Infoworld: "Programming languages don't die easily, but development shops that cling to fading paradigms do. If you're developing apps for mobile devices and you haven't investigated Swift, take note: Swift will not only supplant Objective-C when it comes to developing apps for the Mac, iPhone, iPad, Apple Watch, and devices to come, but it will also replace C for embedded programming on Apple platforms. Thanks to several key features, Swift has the potential to become the de-facto programming language for creating immersive, responsive, consumer-facing applications for years to come."
reifman writes: Hosting a website (even WordPress) after your death has a variety of unexpected complexities, from renewing your domain name, to hosting, security, monitoring, troubleshooting and more. It's a gaping hole that we as technologists should start thinking more about — especially because all of us are going to die, some of us unexpectedly sooner than we'd like or planned for. The only real solution I found was to share credentials and designate funds to descendants — you've done this, right?
New submitter sundarvenkata writes: I am sure most slashdotters (including the ones who had the I-am-an-indispensable-snowflake stance in the past) have already foreseen the writing on the wall for the future of tech professions (with IT being the worst hit) given some of the ominous news in the past few years: here, here and here. Of course, there are always the counter-arguments put forth by slashdotters that "knowing the business" or "being the best in what you do" would save one's derriere as if the offshore workers will remain permanently impaired of such skills. But I was wondering if some slashdotters could share some constructive real-life experiences of planning a transition to a relatively offshore-proof career. If you have already managed to accomplish such a career change, what was your journey and what would your advice be to other aspirants?
Facebook I mean
Psychologists who collaborate with torturers are ethically complicit. Boycotting the torturers is the only ethical stance here.
Just get a Google phone