By Developers, For Developers
| PDF Pg | Paper Pg | Type | Description | Fixed on | Comments |
|---|---|---|---|---|---|
| 7 | TYPO | “…and how way coding to music affects your problem-solving abilities” should be “…and how the way coding to music affects your problem-solving abilities” or “…and how coding to music affects your problem-solving abilities”. Probably cleaner as the latter. | 2014-12-17 | ||
| 19 | TYPO | “In addition, all large-scale codebases have code that no one knows well or feel responsible for.” should be “In addition, all large-scale codebases have code that no one knows well or feels responsible for.” | 2014-12-17 | ||
| 34 | TYPO | “The revisions analysis results in two columns: an enity column”. Misspelled “entity”. | 2014-12-17 | ||
| 75 | TYPO | missing space: “On larger projects youcan’t see the” | 2014-12-17 | ||
| 96 | TYPO | “automatate the mundane tasks” : probably “automate” | 2014-12-17 | ||
| 115 | TYPO | “three parsers: svn, hq and git”. Mercurial reference should be “hg”. | 2014-12-17 | ||
| 57 | TYPO | In “consider wether the hotspot code is deteriorating”, | 2014-12-30 | ||
| 41 | TYPO | “In the above figure, you’re can see both the good and the fragile parts of the codebase.” should be “In the above figure, you can see both the good and the fragile parts of the codebase.” The you’re should be you. | 2014-12-30 | ||
| 330 | TYPO | “patrolling a the entire city.” ‘A’ aricle is not needed. (Kindle version shows only loc, not page number) | 2015-01-01 | ||
| 142 | TYPO | “I replayed version control dta” dta => data | 2015-01-12 | ||
| 0 | TYPO | Footnote 7 (MetricsTreeMap link) contains a couple of typos so the URL does not link anywhere | 2015-01-12 | ||
| viii | TYPO | “Forward” should probably be “Foreword” This is also on the next page in Acknowledgements, fourth paragraph from the bottom. | 2015-02-04 | ||
| 1 | DEFER | On the Kindle version of the book, the diagrams are very low quality, making it quite hard in many to read or see what is in the diagrams. This is especially true of the visualisations. | 2015-06-05 | ||
| 95 | TYPO | “Let’s dive in and see what’s hidden secrets we can cover in our architecture” should read “Let’s dive in and see what hidden secrets we can uncover in our architecture” | 2015-02-25 | ||
| 96 | TYPO | “We developer now risk breaking each other changes” should read “We developers now risk breaking each other’s changes” | 2015-02-25 | ||
| 97 | TYPO | “Once we’ve located that architectural boundaries we need to tell Code Maat about them.” should read “Once we’ve located those architectural boundaries we need to tell Code Maat about them.” | 2015-02-25 | ||
| 104 | TYPO | “perform the analysis more frequent” should read “perform the analysis more frequently” | 2015-02-25 | ||
| 105 | TYPO | “Let’s look at some trends to se what they tell us.” should read “Let’s look at some trends to see what they tell us.” | 2015-02-25 | ||
| 106 | TYPO | “Skilled human testers will find different kinds of bugs compared to automated tests will find.” should read “Skilled human testers will find different kinds of bugs compared to automated tests.” | 2015-02-25 | ||
| 77 | TYPO | Edit needed for “could recommended” on p.77, which states: | 2015-03-04 | ||
| 30 | ERROR | The merge_comp_freqs.py script does not correctly merge data in Windows. In Windows the output of cloc uses back slashes ‘\\’ instead of forward slashes ‘/’ as a file separator in the file names. The output from maat uses forward slashes. As a result the only file that is found in common is project.clj because the leading ‘./’ or ‘.\\’ is stripped from the name in the cloc output. All of the other file names are not equal because of the file separator. Adding a call to replace when retrieving the name will fix this problem. So name = row[0] should be name = row[0].replace(“\\\\”, “/”) inside of parse_freqs and name = row[1][2:] should be name = row[1][2:].replace(“\\\\”, “/”) inside of parse_complexity. This will ensure that all file separators in the name are consistent and will therefore match the key upon look up within the dict. | 2015-06-20 | This is solved by adding the --unix argument to all invocations of cloc in the book. | |
| 26 | 26 | TYPO | When saving the detailed boundaries file the text should read “Open a text editor, enter the following mapping, and save it as maat_src_detailed_test_boundaries.txt…” instead of “maat_src_test_boundaries.txt” from the previous paragraphs. | 2015-06-20 | |
| 125 | 125 | TYPO | “If we hear the same option repeatedly, we come to think of that opinion as…” should not have “option” but should be “opinion” | 2015-06-20 | |
| 24 | TYPO | For Windows git version 1.9.5.msysgit.0 | 2015-06-20 | The git commands on Windows shall be run in the Git Bash Shell as stated in the Introduction; It won't work properly otherwise. | |
| 26 | ERROR | Windows git version 1.9.5.msysgit.0 As suggested in error, command | 2015-06-20 | The git commands on Windows shall be run in the Git Bash Shell as stated in the Introduction; It won't work properly otherwise. | |
| 169 | TYPO | In my printed copy there is twice the same heading used on the pages 169 and 170 (“Link Code Churn to Temporal Coupling”). I guess that either there should be two distinct headings or that you simply remove the second occurence. | |||
| 80 | ERROR | The link (http_www.inf.usi.ch/phd/dambros/tools/evoradar.php) for Evolution Radar no longer works. Perhaps http_reveal.inf.usi.ch/web/dambros/tools/evoradar.php is the updated link? | |||
| 113 | ERROR | The code for nopcommerce has moved to https_github.com/nopSolutions/nopCommerce. Updated git clone command: git clone https_github.com/nopSolutions/nopCommerce.git (Replace _ with ://) | |||
| 114 | ERROR | If I try to run the analysis of nopCommerce as suggested, I got errors because of ^M characters in git log:
There are two ^M characters in log - on lines 667 and 1795. These have to be removed before analysis can succeed | |||
| 89 | TYPO | On the fifth paragraph on the page is a line that references “Figure , , on page 88”. The figure on the opposite page (88) also has no label. (The P1.0 PDF does not have this issue.) | |||
| 70 | TYPO | Second paragraph: | |||
| 109 | 111 | TYPO | In the fourth paragraph there is a typo on the word quotation: (qoutation from Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing [BHS07]). | ||
| 110 | ERROR | If followed the steps outlined in chapter »Merge Complexity and Effort« starting on page 109 but merge_comp_freqs.py does only produce a line with a header when invoked on my Mac with OSX 10.13.4 with Python 2.7.10 and CLOC 1.76: module,revisions,code Both files contain data according to the book from own projects: MacBook-Pro-II:Projekte ms1$ cat scgkpimon_lines.csv |