• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Crime Scenes: CSI?

 
Ranch Hand
Posts: 30
Mac OS X Spring AngularJS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Adam,

This book sounds very interesting for two reasons:
1/ I'm a huge CSI fan. Will there be CSI references in the book? What's your favorite CSI series? (hint: there's only one - it's Las Vegas, the rest is total bs)
2/ When I used to debug my code, I'd always tell people I would be a good member on the CSI team, because indeed, debugging or solving bugs is a lot like inspecting a crime scene. Do you only talk about debugging / bugfixing, or do you propose other techniques as well?

Kind regards,
Dylan (who'd probably love this book!!)
 
Author
Posts: 21
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Dylan

I'm afraid I have to disappoint you on #1 - I've never seen CSI. In fact, I don't even watch TV. The criminal cases and ideas that we discuss in the book are from a more academic perspective. That said, I do include one or two pop-culture references.

The book doesn't focus on debugging. But I think that debugging requires a similar mindset to what I try to introduce in the book and I share your view. Your Code as a Crime Scene covers techniques to analyse large codebases and identify maintenance problems, code at risk for defects and code that becomes team productivity bottlenecks. We mine our supporting evidence from how we've actually worked with the code so far. And that's information we get from our version-control systems.
 
reply
    Bookmark Topic Watch Topic
  • New Topic