Tools & Platforms

Tools & Platforms

The working stack. Tools are means to an end, and I use what fits the team already in place rather than importing my preferences.

Delivery & Programme

  • Linear · issue tracking and cycle planning
  • Jira · where the organisation already runs on it
  • Notion and Confluence · decision records, specifications, programme documentation
  • Slack and Teams · async-first communication, written handover across time zones
  • Miro and Figma · stakeholder workshops, service and journey mapping
  • Mermaid and Excalidraw · architecture diagrams that live in version control

Engineering & Infrastructure

Version control and CI/CD

  • Git · expert level
  • GitHub Actions · primary CI/CD
  • GitLab CI · alternative pipelines
  • Vercel and Netlify · deployment platforms

Cloud and containers

  • AWS · S3, CloudFront, core services
  • Docker · containerisation
  • Kubernetes · orchestration

Languages and frameworks

  • TypeScript / JavaScript, PHP, Python, Node.js
  • React, Next.js, Laravel, Express
  • Solidity, Cairo, Rust · reading and review level

Data

  • MySQL, PostgreSQL, MongoDB, Redis

Payments & Blockchain

  • Card tokenisation · Mastercard MDES and MDES Manager
  • Payment integration · Stripe, PayPal, PSP integrations in enterprise e-commerce
  • Ethereum tooling · Hardhat, Foundry, ethers.js
  • Starknet tooling · Scarb, Starknet Devnet, starknet.js

Content & Documentation

Enterprise structured authoring

  • DITA XML · structured authoring at Mastercard scale
  • DITA-OT · PDF generation and output processing

Docs-as-code

  • Docusaurus · used at Starknet
  • Nextra · Next.js based, including this site
  • GitBook · used at Klevu
  • MkDocs, AsciiDoc / Asciidoctor
  • Markdown, MDX, reStructuredText

Quality

  • Vale · prose linting
  • markdownlint · style checking

AI-assisted work

  • Claude Code CLI · content engineering, codebase analysis, structured refactoring at volume

Ramp-up Time

Productive within:

  • 1 day: any existing delivery or docs toolchain
  • 1 week: a new codebase, enough to review architecture and make calls
  • 2 to 4 weeks: a genuinely new technical domain, working with the people who know it

I learn fast in technically complex domains. I will not claim instant expertise in something I have never seen.