Global Analysis and Transformations in Preprocessed Languages
IEEE Transactions on Software Engineering
An improved methodology on information distillation by mining program source code
Data & Knowledge Engineering
Automatic identification of key classes in a software system using webmining techniques
Journal of Software Maintenance and Evolution: Research and Practice
Improving design-pattern identification: a new approach and an exploratory study
Software Quality Control
CScout: A refactoring browser for C
Science of Computer Programming
Robotran: evolution of an undergraduate software project
Journal of Computing Sciences in Colleges
Proceedings of the 3rd International Conference on Human Computer Interaction
Taupe: Visualizing and analyzing eye-tracking data
Science of Computer Programming
Hi-index | 0.00 |
From the Publisher:If you are a programmer, you need this book.You've got a day to add a new feature in a 34,000-line program:Where do you start? Page 333How can you understand and simplify an inscrutable piece of code? Page 39Where do you start when disentangling a complicated build process? Page 167 How do you comprehend code that appears to be doing five things in parallel? Page 132You may read code because you have to--to fix it, inspect it, or improve it. You may read code the way an engineer examines a machine--to discover what makes it tick. Or you may read code because you are scavenging--looking for material to reuse. Code-reading requires its own set of skills, and the ability to determine which technique you use when is crucial. In this indispensable book, Diomidis Spinellis uses more than 600 real-world examples to show you how to identify good (and bad) code: how to read it, what to look for, and how to use this knowledge to improve your own code. Fact: If you make a habit of reading good code, you will write better code yourself.