Barence writes "Dropbox has kicked off its first developer conference with the stated goal of replacing the hard disk. 'We are replacing the hard drive,' said Dropbox CEO Drew Houston. 'I don't mean that you're going to unscrew your MacBook and find a Dropbox inside, but the spiritual successor to the hard drive is what we're launching.' The new Dropbox Platform includes tools for developers that will allow them to use Dropbox to sync app data between devices. The company's new APIs will also make it easier for app developers to include plugins that save to Dropbox, or choose files stored in the service for use within apps."
MrMetlHed writes "A portion of this Reuters article about the Pentagon's inability to manage paying soldiers properly mentions that their payroll program has 'seven million lines of Cobol code that hasn't been updated.' It goes on to mention that the documentation has been lost, and no one really knows how to update it well. In trying to replace the program, the Pentagon spent a billion dollars and wasn't successful."
cyclomedia writes "Over a number of years my company has managed to slowly shift from a free-for-all (pick a developer at random and get them to do what you want) to something resembling Agile development with weekly builds. But we still have to deal with constant incoming feature changes and requests that are expected to be included in this week's package. The upshot is that builds are usually late, not properly tested and developers get the flak when things go wrong. I suspect the answer is political, but how do we make things better? One idea I had was that every time a new request comes in — no matter how small — the build gets pushed back by 24 or even 48 hours. I'd love to hear your ideas or success stories. (Unfortunately, quitting is not an option)"
dcblogs writes "There are about 18.2 million software developers worldwide, a number that is due to rise to 26.4 million by 2019, a 45% increase, says Evans Data Corp. in its latest Global Developer Population and Demographic Study. Today, the U.S. leads the world in software developers, with about 3.6 million. India has about 2.75 million. But by 2018, India will have 5.2 million developers, a nearly 90% increase, versus 4.5 million in the U.S., a 25% increase though that period, Evans Data projects. India's software development growth rate is attributed, in part, to its population size, 1.2 billion, and relative youth, with about half the population under 25 years of age. Rapid economic growth is fueling interest in development. India's services firms hire, in many cases, thousands of new employees each quarter. Consequently, IT and software work is seen as clear path to the middle class for many of the nation's young. For instance, in one quarter this year, Tata Consultancy Services added more than 17,000 employees, gross, bringing its total headcount to 263,600. In the same quarter of 2010, the company had about 150,000 workers."
itwbennett writes "U.C. Berkeley researchers have determined that crowdsourcing bug-finding is a far better investment than hiring employees to do the job. Here's the math: Over the last three years, Google has paid $580,000 and Mozilla has paid $570,000 for bugs found in their Chrome and Firefox browsers — and hundreds of vulnerabilities have been fixed. Compare that to the average annual cost of a single North American developer (about $100,000, plus 50% overhead), 'we see that the cost of either of these VRPs (vulnerability reward programs) is comparable to the cost of just one member of the browser security team,' the researchers wrote (PDF). And the crowdsourcing also uncovered more bugs than a single full-time developer could find."
theshowmecanuck writes "I'm working at a small- to medium-sized company that creates software for mobile devices, but came from a 'large enterprise' world before. I see node.js being used increasingly in smaller companies (including ours) or in web/mobile related software. Meanwhile we see languages like Java/JEE, C/C++, and .NET continue to be used for medium-to-large enterprise corporate software. Compared to the status quo in the enterprise (JEE/C/C++/.NET ... and yes, maybe even COBOL) maybe Slashdotters can chime in on how they see Node.js in this role. I'm thinking of things like complexity of business logic (dependencies, workflows, linear processes, etc), transaction support (for processes in general and database support), messaging services, etc. Also, what is the state of Node.js in terms of paradigms like application containers, where much of the 'plumbing' is already set up for you (one of the main benefits of JEE application containers)? But there is also the question of maintainability, deployment, and ongoing operations. What say you, Slashdot?"