Kent discusses the balance between tidying code and making necessary changes, emphasizing that while coupling can’t be completely eliminated, it can be managed through cohesion. He introduces the concept of "tiding," which encourages programmers to consider whether to clean up messy code before making changes, highlighting that this decision varies from case to case. The conversation also touches on the importance of structure in code to facilitate easier modifications.