Your code as a crime scene: use forensic techniques to arrest defects, bottlenecks, and bad design in your programs
Jack the Ripper and legacy codebases have more in common than you'd think. Inspired by forensic psychology methods, you can apply strategies to identify problems in your existing code, assess refactoring direction, and understand how your team influences the software architecture. With its uniq...
Saved in:
| Main Author: | |
|---|---|
| Other Authors: | , |
| Format: | Electronic eBook |
| Language: | English |
| Published: |
[Place of publication not identified]
Pragmatic Bookshelf
[2024]
|
| Edition: | Second edition. |
| Series: | The pragmatic programmers
|
| Subjects: | |
| Links: | https://learning.oreilly.com/library/view/-/9798888650837/?ar |
| Summary: | Jack the Ripper and legacy codebases have more in common than you'd think. Inspired by forensic psychology methods, you can apply strategies to identify problems in your existing code, assess refactoring direction, and understand how your team influences the software architecture. With its unique blend of criminal psychology and code analysis, Your Code as a Crime Scene arms you with the techniques you need to take on any codebase, no matter what programming language you use. Software development might well be the most challenging task humanity ever attempted. As systems scale up, they also become increasingly complex, expensive to maintain, and difficult to reason about. We can always write more tests, try to refactor, and even fire up a debugger to understand complex coding constructs. That's a great starting point, but you can do so much better. Take inspiration from forensic psychology techniques to understand and improve existing code. Visualize codebases via a geographic profile from commit data to find development hotspots, prioritize technical debt, and uncover hidden dependencies. Get data and develop strategies to make the business case for larger refactorings. Detect and fix organizational problems from the vantage point of the software architecture to remove bottlenecks for the teams. The original Your Code as a Crime Scene from 2014 pioneered techniques for understanding the intersection of people and code. This new edition reflects a decade of additional experience from hundreds of projects. Updated techniques, novel case studies, and extensive new material adds to the strengths of this cult classic. |
| Item Description: | Includes bibliographical references |
| Physical Description: | 1 Online-Ressource (336 Seiten) Illustrationen |
Staff View
MARC
| LEADER | 00000nam a22000002c 4500 | ||
|---|---|---|---|
| 001 | ZDB-30-ORH-104373296 | ||
| 003 | DE-627-1 | ||
| 005 | 20240701091205.0 | ||
| 007 | cr uuu---uuuuu | ||
| 008 | 240701s2024 xx |||||o 00| ||eng c | ||
| 035 | |a (DE-627-1)104373296 | ||
| 035 | |a (DE-599)KEP104373296 | ||
| 035 | |a (ORHE)9798888650837 | ||
| 035 | |a (DE-627-1)104373296 | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rda | ||
| 041 | |a eng | ||
| 082 | 0 | |a 005.1068/5 |2 23/eng/20240617 | |
| 100 | 1 | |a Tornhill, Adam |e VerfasserIn |4 aut | |
| 245 | 1 | 0 | |a Your code as a crime scene |b use forensic techniques to arrest defects, bottlenecks, and bad design in your programs |c by Adam Tornhill ; foreword by Kevlin Henney ; edited by Kelly Talbot |
| 246 | 3 | 3 | |a Use forensic techniques to arrest defects, bottlenecks, and bad design in your programs |
| 250 | |a Second edition. | ||
| 264 | 1 | |a [Place of publication not identified] |b Pragmatic Bookshelf |c [2024] | |
| 300 | |a 1 Online-Ressource (336 Seiten) |b Illustrationen | ||
| 336 | |a Text |b txt |2 rdacontent | ||
| 337 | |a Computermedien |b c |2 rdamedia | ||
| 338 | |a Online-Ressource |b cr |2 rdacarrier | ||
| 490 | 0 | |a The pragmatic programmers | |
| 500 | |a Includes bibliographical references | ||
| 520 | |a Jack the Ripper and legacy codebases have more in common than you'd think. Inspired by forensic psychology methods, you can apply strategies to identify problems in your existing code, assess refactoring direction, and understand how your team influences the software architecture. With its unique blend of criminal psychology and code analysis, Your Code as a Crime Scene arms you with the techniques you need to take on any codebase, no matter what programming language you use. Software development might well be the most challenging task humanity ever attempted. As systems scale up, they also become increasingly complex, expensive to maintain, and difficult to reason about. We can always write more tests, try to refactor, and even fire up a debugger to understand complex coding constructs. That's a great starting point, but you can do so much better. Take inspiration from forensic psychology techniques to understand and improve existing code. Visualize codebases via a geographic profile from commit data to find development hotspots, prioritize technical debt, and uncover hidden dependencies. Get data and develop strategies to make the business case for larger refactorings. Detect and fix organizational problems from the vantage point of the software architecture to remove bottlenecks for the teams. The original Your Code as a Crime Scene from 2014 pioneered techniques for understanding the intersection of people and code. This new edition reflects a decade of additional experience from hundreds of projects. Updated techniques, novel case studies, and extensive new material adds to the strengths of this cult classic. | ||
| 650 | 0 | |a Computer software |x Quality control | |
| 650 | 0 | |a Computer programming |x Management | |
| 650 | 0 | |a Computer architecture | |
| 650 | 0 | |a Forensic sciences | |
| 650 | 4 | |a Logiciels ; Qualité ; Contrôle | |
| 650 | 4 | |a Ordinateurs ; Architecture | |
| 650 | 4 | |a Criminalistique | |
| 650 | 4 | |a forensic science | |
| 700 | 1 | |a Henney, Kevlin |e MitwirkendeR |4 ctb | |
| 700 | 1 | |a Talbot, Kelly |e HerausgeberIn |4 edt | |
| 966 | 4 | 0 | |l DE-91 |p ZDB-30-ORH |q TUM_PDA_ORH |u https://learning.oreilly.com/library/view/-/9798888650837/?ar |m X:ORHE |x Aggregator |z lizenzpflichtig |3 Volltext |
| 912 | |a ZDB-30-ORH | ||
| 951 | |a BO | ||
| 912 | |a ZDB-30-ORH | ||
| 049 | |a DE-91 | ||
Record in the Search Index
| DE-BY-TUM_katkey | ZDB-30-ORH-104373296 |
|---|---|
| _version_ | 1831287144359919616 |
| adam_text | |
| any_adam_object | |
| author | Tornhill, Adam |
| author2 | Henney, Kevlin Talbot, Kelly |
| author2_role | ctb edt |
| author2_variant | k h kh k t kt |
| author_facet | Tornhill, Adam Henney, Kevlin Talbot, Kelly |
| author_role | aut |
| author_sort | Tornhill, Adam |
| author_variant | a t at |
| building | Verbundindex |
| bvnumber | localTUM |
| collection | ZDB-30-ORH |
| ctrlnum | (DE-627-1)104373296 (DE-599)KEP104373296 (ORHE)9798888650837 |
| dewey-full | 005.1068/5 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1068/5 |
| dewey-search | 005.1068/5 |
| dewey-sort | 15.1068 15 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| edition | Second edition. |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>03438nam a22004692c 4500</leader><controlfield tag="001">ZDB-30-ORH-104373296</controlfield><controlfield tag="003">DE-627-1</controlfield><controlfield tag="005">20240701091205.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">240701s2024 xx |||||o 00| ||eng c</controlfield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)104373296</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)KEP104373296</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(ORHE)9798888650837</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627-1)104373296</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rda</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">005.1068/5</subfield><subfield code="2">23/eng/20240617</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Tornhill, Adam</subfield><subfield code="e">VerfasserIn</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Your code as a crime scene</subfield><subfield code="b">use forensic techniques to arrest defects, bottlenecks, and bad design in your programs</subfield><subfield code="c">by Adam Tornhill ; foreword by Kevlin Henney ; edited by Kelly Talbot</subfield></datafield><datafield tag="246" ind1="3" ind2="3"><subfield code="a">Use forensic techniques to arrest defects, bottlenecks, and bad design in your programs</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">Second edition.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">[Place of publication not identified]</subfield><subfield code="b">Pragmatic Bookshelf</subfield><subfield code="c">[2024]</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (336 Seiten)</subfield><subfield code="b">Illustrationen</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="0" ind2=" "><subfield code="a">The pragmatic programmers</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Includes bibliographical references</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Jack the Ripper and legacy codebases have more in common than you'd think. Inspired by forensic psychology methods, you can apply strategies to identify problems in your existing code, assess refactoring direction, and understand how your team influences the software architecture. With its unique blend of criminal psychology and code analysis, Your Code as a Crime Scene arms you with the techniques you need to take on any codebase, no matter what programming language you use. Software development might well be the most challenging task humanity ever attempted. As systems scale up, they also become increasingly complex, expensive to maintain, and difficult to reason about. We can always write more tests, try to refactor, and even fire up a debugger to understand complex coding constructs. That's a great starting point, but you can do so much better. Take inspiration from forensic psychology techniques to understand and improve existing code. Visualize codebases via a geographic profile from commit data to find development hotspots, prioritize technical debt, and uncover hidden dependencies. Get data and develop strategies to make the business case for larger refactorings. Detect and fix organizational problems from the vantage point of the software architecture to remove bottlenecks for the teams. The original Your Code as a Crime Scene from 2014 pioneered techniques for understanding the intersection of people and code. This new edition reflects a decade of additional experience from hundreds of projects. Updated techniques, novel case studies, and extensive new material adds to the strengths of this cult classic.</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Computer software</subfield><subfield code="x">Quality control</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Computer programming</subfield><subfield code="x">Management</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Computer architecture</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Forensic sciences</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Logiciels ; Qualité ; Contrôle</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Ordinateurs ; Architecture</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Criminalistique</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">forensic science</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Henney, Kevlin</subfield><subfield code="e">MitwirkendeR</subfield><subfield code="4">ctb</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Talbot, Kelly</subfield><subfield code="e">HerausgeberIn</subfield><subfield code="4">edt</subfield></datafield><datafield tag="966" ind1="4" ind2="0"><subfield code="l">DE-91</subfield><subfield code="p">ZDB-30-ORH</subfield><subfield code="q">TUM_PDA_ORH</subfield><subfield code="u">https://learning.oreilly.com/library/view/-/9798888650837/?ar</subfield><subfield code="m">X:ORHE</subfield><subfield code="x">Aggregator</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">BO</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-30-ORH</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91</subfield></datafield></record></collection> |
| id | ZDB-30-ORH-104373296 |
| illustrated | Not Illustrated |
| indexdate | 2025-05-05T13:25:15Z |
| institution | BVB |
| language | English |
| open_access_boolean | |
| owner | DE-91 DE-BY-TUM |
| owner_facet | DE-91 DE-BY-TUM |
| physical | 1 Online-Ressource (336 Seiten) Illustrationen |
| psigel | ZDB-30-ORH TUM_PDA_ORH ZDB-30-ORH |
| publishDate | 2024 |
| publishDateSearch | 2024 |
| publishDateSort | 2024 |
| publisher | Pragmatic Bookshelf |
| record_format | marc |
| series2 | The pragmatic programmers |
| spelling | Tornhill, Adam VerfasserIn aut Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs by Adam Tornhill ; foreword by Kevlin Henney ; edited by Kelly Talbot Use forensic techniques to arrest defects, bottlenecks, and bad design in your programs Second edition. [Place of publication not identified] Pragmatic Bookshelf [2024] 1 Online-Ressource (336 Seiten) Illustrationen Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier The pragmatic programmers Includes bibliographical references Jack the Ripper and legacy codebases have more in common than you'd think. Inspired by forensic psychology methods, you can apply strategies to identify problems in your existing code, assess refactoring direction, and understand how your team influences the software architecture. With its unique blend of criminal psychology and code analysis, Your Code as a Crime Scene arms you with the techniques you need to take on any codebase, no matter what programming language you use. Software development might well be the most challenging task humanity ever attempted. As systems scale up, they also become increasingly complex, expensive to maintain, and difficult to reason about. We can always write more tests, try to refactor, and even fire up a debugger to understand complex coding constructs. That's a great starting point, but you can do so much better. Take inspiration from forensic psychology techniques to understand and improve existing code. Visualize codebases via a geographic profile from commit data to find development hotspots, prioritize technical debt, and uncover hidden dependencies. Get data and develop strategies to make the business case for larger refactorings. Detect and fix organizational problems from the vantage point of the software architecture to remove bottlenecks for the teams. The original Your Code as a Crime Scene from 2014 pioneered techniques for understanding the intersection of people and code. This new edition reflects a decade of additional experience from hundreds of projects. Updated techniques, novel case studies, and extensive new material adds to the strengths of this cult classic. Computer software Quality control Computer programming Management Computer architecture Forensic sciences Logiciels ; Qualité ; Contrôle Ordinateurs ; Architecture Criminalistique forensic science Henney, Kevlin MitwirkendeR ctb Talbot, Kelly HerausgeberIn edt |
| spellingShingle | Tornhill, Adam Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs Computer software Quality control Computer programming Management Computer architecture Forensic sciences Logiciels ; Qualité ; Contrôle Ordinateurs ; Architecture Criminalistique forensic science |
| title | Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs |
| title_alt | Use forensic techniques to arrest defects, bottlenecks, and bad design in your programs |
| title_auth | Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs |
| title_exact_search | Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs |
| title_full | Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs by Adam Tornhill ; foreword by Kevlin Henney ; edited by Kelly Talbot |
| title_fullStr | Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs by Adam Tornhill ; foreword by Kevlin Henney ; edited by Kelly Talbot |
| title_full_unstemmed | Your code as a crime scene use forensic techniques to arrest defects, bottlenecks, and bad design in your programs by Adam Tornhill ; foreword by Kevlin Henney ; edited by Kelly Talbot |
| title_short | Your code as a crime scene |
| title_sort | your code as a crime scene use forensic techniques to arrest defects bottlenecks and bad design in your programs |
| title_sub | use forensic techniques to arrest defects, bottlenecks, and bad design in your programs |
| topic | Computer software Quality control Computer programming Management Computer architecture Forensic sciences Logiciels ; Qualité ; Contrôle Ordinateurs ; Architecture Criminalistique forensic science |
| topic_facet | Computer software Quality control Computer programming Management Computer architecture Forensic sciences Logiciels ; Qualité ; Contrôle Ordinateurs ; Architecture Criminalistique forensic science |
| work_keys_str_mv | AT tornhilladam yourcodeasacrimesceneuseforensictechniquestoarrestdefectsbottlenecksandbaddesigninyourprograms AT henneykevlin yourcodeasacrimesceneuseforensictechniquestoarrestdefectsbottlenecksandbaddesigninyourprograms AT talbotkelly yourcodeasacrimesceneuseforensictechniquestoarrestdefectsbottlenecksandbaddesigninyourprograms AT tornhilladam useforensictechniquestoarrestdefectsbottlenecksandbaddesigninyourprograms AT henneykevlin useforensictechniquestoarrestdefectsbottlenecksandbaddesigninyourprograms AT talbotkelly useforensictechniquestoarrestdefectsbottlenecksandbaddesigninyourprograms |