_overview-3-how-do-we-get-well-structured-containment.jpg "Overview 3 - How do we get well-structured containment? from code refactoring means Video Screenshot Preview")
GalleryPlay Video:
(Note: The default playback of the video is HD VERSION. If your browser is buffering the video slowly, please play the REGULAR MP4 VERSION or Open The Video below for better experience. Thank you!)
⏲ Duration: 3 min 74 sec
✓ Published: 15-Dec-2013
✓ Published: 15-Dec-2013
Description:
This video explores how we can discover or create a “well-structured containment model” for an existing code-base.nnScript:nPreviously we asserted that “well-structured containment” nis a hierarchical organization of all of the files in a code-base, into containers, so that nno containers contain too many files or child-containers, andnThe dependency relationships between containers is acyclicnSuch a model will give us the foundation we need for defining a software architecture, with the
This video explores how we can discover or create a “well-structured containment model” for an existing code-base.nnScript:nPreviously we asserted that “well-structured containment” nis a hierarchical organization of all of the files in a code-base, into containers, so that nno containers contain too many files or child-containers, andnThe dependency relationships between containers is acyclicnSuch a model will give us the foundation we need for defining a software architecture, with the
Share with your friends:
Whatsapp | Viber | Telegram | Line | SMS
Email | Twitter | Reddit | Tumblr | Pinterest
_doc-norton-the-technical-debt-trap.webp "Technical Debt has become a catch-all phrase for any code that needs to be re-worked. Much like Refactoring has become a catch-all phrase for any activity that involves changing code. These fundamental misunderstandings and comfortable yet mis-applied metaphors have resulted in a plethora of poor decisions. What is technical debt? What is not technical debt? Why should we care? What is the cost of misunderstanding? What do we do about it? Doc discusses the origins of the metaphor, what it means")
_what-is-refactoring-and-why-is-it-so-important.webp "nullQueries")
_what-is-refactoring-124124-3-minute-thursday.webp "Step Aument")
_the-truth-about-code-refactoring-what-is-code-refactoring.webp "jSparrow - start programming")
_code-refactoring.webp "Derek Banas")
_thomas-sundberg-technical-debt.webp "When you borrow money you end up having a debt. A loan must be repaid. When you cut corners in your development, you end up with a technical debt. Technical debts also need to be repaid.nnAvoiding amortizing your technical debt and instead increasing it will result in a code base that rots. A code base that rots is a bad code base and it will slow down development until it finally grinds to a halt. Building up a technical debt isn’t something that happens over a night. It is the sum of all sho")
_reviewing-your-code-refactoring.webp "Jacob Sorber")
_doc-norton-the-technical-debt-trap.jpg)
_what-is-refactoring-and-why-is-it-so-important.jpg)
_what-is-refactoring-124124-3-minute-thursday.jpg)
_the-truth-about-code-refactoring-what-is-code-refactoring.jpg)
_code-refactoring.jpg)
_thomas-sundberg-technical-debt.jpg)
_reviewing-your-code-refactoring.jpg)
![[+]](/images/menu.gif){kind=small}