How sunilgudivada/notebook works
High-Level Purpose and Categories
• Data Structures and Algorithms
• System Design (including building blocks, key concepts, and case studies like “UPI Payment” or “Stock Broker System”)
• Design Patterns (creational, behavioral, structural)
• Concurrency and Multithreading
• Interview Questions (including sublevels like Google L3/L4 and phone screen questions)
• Preparation Manual (with curated guides and schedules)
• Miscellaneous/Additional Resources (e.g., research papers and web applications guidelines)
• GitBook & Rendered Static Content Infrastructure (this project is rendered to a website or PDF)
Out the File/Directory Structure into Logical Components
• At the top level, represent individual modules—each directory (for example, “data-structures-and-algorithms”, “system-design”, “design-patterns”, “concurrency-and-multithreading”, etc.) should be a separate block.
• For each module, consider subcomponents:
• For Data Structures and Algorithms: highlight “topics”, with further subdivisions like “sorting”, “graphs”, “stacks-and-queues”, and the “analysis” pages.
• For Design Patterns: separate into “creational”, “behavioral”, and “structural” patterns.
• For Interview Questions and Preparation Manual, note the grouping by difficulty levels and additional reference links.
Specify the Relationships and How They Connect
• Interdependence where one topic references another (for example, system design concepts often reference design patterns and algorithms).
• If applicable, connect the “references” directories (found under many modules like concurrency and system design) to the corresponding main topic to denote additional detail.
Architectural Patterns / Design Principles
• Although this is static content, consider using the separation-of-concerns principle: each topic area is isolated but collectively forms the complete learning library.
• That the project is modular and extensible – new topics or subtopics can be added as new directories.