Multi-year knowledge compounding for software engineering mastery

One concept. One drop. 30-60 seconds. Repeat for 3-5 years.

Replace scrolling with deliberate skill-building. Each entry is standalone, digestible, and implementation-focused.

drops/              # 30-60 second knowledge drops
├── ds/            # Data structures  
├── algo/          # Algorithms
├── patterns/      # Design patterns
├── security/      # Security concepts
└── systems/       # System design

meta/              # Cross-AI prompts & tracking

1. Copy drops/TEMPLATE.md
2. Write one concept (30-60 seconds)
3. Save to appropriate category
4. Commit with git add . && git commit -m "Add drop: [concept]"

# Concept Name

**Category**: ds|algo|patterns|security|systems
**Difficulty**: 1-5
**Read Time**: 30s|45s|60s
**Tags**: #tag1 #tag2

## What
One-sentence definition.

## Why It Exists
Problem it solves (2-3 lines).

## How It Works
Core mechanism (4-6 lines).

## Code
Minimal working example (15-20 lines).

## The Gotcha
Common mistake.

## Real-World Example
Production use case.

## Micro Challenge
Thinking question.

**Related**: [link]
**Next**: [harder-concept]

Phase 1 (Months 1-6): Arrays, Stack, Queue, Hash, Recursion, Big-O
Phase 2 (Months 6-12): Sorting, Search, Sliding Window, DP
Phase 3 (Year 2): Design Patterns
Phase 4 (Year 2-3): System Design
Phase 5 (Year 3+): Security Deep Dives

✅ Do: 30-60s max, one insight, working code, commit imperfect work
❌ Don't: Write essays, duplicate, skip code, aim for perfection

• Tiny friction = Consistency
• Templates = Quality
• Multi-year horizon = Compounding

You're building your second brain.

License: MIT

---