The Technical Fix

Nanotechnology! Genetic engineering! Miracle Drugs! We are promised that new technological developments will magically save us from the dire consequences of the 300-year fossil-fueled binge known as modern industrial civilization, without demanding any fundamental changes in our behavior. There is a pervasive belief that technological innovation will enable us to continue our current lifestyle indefinitely and will prevent social, economic and environmental collapse. Techno-Fix shows that negative unintended consequences of technology are inherently predictable and unavoidable, techno-optimism is completely unjustified, and modern technology, in the presence of continued economic growth, does not promote sustainability, but hastens collapse. The authors demonstrate that most technological solutions to social and technology-created problems are ineffective. They explore the reasons for the uncritical acceptance of new technologies, show who really controls the direction of technological change, and then advocate extensive reform. This comprehensive exposé is a powerful argument for why we can and should put the genie back in the bottle. An insightful and powerful critique, it is required reading for anyone who is concerned about blind techno-optimism and believes that the time has come to make science and technology more socially and environmentally responsible. For more information, please visit technofix.org .

The term "technological fix" should mean a fix provided by technology--a solution for all of our problems, from medicine and food production to the environment and business. Instead, technological fix has come to mean a cheap, quick fix using inappropriate technology that usually creates more problems than it solves. This collection sets out the distinction between a technological fix and a true technological solution. Bringing together scholars from a variety of disciplines, the essays trace the technological fix as it has appeared throughout the twentieth century. Addressing such "fixes" as artificial hearts, industrial agriculture and climate engineering, these essays examine our need to turn to technology for solutions to all of our problems.

The practical implications of technical debt for the entire software lifecycle; with examples and case studies. Technical debt in software is incurred when developers take shortcuts and make ill-advised technical decisions in the initial phases of a project, only to be confronted with the need for costly and labor-intensive workarounds later. This book offers advice on how to avoid technical debt, how to locate its sources, and how to remove it. It focuses on the practical implications of technical debt for the entire software life cycle, with examples and case studies from companies that range from Boeing to Twitter. Technical debt is normal; it is part of most iterative development processes. But if debt is ignored, over time it may become unmanageably complex, requiring developers to spend all of their effort fixing bugs, with no time to add new features--and after all, new features are what customers really value. The authors explain how to monitor technical debt, how to measure it, and how and when to pay it down. Broadening the conventional definition of technical debt, they cover requirements debt, implementation debt, testing debt, architecture debt, documentation debt, deployment debt, and social debt. They intersperse technical discussions with "Voice of the Practitioner" sidebars that detail real-world experiences with a variety of technical debt issues.

A New York Times Notable Book of the Year In the very near future, "smart" technologies and "big data" will allow us to make large-scale and sophisticated interventions in politics, culture, and everyday life. Technology will allow us to solve problems in highly original ways and create new incentives to get more people to do the right thing. But how will such "solutionism" affect our society, once deeply political, moral, and irresolvable dilemmas are recast as uncontroversial and easily manageable matters of technological efficiency? What if some such problems are simply vices in disguise? What if some friction in communication is productive and some hypocrisy in politics necessary? The temptation of the digital age is to fix everything -- from crime to corruption to pollution to obesity -- by digitally quantifying, tracking, or gamifying behavior. But when we change the motivations for our moral, ethical, and civic behavior we may also change the very nature of that behavior. Technology, Evgeny Morozov proposes, can be a force for improvement -- but only if we keep solutionism in check and learn to appreciate the imperfections of liberal democracy. Some of those imperfections are not accidental but by design. Arguing that we badly need a new, post-Internet way to debate the moral consequences of digital technologies, To Save Everything, Click Here warns against a world of seamless efficiency, where everyone is forced to wear Silicon Valley's digital straitjacket.

The authors challenge the "computer literacy" programmes devised by the government and directed at education in a bid to equip the young and rescue the economy from recession. They explore the relationship that has developed between education, industry and technology.

Are you working on a codebase where cost overruns, death marches, and heroic fights with legacy code monsters are the norm? Battle these adversaries with novel ways to identify and prioritize technical debt, based on behavioral data from how developers work with code. And that's just for starters. Because good code involves social design, as well as technical design, you can find surprising dependencies between people and code to resolve coordination bottlenecks among teams. Best of all, the techniques build on behavioral data that you already have: your version-control system. Join the fight for better code! Use statistics and data science to uncover both problematic code and the behavioral patterns of the developers who build your software. This combination gives you insights you can't get from the code alone. Use these insights to prioritize refactoring needs, measure their effect, find implicit dependencies between different modules, and automatically create knowledge maps of your system based on actual code contributions. In a radical, much-needed change from common practice, guide organizational decisions with objective data by measuring how well your development teams align with the software architecture. Discover a comprehensive set of practical analysis techniques based on version-control data, where each point is illustrated with a case study from a real-world codebase. Because the techniques are language neutral, you can apply them to your own code no matter what programming language you use. Guide organizational decisions with objective data by measuring how well your development teams align with the software architecture. Apply research findings from social psychology to software development, ensuring you get the tools you need to coach your organization towards better code. If you're an experienced programmer, software architect, or technical manager, you'll get a new perspective that will change how you work with code. What You Need: You don't have to install anything to follow along in the book. TThe case studies in the book use well-known open source projects hosted on GitHub. You'll use CodeScene, a free software analysis tool for open source projects, for the case studies. We also discuss alternative tooling options where they exist.