An anonymous reader writes: For the better part of three years there has been talk about running Wine on Android to bring Windows x86 programs to Android phones/tablets, and it's going to become a reality. CodeWeavers is planning to release CrossOver For Android before the end of the year. This will allow native Windows binaries to run on Android, but will be limited to Android-x86 due to struggles in emulating x86 Windows code on ARM. The tech preview will be free and once published the open-source patches will be published for Wine.

An anonymous reader writes: This month Twitter is closing down the JSON endpoint API which thousands of third-party software and plugin developers have depended upon for years. The alternative Rest API offers data which is aggregated or limited in other ways, whilst the full-featured share data offered by Gnip (purchased last year by Twitter) can cost developers thousands per month to access — in one case up to £20,000 a month. The general objective seems to be to either drive users back to the core Twitter interface where they can be monetized via the social network's advertising, or to regain lost advertising by converting open source data — currently utilized a lot in scientific research — into premium information, offering the possibility for well-funded organizations to gain reputations as Twitter barometers without ever needing to expose the expensive, accurate share figures. The company also announced today that co-founder Jack Dorsey would be the new CEO.

szczys writes: The average age of Japan's rice farmers is 65-70 years old. The work is difficult and even small changes to the way things are done can have a profound impact on these lives. The flooded paddies where the rice is grown must maintain a consistent water level, which means farmers must regularly traverse the terraced fields to check many different paddies. A simple sensor board is changing this, letting farmers check their fields by phone instead of in person.

This might not sound like much, but reducing the number of times someone needs to walk the fields has a big effect on the man-hours spent on each crop. The system, called TechRice, is inexpensive and the nodes recharge batteries from a solar cell. The data is aggregated on the Internet and can be presented as a webpage, a text-message interface, or any other reporting scheme imaginable by utilizing the API of the Open Source software. This is a testament to the power we have as small groups of engineers to improve the world.

An anonymous reader writes: It's been five years since Oracle killed off OpenSolaris while the community of developers are letting it live on with the new OpenIndiana "Hipster" 15.10 release. OpenIndiana 15.10 improves its Python-based text installer as it looks to drop its GUI installer, switches out the Oracle JDK/JRE for OpenJDK, and updates its vast package set. However, there are still a number of outdated packages on the system like Firefox 24 and X.Org Server 1.14 while the default office suite is a broken OpenOffice build, due to various obstacles in maintaining open-source software support for Solaris while being challenged by limited contributors. Download links are available via the OpenIndiana.org release notes. There's also a page for getting involved if wishing to improve the state of open-source Solaris.

theodp writes: In an interesting contrast to the Disney princess-themed Hour of Code tutorial that 'taught President Obama to code' last December, Chile is kicking off its 2015 Hora del Codigo this week with a top-featured Blockly tutorial that teaches computer science by having kids drag-and-drop blocks of code to pick up dog poop. "Collect all the shit you have left your dog," reads the Google translated instructions for the final coding exercise. In its new video for the Hour of Code 2015 campaign, tech billionaire-backed Code.org notes that it's striving to reach 200 million schoolchildren worldwide by this December. Presumably towards that end, Code.org warns that it will penalize Computer Science tutorials that "work only in English."

Guinnessy writes with an interesting analysis of the Volkswagen software cheating scandal: Physics Today's Charles Day takes a look at how diesel engines work, and why it's clear it's not just a lone software engineer who came up with the cheat. "...[S]oftware is impotent without hardware. To recognize when a car was being tested and not driven, the defeat device required data from a range of sensors -- sensors that a noncheating car might not need.... Whereas it's conceivable that a single software engineer, directed by a single manager, could have secretly written and uploaded the code that ran the defeat device, installing its associated hardware would require a larger and more diverse team of conspirators," he says.

An anonymous reader writes: Some U.S. IT workers who have been replaced with H-1B contractors are alleging discrimination and are going to court. They are doing so in increasing numbers. There are at least seven IT workers at Disney who are pursuing, or plan to pursue, federal and state discrimination administrative complaints over their layoffs. Separately, there are ongoing court cases alleging discrimination against two of the largest India-based IT services firms, Infosys and Tata Consultancy Services. There may also be federal interest in examining the issue.

