Add personal/yml_distilled.md

personal/yml_distilled.md

@@ -0,0 +1,77 @@
+# Decoding Jason Davis' Professional Trajectory
+
+Based on his LinkedIn experience, Jason Davis has a fascinating career arc that explains his current "bounded chaos" automation philosophy. Let me analyze the key patterns:
+
+## Career Evolution
+
+1. **Early Years (2005-2010)**
+   - Field service and network operations roles
+   - Developed foundational understanding of infrastructure extremes
+   - Learned that "better technology ≠ adoption" (his BSD vs Linux comment)
+   - Recognized the tension between productivity and technical debt
+
+2. **Enterprise Scaling (2010-2018)**
+   - AT&T, Kaiser Permanente, Charter Communications
+   - Worked with critical infrastructure at massive scale
+   - Developed appreciation for rigorous processes ("JC and his wall charts")
+   - Learned from exceptional managers about leadership and raising standards
+
+3. **Consulting Phase (2018-2022)**
+   - Verizon, Zivaro, AWS
+   - Exposure to global RFP processes and diverse OEM environments
+   - "Chaos at scale" experience at AWS
+   - Transition toward more strategic/consultative roles
+
+4. **Current Entrepreneurial Phase (2022-present)**
+   - Combining infrastructure automation with AI/LLMs
+   - Focus on "structured chaos" through CUE/Jinja2/Go tooling
+   - Boutique multidisciplinary solutions at Dynamic Impact Marketing
+
+## Key Themes in His Approach
+
+1. **Infrastructure as Code Meets Marketing**
+   - His current work combines:
+     - Rigorous config management (CUE)
+     - Flexible templating (Jinja2/Go)
+     - LLM capabilities
+     - Marketing applications
+
+2. **The "Bounded Chaos" Philosophy Comes From:**
+   - Seeing over-engineering at Charter ("most favorite tech job")
+   - AWS's scale challenges ("chaos at scale")
+   - Verizon's global RFP processes
+   - Kaiser's critical data center operations
+
+3. **Why His System Works:**
+   - Balances AT&T's rigorous processes ("gold standard team")
+   - With AWS's need for flexibility at scale
+   - While avoiding PHNS's "productivity creating tech debt" pitfall
+
+## Practical Applications for You
+
+Given his background, here's how to adapt his approach:
+
+1. **Start Small But Structured**
+   - Use his "CUE for configs + Jinja2 for templates" pattern
+   - Example: Build a content generation system where:
+     - CUE defines strict content guidelines
+     - Jinja2 templates create variations
+     - LLMs fill in the creative parts
+
+2. **Raspberry Pi MVP Idea**
+   - Create a "Policy-Driven Content Server":
+   ```bash
+   # Architecture
+   CUE files → define content rules (character limits, brand guidelines)
+   Jinja2 → website templates
+   Python → LLM integration for dynamic content
+   Docker → containerized deployment
+   ```
+   - Perfect for local marketing agencies
+
+3. **Monetization Pathways**
+   - Automated compliance documentation generator
+   - Policy-aware content creation tools
+   - Marketing infrastructure that "can't break brand guidelines"
+
+Would you like me to develop one of these ideas into a more detailed technical blueprint? I can show exactly how to implement his "bounded chaos" approach in a weekend project.