Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Instant streaming of thousands of movies and TV episodes with Prime Video
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
$34.31$34.31
FREE delivery: Friday, Dec 15 on orders over $35.00 shipped by Amazon.
Ships from
Amazon.com
Sold by
Amazon.com
Returns
Returnable until Jan 31, 2024
Payment
Secure transaction
Buy used: $29.99
Other Sellers on Amazon
+ $3.99 shipping
91% positive over last 12 months
& FREE Shipping
81% positive over last 12 months
& FREE Shipping
92% positive over last 12 months
Usually ships within 4 to 5 days.
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Software Design X-Rays: Fix Technical Debt with Behavioral Code Analysis 1st Edition
| Price | New from | Used from |
- Kindle
$28.99 Read with our free app - Paperback
$29.99 - $34.3111 Used from $21.84 28 New from $30.31
Purchase options and add-ons
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.- ISBN-101680502727
- ISBN-13978-1680502725
- Edition1st
- PublisherPragmatic Bookshelf
- Publication date
2018
April 17
- Language
EN
English
- Dimensions
7.5 x 0.6 x 9.3
inches
- Length
276
Pages
Frequently bought together

Customers who viewed this item also viewed
From the brand
-
The Pragmatic Programmers publishes hands-on, practical books on classic and cutting-edge software development and engineering management topics. We help professionals solve real-world problems, hone their skills, and advance their careers.
-
Editorial Reviews
About the Author
Product details
- Publisher : Pragmatic Bookshelf; 1st edition (April 17, 2018)
- Language : English
- Paperback : 276 pages
- ISBN-10 : 1680502727
- ISBN-13 : 978-1680502725
- Item Weight : 1.14 pounds
- Dimensions : 7.5 x 0.58 x 9.25 inches
- Best Sellers Rank: #944,437 in Books (See Top 100 in Books)
- Customer Reviews:
Important information
To report an issue with this product, click here.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonTop reviews from other countries
On part pourtant d'un constat de base simple : le fonctionnement de Git (ou autre SCV peu importe) fait que vous avez à votre disposition tout l'historique du projet, d'où la question "que peut-on tirer de cette mine d'informations ?" Et bien énormément, ce que l'auteur nous démontre au fil du livre, en se basant sur l'analyse de véritables projets open-source.
Quand on parle de dette technique, ce qui limite l'utilité de la métaphore, c'est qu'on se heurte vite au problème du manque de données. Ce qui fait de ce livre de loin le meilleur que j'ai lu sur ce sujet, c'est qu'il est le plus concret : aborder une codebase inconnue, trouver les problèmes, les prioriser, les rendre tangibles pour les stakeholders, complèter les outils d'analyse statique qui ne peuvent pas prendre en compte l'aspect "legacy" et vous annonce des 40ans/homme de problèmes à résoudre, diagnostiquer les problèmes de bottlenecks entre équipes, etc.
Le tout basé non pas sur des approximations ou des impressions mais des données concrètes et vérifiables.
Anecdote: j'ai pu trouver un bug dans du code inconnu d'une autre équipe juste grâce à l'analyse coupling/duplication.
Bref change complètement la donne quand on parle de dette technique, à recommander à tout professionnel.
À noter que le code utilisé dans le livre est sur Github donc on peut aussi jouer avec.
I find really hard day-to-day is to justify refactoring to managers or non-technical decision-makers. It is often seen as a nice to have, and I always had difficulty communicating about it. The insights I found in this book help me better communicate where the complexity lies, and where more design is necessary, as well where it is not, as often the biggest downside of mentioning refactoring is it can take too long without immediate benefits. Now I don't find it necessary everywhere and I can better prioritize slices of where features get stuck and reduce maintenance difficulties at the same time.
This book also helped me look at how a function or class grows over time in order to mine the assumptions hidden behind why it is like that and how to change it further. It helped with my mental model of how to navigate my implementations day to day too.