mattydread23 writes: This interview with GitHub CEO Chris Wanstrath and product VP Kakul Srivastava explains a little more what GitHub is planning for the future — and how the company is trying to live up to its $2 billion valuation. Basically, if every developer in the world uses and loves GitHub, the next logical step is to turn more people into developers. "Even today, Wanstrath says, there are journalists and scientists who are using GitHub to find, build, and share data-driven applications that assist with research or interactive projects. The goal, then, is to gradually make it a lot easier for anybody to get started on the platform. As more and more people get educated as programmers from an early age, Wanstrath wants GitHub to be the service of choice for the next generation to really get their feet wet."

An anonymous reader writes: When Oculus took to Kickstarter in 2012, the company sought to create the 'DK1', a development kit of the Rift which the company wanted to eventually become an affordable VR headset that they would eventually take to market as a consumer product. At the time, the company was aiming for a target price around $350, but since then the company, and the scope of the Rift headset, has grown considerably. That's one reason why Oculus Founder Palmer Luckey says that the consumer Rift headset, launching in Q1 2016, will cost more than $350. '...the reason for that is that we've added a lot of technology to this thing beyond what existed in the DK1 and DK2 days,' says Luckey.

dotancohen writes: The author of bioinformatics software Treefinder is revoking the license to his software for researchers working in eight European countries because he says those countries allow too many immigrants to cross their borders, effective 1 October. The author states, "Immigration to my country harms me, it harms my family, it harms my people. Whoever invites or welcomes immigrants to Europe and Germany is my enemy."

HughPickens.com writes: Tyler Cowen writes in MIT Technology Review that the improved measurement of worker performance through information technology is beginning to allow employers to measure value fairly precisely and as we get better at measuring who produces what, the pay gap between those who make more and those who make less grows. Insofar as workers type at a computer, everything they do is logged, recorded, and measured. Surveillance of workers continues to increase, and statistical analysis of large data sets makes it increasingly easy to evaluate individual productivity, even if the employer has a fairly noisy data set about what is going on in the workplace. Consider journalism. In the "good old days," no one knew how many people were reading an article, or an individual columnist. Today a digital media company knows exactly how many people are reading which articles for how long, and also whether they click through to other links. The result is that many journalists turn out to be not so valuable at all. Their wages fall or they lose their jobs, while the superstar journalists attract more Web traffic and become their own global brands.

According to Cowen, the upside is that measuring value tends to boost productivity, as has been the case since the very beginning of management science. We're simply able to do it much better now, and so employers can assign the most productive workers to the most suitable tasks. The downsides are several. Individuals don't in fact enjoy being evaluated all the time, especially when the results are not always stellar: for most people, one piece of negative feedback outweighs five pieces of positive feedback.

StewBeans writes: InfoWorld recently pointed out that the "architect" part of enterprise architect is a misnomer, because what they are building can't be a static, unmoving structure or it will fail. Businesses need to remain fluid and flexible as technology and consumer behaviors evolve, so modern enterprise architects must "develop frameworks with constant change as a first principle." The business value of these frameworks, however, is often called into question, and EAs have even been called the "Miltons" (as in Milton from Office Space) of the enterprise. If the field of enterprise architecture is changing to focus more on digital transformation, how does that compete with or compliment IT's role in the enterprise, which is also focused on digital transformation? The enterprise architect of BJ's Wholesale breaks down his responsibilities and addresses some myths about the EA role in this article.

New submitter DarkHorseman writes: I am looking into a new position with my employer and have the opportunity to work with the development and QA team to further the creation of a Quality Assurance Framework that will be used into the long-term future. This is software that has been in continuous development, in-house, for >10 years and is used company-wide (Fortune100, ~1000 locations, >10k users, different varieties based on discipline) as a repair toolset on a large variety of computers (high variability of SW/HW configuration). Now is the time to formalize the QA process. We have developed purpose-built tools and include vendor-specific applications based on business need. This framework will ideally provide a thorough and documentable means by which a team of testers could help to thoroughly ensure proper functionality before pushing the software to all locations. The information provided by Lynda.com along with other sources has been invaluable in understanding the software side of QA but I have seen very little in terms of actual creation of the framework of the process. What would you consider the best resources to prepare me to succeed? Even if your QA needs are for smaller projects, what advice do you have for formalizing the process?

An anonymous reader writes: Italo Vignoli, founding member of The Document Foundation, reflects on the project's five-year mark in an article on Opensource.com: "LibreOffice was launched as a fork of OpenOffice.org on September 28, 2010, by a tiny group of people representing the community in their capacity as community project leaders. At the time, forking the office suite was a brave -- and necessary -- decision, because the open source community did not expect OpenOffice.org to survive for long under Oracle stewardship." The project that was OpenOffice.org does still exist, in the form of Apache Open Office, but along with most Linux distros, I've switched completely to LibreOffice, after some initial misgivings.

