ramin
2024/03/12
5 / 5
I have been looking for this book for a long time tanx
برگزیده رفرنسهاب
Kent Beck
3 نظر
سال انتشار
صفحه
بازدید
Messy code is a nuisance. "Tidying" code, to make it more readable, requires breaking it up into manageable sections. In this practical guide, author Kent Beck, creator of Extreme Programming and pioneer of software patterns, suggests when and where you might apply tidyings to im
Messy code is a nuisance. "Tidying" code, to make it more readable, requires breaking it up into manageable sections. In this practical guide, author Kent Beck, creator of Extreme Programming and pioneer of software patterns, suggests when and where you might apply tidyings to improve your code while keeping the overall structure of the system in mind. Instead of trying to master tidying all at once, this book lets you try out a few examples that make sense for your problem. If you have a big function containing many lines of code, you'll learn how to logically divide it into smaller chunks. Along the way, you'll learn the theory behind software design: coupling, cohesion, discounted cash flows, and optionality. This book helps you: • Understand the basic theory of how software design works and the forces that act on it • Explore the difference between changes to a system's behavior and changes to its structure • Improve your programming experience by sometimes tidying first and sometimes tidying after • Learn how to make large changes in small, safe steps • Approach software design as an exercise in human relationships
Persian Summary
پرسشت با عنوان و نویسنده همین کتاب برای دستیار ارسال میشود. هر پاسخ ۲ امتیاز مصرف میکند.
3 نظر · میانگین 5.0 از ۵
2024/03/12
5 / 5
I have been looking for this book for a long time tanx
2025/01/22
5 / 5
Thanks
2025/06/07
5 / 5
The book is divided into 3 parts.
Part 1: Tidyings deals with specific small tidying opportunities that an individual developer can do as they go about changing the code for delivering business features
Part 2: Managing deals with how to integrate tidying into the day to day work
Part 3: Theory describes the economics of software, the difference between Future cash flows and Options. This is the part which gave me a clear understanding of the difference between software functionality (behavior) and structure of software (design). The clarity of the concepts and explanation is fantastic.
Awaiting the next 2 books that the author has promised.
وارد شوید تا نظر خود را ثبت کنید.
سؤال مشخص بپرس و از تجربه جامعه استفاده کن.
منابع مرتبط برای ادامه همین مسیر.
Scott Millett,Nick Tune
Martin Fowler,Kent Beck,John Brant,William Opdyke,Don Roberts