By Robin Carnahan, Randy Hart, and Waldo Jaquith. Only 13% of large government software projects are successful.1 State IT projects, in particular, are often challenged because states lack basic knowledge about modern software development, relying on outdated procurement processes. Every year, the federal government matches billions of dollars in funding to state and local governments to maintain and modernize IT systems used to implement federal programs such as Medicaid, child welfare benefits, housing, and unemployment insurance. Efforts to modernize those legacy systems fail at an alarmingly high rate and at great cost to the federal budget. […] This handbook is designed for executives, budget specialists, legislators, and other "non-technical" decision-makers who fund or oversee state government technology projects that receive federal funding and implement the necessary technology to support federal programs. It can help you set these projects up for success by asking the right questions, identifying the right outcomes, and equally important, empowering you with a basic knowledge of the fundamental principles of modern software design.

Hackathons can spur creativity, can inspire a concerted amount of development effort on a focused project for a short period of time, and can increase attention to a critical issue. For people who feel disaffected and hopeless, a hackathon can rekindle a sense of creativity and possibility. But the tangible products of a hackathon (hardware, software) are rarely of adequate quality for real-world use.

Plain and simple: software patents don't work because there's too much software and not enough people who know about it.

On the price of software.