joabj writes: Most software releases more or less follow the routine convention of Major.Minor.Bugfix numbering (i.e. Linux 4.2.1). This gives administrators an idea of what updates are major ones and might bring compatibility issues. As Dominic Tarr points out in his essay "Sentimental Versioning," a few projects boldly take on more whimsical schemes for versioning, such as Donald Knuth's use of successive Pi digits to enumerate new updates to TeX, or Node.js's punk-rock careening between major and minor releases. If you break convention, Tarr seems to be arguing, at least do so with panache.

theodp writes: Responding to New York City's much-ballyhooed $81 million initiative to require all of the city's public schools to offer CS to all students, Coding Horror's Jeff Atwood has penned a guest column for the NY Daily News which cautions that learning to code isn't all it's cracked up to be. Atwood begins, "Mayor de Blasio is winning widespread praise for his recent promise that, within 10 years, all of New York City's public schoolchildren will take computer science classes. But as a career programmer who founded two successful software startups, I am deeply skeptical about teaching all kids to code." Why? "If someone tells you 'coding is the new literacy' because 'computers are everywhere today,' ask them how fuel injection works. By teaching low-level coding, I worry that we are effectively teaching our children the art of automobile repair. A valuable skill — but if automobile manufacturers and engineers are doing their jobs correctly, one that shouldn't be much concern for average people, who happily use their cars as tools to get things done without ever needing to worry about rebuilding the transmission or even change the oil." Atwood adds, "There's nothing wrong with basic exposure to computer science. But it should not come at the expense of fundamental skills such as reading, writing and mathematics...I've known so many programmers who would have been much more successful in their careers if they had only been better writers, better critical thinkers, better back-of-the-envelope estimators, better communicators. And aside from success in careers, we have to ask the broader question: What kinds of people do we want children to grow up to be?"

An anonymous reader writes: More fuel was thrown on the Volkswagen fire today after two German newspapers reported that Volkswagen's own staff and one of its suppliers warned years ago about software designed to thwart emissions test. Volkswagen declined to comment on the details of either newspaper report. "There are serious investigations underway and the focus is now also on technical solutions" for customers and dealers, a Volkswagen spokesman said. "As soon as we have reliable facts we will be able to give answers."

pacopico writes: Gennady Korotkevich — aka Tourist — has spent a decade ruling the world of sport coding. He dominates TopCoder, Codeforces and just about every tournament sponsored by the likes of Google and Facebook. Bloomberg has profiled Korotkevich's rise through the sport coding ranks and taken a deep look at what makes this sport weirdly wonderful. The big takeaway from the piece seems to be that sport coding has emerged as a way for very young coders to make names for themselves and get top jobs — sometimes by skipping college altogether.

New submitter MikeTechDude writes: Estimates have always been an integral part of the software development process. In recent years, however, developers, including Woody Zuill and Vasco Duarte, have begun to question the efficacy, and even the purpose, of using estimates to predict a project's cost and time line. A fierce debate has sprung up on Twitter, between those calling for an end to estimates and those who continue to champion their use in a professional setting. On the surface, it would appear that the debate is black and white. Proponents of the #NoEstimates Twitter hashtag are promoting a hard stop to all estimates industry-wide, and critics of the movement are insisting on a conservative approach that leaves little room for innovation. However, the reality of the debate has unfolded in far more complex, nuanced shades of gray. HP's Malcolm Isaacs digs deep and pinpoints where the debate started, where it now stands, and what its implications are for the future of software development. Meanwhile, Martin Heller offers his less unbiased approach with his post, #NoEstimates? Not so fast.

Lucas123 writes: The method by which Volkswagen diesel cars were able to thwart emissions tests and spew up to 40X the nitrogen oxide levels set by the Environmental Protection Agency was relatively simple. It was more likely no more than a single line of code used to detect when an emissions test was being performed and place the emissions system in an alternate mode — something as simple as a software "on/off" switch. Volkswagen AG CEO Martin Winterkorn, who stepping down as the result of his company's scandal, has said he had no knowledge of the emissions cheat, but software dev/test audit trails are almost certain to pinpoint who embedded the code and who authorized it. You can actually see who asked the developer to write that code," said Nikhil Kaul, a product manager at test/dev software maker SmartBear Software. "Then if you go upstream you can see who that person's boss was...and see if testing happened...and, if testing didn't happen. So you can go from the bottom up to nail everyone."