Lots of updates

This commit is contained in:
paul
2026-03-18 23:32:45 -04:00
parent 0e19326bcb
commit b202ec9954
33 changed files with 4312 additions and 648 deletions

View File

@@ -2,6 +2,25 @@
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
---
## ⚠️ CRITICAL: NEVER FABRICATE NUMBERS OR DETAILS
**This is checked on every build-resume run. Violation is a critical error.**
- **ONLY use facts from `paul-halvorsen-resume-detailed.md`**
- DO NOT invent: team sizes, customer counts, specific metrics, percentages, achievements, scales
- If a detail isn't in the detailed resume, do not include it
- Allowed: reframe/reorder existing information, remove less relevant details
- **Examples of violations:**
- ❌ "$9 trillion in assets" (not in detailed resume)
- ❌ "40+ engineers" (not in detailed resume)
- ❌ "thousands of security events daily" (not in detailed resume)
- ✓ "10 auto-scaling clusters" (IS in detailed resume)
- ✓ "~90% CPU reduction" (IS in detailed resume)
---
## Project Overview
This is a resume builder using Pandoc to convert Markdown resumes with YAML metadata to PDF via LaTeX templates. The build process is containerized using Podman (Docker alternative) for reproducibility and portability.
@@ -277,3 +296,60 @@ Is the company a startup or growth-stage company?
- **Valon** (Series C, a16z-backed): awesome-cv recommended
- **Enterprise customers**: jb2resume-modern
- **Government/DoD contracts**: jb2resume (classic)
## CRITICAL: Resume Content Rules
### Never Fabricate Numbers, Metrics, or Details
**⚠️ BLOCKING REQUIREMENT: DO THIS CHECK BEFORE WRITING EACH RESUME SECTION**
**ONLY use facts from `paul-halvorsen-resume-detailed.md` as the source of truth.**
**Do NOT invent:**
- Team sizes ("40+ engineers across company")
- Customer/endpoint counts unless explicitly documented
- Specific metrics not stated in detailed resume
- Job responsibilities not listed
- Percentages, scales, or achievements without documentation
- Any number or quantifiable claim not in detailed resume
**Pre-write checklist (do this for EVERY bullet point):**
- [ ] Is this number/metric in paul-halvorsen-resume-detailed.md?
- [ ] If NO, do not include it
- [ ] Am I reframing documented information, or inventing new information?
- [ ] If inventing, stop and remove the bullet
**What IS allowed:**
- Reorder existing information for job relevance
- Rephrase/reframe documentation for clarity
- Remove less relevant details to save space
- Use exact metrics/percentages from detailed resume
**Violations Paul has caught (do not repeat):**
- ❌ "$9 trillion in assets" (Addepar) — Not in detailed resume
- ❌ "40+ engineers across company" (DOPE) — Not in detailed resume
- ❌ "thousands of security events daily" (made up) — Not documented anywhere
**Valid examples (these ARE documented):**
- ✓ "Performance improvements: reduced CPU usage ~90%" → Binary Defense section
- ✓ "Customers: Fortune 500 companies, thousands of endpoints" → Binary Defense section
- ✓ "10 auto-scaling clusters in AWS" → Abnormal AI section
- ✓ "MySQL database (thousands of records)" → NSA section
**Apply this rule to:**
- Work experience descriptions
- Metrics and achievements
- Team structures
- Customer information
- Technical details
- ANY quantifiable claim
### Job Breakdown File Checklist
When creating `job-breakdown.md` files:
- [ ] All numbers in "Requirements Analysis" table come from job posting OR documented facts
- [ ] All numbers in "Strengths in Context" are from paul-halvorsen-resume-detailed.md
- [ ] No invented metrics like "years of experience with technology X" unless documented
- [ ] Salary recommendations are conservative estimates, not fabricated
- [ ] Keyword match % is realistic based on actual resume content
- [ ] All claims about Paul's background are verifiable from detailed resume