Using an RTSJ-compatible MVC pattern as basis for configurable event-driven real-time software
Proceedings of the 8th International Workshop on Java Technologies for Real-Time and Embedded Systems
Managing technical debt in software-reliant systems
Proceedings of the FSE/SDP workshop on Future of software engineering research
Second international workshop on managing technical debt (MTD 2011)
Proceedings of the 33rd International Conference on Software Engineering
Extreme apprenticeship method: key practices and upward scalability
Proceedings of the 16th annual joint conference on Innovation and technology in computer science education
ACM SIGSOFT Software Engineering Notes
Localizing globals and statics to make C programs thread-safe
CASES '11 Proceedings of the 14th international conference on Compilers, architectures and synthesis for embedded systems
Management, structures and tools to scale up personal advising in large programming courses
Proceedings of the 2011 conference on Information technology education
The artist in the computer scientist: more humanity to our research
Proceedings of the 10th SIGPLAN symposium on New ideas, new paradigms, and reflections on programming and software
A software craftsman's approach to data structures
Proceedings of the 43rd ACM technical symposium on Computer Science Education
ACM SIGSOFT Software Engineering Notes
Articulating everyday actions: an activity theoretical approach to scrum
Proceedings of the 30th ACM international conference on Design of communication
Three years of design-based research to reform a software engineering curriculum
Proceedings of the 13th annual conference on Information technology education
Agile Software Development: The Straight and Narrow Path to Secure Software?
International Journal of Secure Software Engineering
Empirical evaluation of periodic retrospective assessment
Proceeding of the 44th ACM technical symposium on Computer science education
Refactoring delta-oriented software product lines
Proceedings of the 12th annual international conference on Aspect-oriented software development
Strategies for avoiding text fixture smells during software evolution
Proceedings of the 10th Working Conference on Mining Software Repositories
Learning agile software engineering practices using coding dojo
Proceedings of the 14th annual ACM SIGITE conference on Information technology education
Crafting interaction: The epistemology of modern programming
Personal and Ubiquitous Computing
Hi-index | 0.00 |
Even bad code can function. But if code isnt clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesnt have to be that way.Noted software expert Robert C. Martin, presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin, who has helped bring agile principles from a practitioners point of view to tens of thousands of programmers, has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code on the fly into a book that will instill within you the values of software craftsman, and make you a better programmerbut only if you work at it.What kind of work will you be doing? Youll be reading codelots of code. And you will be challenged to think about whats right about that code, and whats wrong with it. More importantly you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up codeof transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and smells gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.Readers will come away from this book understandingHow to tell the difference between good and bad codeHow to write good code and how to transform bad code into good codeHow to create good names, good functions, good objects, and good classesHow to format code for maximum readability How to implement complete error handling without obscuring code logicHow to unit test and practice test-driven developmentWhat smells and heuristics can help you identify bad codeThis book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.