A short reference for terms that recur across this site — bio, blog posts, and resume. Defined here so visiting humans and agents share the same vocabulary.
Agent Led Growth (ALG)
A go-to-market practice where AI agents — both general-purpose models and product-specific copilots — are treated as a primary distribution and adoption channel, on par with human users. Includes content optimized for agent retrieval (markdown sources, structured data), product surfaces designed for agent consumption (CLI, APIs, skills, plugins), and metrics that track agent-originated activity (deploys, signups, support resolutions).
Agent Engine Optimization (AEO)
The agent-readability analogue of SEO. AEO is the practice of structuring content, navigation, and metadata so that AI agents can discover, parse, summarize, and cite a site accurately. Includes markdown mirrors, llms.txt, JSON-LD, sitemap.md, and other agent-friendly conventions.
Agent Readability
The general property of a site or document being structured so that AI agents (LLM-driven assistants, retrieval pipelines, crawlers) can ingest it correctly. Measured by the a14y scorecard.
DevRel
Developer Relations. The practice of building two-way relationships between a software product or platform and the developers who use it. DevRel teams typically include developer advocates, developer engineers, technical writers, program managers, and instructional designers. The goal is to help developers succeed with the product while feeding their experience back into the product.
DevRel Lifecycle
A model for thinking about developer engagement as a series of stages — discovery, evaluation, learning, building, scaling, advocating — each with its own content, tools, and team responsibilities. See the post for the full framing.
DX
Developer Experience. The end-to-end quality of using a developer-facing product or platform — onboarding, documentation, APIs, CLIs, error messages, support, community. Adjacent to but broader than UX.
GSOC
Google Summer of Code. A long-running Google program that pays university students to contribute to open source projects over a summer. First held in 2005; celebrated its 20th year in 2024.
Google Developer Advocacy / Developer Studio
Internal Google teams Timothy led. Developer Advocacy covered all developer-facing platforms; the Developer Studio was the in-house video production team for developer content (talks, tutorials, launches).
Glass / Google Glass
The Google augmented-reality headset (2012–2015 consumer; later enterprise). Timothy was the developer advocate for Glass, ran the launch demo, and stood up the developer platform.
llms.txt
A plain-text file at a site root (/llms.txt or /.well-known/llms.txt) that lists key URLs and a brief site description in markdown. Designed for LLM-based retrieval to find the canonical, agent-friendly version of a site quickly. See llmstxt.org for the specification.
Microsite
A small, focused site (or section of a site) with its own brand and navigation, run independently of the main site. Used here to describe how this repo is organized: public/ (homepage), blog/ (Jekyll), and resume/ (Jekyll) historically built independently. See PRODUCT.md for the architecture.
Open Source / OSS
Software released under a license that grants users the right to use, study, modify, and distribute the source code. Open Source Software is a major part of Timothy’s Google career — including running Google’s open source policy and program offices.
Schema.org / JSON-LD
A structured-data vocabulary for describing pages, articles, people, breadcrumbs, etc., embedded in HTML as JSON-LD <script> blocks. Helps agents and search engines understand page semantics. The blog uses BlogPosting + BreadcrumbList; the homepage uses WebSite; the resume uses Person.
Skills (Claude Code, Vercel)
Small, named units of agent capability — prompt + tools + instructions — that an agent can invoke on demand. Used in Claude Code, the Anthropic SDK, and (in slightly different form) elsewhere. Closely related to “tools” and “plugins.”