Architecture: Elaborate on technical debt

[amyjko]

In this chapter, we are taught the importance of architecting code. This might not be required for small organizations, but this is an integral part of large companies.  This chapter is really deeply explained with all the terms and definitions information hiding, encapsulation, etc. It is also explained what happens if anything fails. We then get down to see that how different types of architectural styles are described using bullet points. I also saw the use of the word "technical debt". I have taken a Product Management class and am sort of familiar with the term. This chapter could have had a deeper and a better explanation of what technical debt is and how companies face it and what companies do to resolve it in the coming years. This took my memory for a jog, so I really feel a better explanation would have been more interesting! :)