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.

A long lost library. A priceless manuscript. A deadly secret... About to depart on his first vacation in years, Edward Wozny, a young hot-shot banker, is sent to help one of his firm's most important and mysterious clients. When asked to unpack and organise a personal library of rare books, Edward's indignation turns to intrigue as he realises that among the volumes there may be hidden a unique medieval codex, a treasure kept sealed away for many years and for many reasons. Edward's intrigue becomes an obsession that only deepens as friends draw him into a peculiar and addictive computer game, as mystifying parallels between the game's virtual reality and the legend of the codex emerge and the lines between reality, fantasy and mysterious legend start to blur ...

Code X brings together a selection of personal histories of the current `transforming' and `expanding' of the book medium with the aim to challenge the very notion of what it could be(come) in today's complex information era. The design of Code--X within codex form represents a playful and daring twist of ink imitating pixel to render composition and design. The content is seen as a continuous scroll, cropped where screen meets paper edge. We celebrate both camps by highlighting dichotomies of edge to scroll, sequence to time and image to place.

Jack the Ripper and legacy codebases have more in common than you'd think. Inspired by forensic psychology methods, you'll learn strategies to predict the future of your codebase, assess refactoring direction, and understand how your team influences the design. With its unique blend of forensic psychology and code analysis, this book arms you with the strategies you need, no matter what programming language you use. Software is a living entity that's constantly changing. To understand software systems, we need to know where they came from and how they evolved. By mining commit data and analyzing the history of your code, you can start fixes ahead of time to eliminate broken designs, maintenance issues, and team productivity bottlenecks. In this book, you'll learn forensic psychology techniques to successfully maintain your software. You'll create a geographic profile from your commit data to find hotspots, and apply temporal coupling concepts to uncover hidden relationships between unrelated areas in your code. You'll also measure the effectiveness of your code improvements. You'll learn how to apply these techniques on projects both large and small. For small projects, you'll get new insights into your design and how well the code fits your ideas. For large projects, you'll identify the good and the fragile parts. Large-scale development is also a social activity, and the team's dynamics influence code quality. That's why this book shows you how to uncover social biases when analyzing the evolution of your system. You'll use commit messages as eyewitness accounts to what is really happening in your code. Finally, you'll put it all together by tracking organizational problems in the code and finding out how to fix them. Come join the hunt for better code! What You Need: You need Java 6 and Python 2.7 to run the accompanying analysis tools. You also need Git to follow along with the examples.

Mark Sutherland's Code X transforms your computer into a sound poetry organ, whether you like it or not.

Peter Eisenman's competition-winning project for the City of Culture of Galicia in Santiago de Compostela, Spain, is a formidable battery of museums, libraries, and auditoriums, a cultural acropolis atop a spectacular hillside site in northeastern Spain. By excavating the hilltop and arranging six buildings as a kind of artificial topography, Eisenman creates a new warped landscape that seems to merge building and ground, that occupies the hilltop without seeming to have been built upon it. In CODEX, the New York-based Eisenman, known for a career of formal investigations, reveals in essays and illustrations his theory of coding as a device for producing form. Through more than three hundred line drawings and perspectives, the development of the code--and the buildings and landscape it informs--becomes apparent, culminating in a giant earthwork as excavation of the site begins.

The author demonstrates that the Book of Mormon is a native Mesoamerican book (or codex) that exhibits what one would expect of a historical document produced in the context of ancient Mesoamerican civilization. He also shows that scholars' discoveries about Mesoamerica and the contents of the Nephite record are clearly related, listing more than 400 points where the Book of Mormon text corresponds to characteristic Mesoamerican situations, statements, allusions, and history.