Professional Architecture
System Overview
16 years of evolution from writing code to writing about code. Each role built on the previous, creating a unique combination of skills that makes me effective as a technical writer.
Career progression:
Web Developer → Technical Lead → Technical Director → Solutions Architect → Technical Writer → Documentation Engineer
Evolution History
v1.0: Web Developer (2010–2014)
Core competencies developed:
- PHP, JavaScript, HTML/CSS
- Database design and optimization
- E-commerce platforms (Magento, custom builds)
- Client communication and requirements gathering
Key learning: Understanding how developers think and what they need to be successful.
v1.5: Technical Lead (2014–2017)
Core competencies developed:
- Team leadership and mentoring
- Code review and quality standards
- Project planning and delivery
- Technical decision-making
Key learning: How to communicate technical concepts to non-technical stakeholders.
v2.0: Technical Director (2017–2019)
Core competencies developed:
- System architecture design
- DevOps and CI/CD pipelines
- Performance optimization
- Business strategy and technical roadmapping
Key learning: Seeing the bigger picture beyond just code.
v2.5: Solutions Architect & Consultant (2019–2022)
Core competencies developed:
- Enterprise integrations
- Payment systems (Stripe, PayPal, custom)
- API design and documentation
- Client advisory and problem-solving
Key learning: How to quickly understand complex systems and explain them clearly.
v3.0: Technical Writer (Sep 2022 – Nov 2023)
Company: Starknet Foundation (Ethereum L2, ZK-rollup built on STARK proofs) Scope: Sole owner of all developer documentation for Ethereum Layer 2 protocol
What I built:
- Complete documentation suite for zero-knowledge proof system
- Cairo smart contract language guides
- Integration tutorials for dApp developers
- API reference documentation
- Collaboration framework with cryptographers and protocol engineers
Key learning: The power of excellent documentation to accelerate developer adoption.
Why the transition?
After 15 years of building systems, I discovered I loved the challenge of explaining complex technical concepts more than building the systems themselves. Documentation engineering combines both—writing clarity with technical infrastructure.
v3.5: Independent Technical Writer (2022–2025)
Focus: Documentation consulting with emphasis on Web3, SaaS, and technical infrastructure
Specializations:
- Blockchain protocols and smart contracts
- API documentation
- Developer experience optimization
- Documentation infrastructure (Docusaurus, Nextra, custom tooling)
v4.0: Senior Technical Writer — Payments Infrastructure (2025–Present)
Company: Mastercard (MDES Manager) Scope: Senior contract technical writer, leading full documentation and UX content overhaul for MDES Manager — Mastercard's self-service tokenisation platform used by banks, issuers, processors, and payment service providers
What I delivered:
- Full structural and editorial overhaul of the 379-page MDES Manager User Guide in DITA XML
- UX microcopy revision across 100+ product screens, establishing 12 reusable content patterns
- 14 customer-facing delivery guides structured for dual readability (human and LLM/RAG retrieval), informed by analysis of 949 support tickets
- Contributed to scoping a conversational AI assistant for MDES, benchmarked against Klarna, Bank of America Erica, and Morgan Stanley's internal KB deployment
Key learning: Enterprise payments infrastructure documentation requires the same rigour as protocol documentation — but the audience is financial institutions, not developers. Mastercard's brand writing standards, W3C COGA accessibility guidelines, and DITA XML structured authoring are the discipline.
Technical Stack Evolution
Development era:
- Languages: PHP, JavaScript, Python, Node.js
- Frameworks: React, Next.js, Laravel, Express
- Infrastructure: AWS, Docker, Kubernetes, CI/CD
- Databases: MySQL, PostgreSQL, MongoDB, Redis
Documentation era:
- Platforms: DITA XML (structured authoring), DITA-OT (PDF generation), Docusaurus, Nextra, GitBook, AsciiDoc
- Languages: Markdown, MDX, reStructuredText, AsciiDoc
- Tools: Git, GitHub Actions, Vale, markdownlint, Claude Code CLI
- Technologies documented: Solidity, Cairo, Rust, zkSNARKs/STARKs, Layer 2 protocols
Migration Path
This architecture makes me uniquely effective because I can:
- Understand your codebase without extensive hand-holding
- Build documentation infrastructure not just write content
- Debug technical issues in the docs deployment pipeline
- Collaborate effectively with senior engineers and cryptographers
- Think systematically about documentation as product