Synthesized from a Grok DeepSearch conversation, April 2026.
Most senior architects fall into one of three recognizable patterns:
The Modern Full-Stack/Cloud Architect VS Code, JetBrains, GitHub Copilot, Docker/Kubernetes. Typically 1–2 AI subscriptions (Claude Pro or ChatGPT Plus, maybe Gemini for Google Workspace). Hardware: Linux/Windows mix, cloud-heavy, 10–20+ integrated CI/CD tools. Philosophy: speed of delivery, scalability, team enablement. 10–20 years experience, strong in current hype cycles, less grounding in pre-2000s history.
The Design-Centric UX Architect Figma-centric (FigJam, Dev Mode, AI plugins). Light coding via AI. Minimal deep-coding AI subscriptions. Philosophy: user empathy, design systems, handoff friction reduction. Often a design background transitioning to tech leadership.
The Enterprise/Glue Architect Broad but shallow across domains. Heavy coordination, standards enforcement, "foreman"-style orchestration. Toolchain is whatever the org mandates, with emphasis on observability and standardization.
Richard Hess maps to a fourth, rarer archetype — less common in 2026 but highly respected among veterans who survived multiple tech and AI cycles.
Editor choices signal craft over ecosystem. Sublime Text + Sublime Merge instead of VS Code (75%+ market share among principals). Raw speed, minimalism, and low friction over feature bloat. More common among high-output ICs who value velocity and customization honed over decades.
AI stack is aggressive and diversified. Most power users stop at 1–2 paid plans. A four-subscription stack (Claude Max 5x at $100/month for all-day deep work, Perplexity Pro for research, Grok SuperGrok for real-time, Gemini Pro for multimodal) is rare outside heavy coding/research roles. The upgrade from Pro to Max 5x was a pragmatic fix for real workflow friction — afternoon quota exhaustion — not a status signal.
Environment reproducibility reflects systems-first values. Mise + Brewfile + upp for exact, version-controlled runtimes. Most architects focus on cloud pipelines; this emphasizes local inspectability. Directly mirrors the YAML-driven declarative platform work: single source of truth, zero post-parse probabilistic behavior.
UI investment goes further than typical UX architects. Heavy Tailwind ecosystem (Flowbite Pro, Tailwind Plus, Web Awesome) plus custom MCP servers. Typical UX architects live in Figma. This approach bridges design → deterministic runtime with YAML as the contract language.
40+ year arc is the differentiator. Xerox Lisp Machines → expert systems → X11 stewardship → browser wars → YAML/MCP platforms. Most current principals have 10–25 years and lean into the latest hype. The explicit "AI winter calibration" — having watched the entire expert systems bubble form and collapse in real time — sets the profile apart. Hype-resistant by experience, not posture.
| Typical Principal Architect | Richard Hess (eswat2) | |
|---|---|---|
| Editor | VS Code | Sublime Text |
| AI spend | 1–2 plans, usually $20–40/mo | 4 plans, ~$170/mo |
| Environment | Cloud-native, CI/CD-heavy | Local reproducibility + Mise/Brewfile |
| UI work | Figma handoff or React components | YAML spec → deterministic runtime |
| Experience | 10–25 years, current-cycle strong | 40+ years, multiple cycles survived |
| Philosophy | Delivery velocity, team leverage | Deep flow, inspectability, continuity |
The toolchain doesn't just support the work — it embodies a seasoned, systems-first principal who values reliability and personal agency across eras rather than maximizing adoption of whatever is dominant in the current cycle.