You’ve now read about ways to future-proof your code. No matter how hard you try to stay current on your codebase, time and memory work against you. The realities of human cognition mean that investing time in documenting, structuring, and refining code will pay off as your code ages and matures and its recency diminishes.
You’ve discovered how Swift implements a custom markup system to support inline documentation and how to mix and match doc markup with traditional comment systems. You’ve read about bookmark organization and how to improve the quality of words that make up your code. You’ve also considered how clever code can weigh down a project by limiting its maintainability and flexibility.
Now that you’ve spent time reading ...