DOMAIN:BACKEND:THOUGHT_LEADERS¶
OWNER: urszula (Team Alfa), maxim (Team Bravo)
UPDATED: 2026-03-24
SCOPE: key people, companies, repos, and resources for backend TypeScript/Node.js
LEADERS:TYPESCRIPT¶
MATT_POCOCK¶
ROLE: TypeScript educator, author
PLATFORM: totaltypescript.com
GITHUB: github.com/mattpocock
WHY_RELEVANT: created Total TypeScript — the definitive TypeScript training platform. His workshops on type-level programming, generics, and advanced patterns are industry standard. Book "Total TypeScript" (No Starch Press, April 2026) co-authored with Taylor Bell.
KEY_CONTRIBUTIONS:
- Total TypeScript workshops (5 professional-grade courses)
- ts-reset library — fixes TypeScript's built-in types (e.g., .filter(Boolean) works properly)
- Effect advocacy — functional error handling patterns
- Type challenges — practical advanced TypeScript exercises
LEARN_FROM: his "TypeScript Tips" series — short videos explaining one concept each
QUOTE: Ryan Cavanaugh (TypeScript lead at Microsoft) called his work "an invaluable resource to countless developers"
TANNER_LINSLEY¶
ROLE: creator of TanStack (formerly React Query, React Table, React Router)
GITHUB: github.com/tannerlinsley
WHY_RELEVANT: TanStack Router + Start bring full-stack type safety to the frontend-backend boundary. His thinking on data fetching patterns, caching, and type inference heavily influences backend API design.
KEY_CONTRIBUTIONS:
- TanStack Query — de facto standard for server state management
- TanStack Router — type-safe routing with built-in data loading
- TanStack Start — full-stack React framework with type-safe RPC
LEARN_FROM: TanStack Start's approach to type-safe server functions — similar to Hono RPC
RELEVANCE_TO_GE: when building Next.js projects, TanStack Query is the standard for API consumption
SINDRE_SORHUS¶
ROLE: prolific open-source author (1000+ npm packages)
GITHUB: github.com/sindresorhus
WHY_RELEVANT: author of foundational Node.js utilities that GE projects may depend on. Expert on ESM migration, TypeScript best practices for library authors, Node.js API design.
KEY_CONTRIBUTIONS:
- got (HTTP client), execa (process execution), p-limit (concurrency control)
- type-fest — collection of essential TypeScript types
- ESM-only packages movement — pushed the ecosystem toward native ES modules
- ky — tiny HTTP client for browsers/Deno (fetch-based)
LEARN_FROM: his package design philosophy — small, focused, typed, well-tested
RULE: when needing a utility, check if Sindre has a package for it before writing from scratch
LEADERS:HONO¶
YUSUKE_WADA¶
ROLE: creator of Hono, Developer Advocate at Cloudflare
HANDLE: @yusukebe (GitHub, X)
BACKGROUND: 17+ years in web development from Japan. Former CTO of Omoroki (creators of "Bokete" UGC service). Author of a 2012 book on building web services (Gijutsu-Hyoronsha). Started Hono in December 2021.
WHY_RELEVANT: Hono is GE's primary backend framework — understanding the creator's philosophy informs correct usage patterns.
PHILOSOPHY: "I'm making a framework everyday. I'm a creator of Hono." — driven by passion for developer experience and performance.
KEY_DECISIONS:
- Web Standards-based (Request/Response, not custom abstractions)
- RegExpRouter for fastest possible routing
- Multi-runtime from day one (not Node.js-first)
- RPC client built into the framework (not a separate package)
BLOG: blog.yusu.ke — technical posts about Hono internals
LEARN_FROM: "The story of web framework Hono" on Cloudflare blog — design decisions explained
LEADERS:DRIZZLE¶
DRIZZLE_TEAM (ORM)¶
COMPANY: Drizzle Team (drizzle.team)
DOCS: orm.drizzle.team
GITHUB: github.com/drizzle-team/drizzle-orm
WHY_RELEVANT: Drizzle is GE's standard ORM — their docs and release notes are primary reference.
KEY_PEOPLE:
- Andrew Sherman (lead maintainer)
- Dan Kochetov (core contributor)
PHILOSOPHY: SQL-in-TypeScript, not TypeScript-that-generates-SQL. Drizzle maps 1:1 to SQL — if you know SQL, you know Drizzle.
CURRENT_STATE: v0.38+ stable, v1.0 beta in development (2026). ~7.4KB bundle.
LEARN_FROM: Drizzle Discord — active community, quick answers to edge cases
NOTE: Drizzle team actively responds to GitHub issues — file bugs with reproduction
LEADERS:NODE_JS¶
MATTEO_COLLINA¶
ROLE: Node.js TSC member, co-creator of Fastify, creator of Pino
GITHUB: github.com/mcollina
WHY_RELEVANT: created Pino (GE's standard logger) and Fastify. Deep expertise in Node.js performance, streams, and production patterns.
KEY_CONTRIBUTIONS:
- Pino — fastest Node.js logger (GE standard)
- Fastify — high-performance Node.js framework
- undici — modern HTTP client built into Node.js
- Node.js streams and event loop expertise
LEARN_FROM: his conference talks on Node.js performance — especially "There are no slow languages, only slow runtimes" and talks on the event loop
RELEVANCE_TO_GE: his work on Pino directly shapes GE's logging patterns
JAMES_SNELL¶
ROLE: Node.js TSC member, Cloudflare
GITHUB: github.com/jasnell
WHY_RELEVANT: deep Node.js core expertise, contributor to Web Standards, performance APIs
KEY_CONTRIBUTIONS:
- Node.js Performance measurement APIs
- HTTP/2 implementation in Node.js
- Workers standards at Cloudflare
NODE_JS_BEST_PRACTICES REPO¶
REPO: github.com/goldbergyoni/nodebestpractices
STARS: 100k+
AUTHOR: Yoni Goldberg
WHY_RELEVANT: comprehensive, community-curated Node.js best practices covering project structure, error handling, testing, security, production, and more. Updated regularly.
HOW_TO_USE: reference specific sections when implementing a new pattern — each practice has explanations and code examples
SECTIONS_MOST_RELEVANT_TO_GE:
- Error handling practices
- Testing practices
- Security practices
- Production practices (process management, monitoring)
- Project structure practices
LEADERS:ARCHITECTURE¶
OSKAR_DUDYCZ¶
ROLE: architect, Event Sourcing/CQRS expert
BLOG: event-driven.io
GITHUB: github.com/oskardudycz
WHY_RELEVANT: practical Event Sourcing and CQRS patterns, especially in TypeScript. His "Practical Event Sourcing Workshop" uses Node.js/TypeScript.
KEY_CONTRIBUTIONS:
- emmett — TypeScript-first Event Sourcing framework
- Event Sourcing in Node.js workshops
- Blog posts on vertical slices, CQRS practical implementation
LEARN_FROM: "Vertical Slices in Practice" — practical guide to structuring code by feature
JIMMY_BOGARD¶
ROLE: inventor of Vertical Slice Architecture term, creator of MediatR/AutoMapper
WHY_RELEVANT: coined the vertical slice approach GE uses. While his implementation is in C#, the architectural concepts are language-agnostic.
LEARN_FROM: his original blog post "Vertical Slice Architecture" — the fundamental argument against layered architecture
LEADERS:API_DESIGN¶
PHIL_STURGEON¶
ROLE: API design expert, author
BOOK: "Build APIs You Won't Hate" (2013, updated 2020)
BLOG: apisyouwonthate.com
WHY_RELEVANT: practical API design guidance covering pagination, versioning, error handling, and evolution patterns.
LEARN_FROM: the blog covers common REST API mistakes and how to fix them
OPENAPI_INITIATIVE¶
ORG: openapis.org
SPEC: OpenAPI 3.1 (current)
WHY_RELEVANT: GE uses spec-first API development with @hono/zod-openapi
LEARN_FROM: official spec documentation — understand what each field means before generating from Zod
RESOURCES:REPOSITORIES¶
ESSENTIAL_REPOS¶
| Repository | Why | Stars |
|---|---|---|
| goldbergyoni/nodebestpractices | Comprehensive Node.js best practices | 100k+ |
| honojs/hono | GE's primary framework — read source for patterns | 22k+ |
| drizzle-team/drizzle-orm | GE's ORM — check issues for known gotchas | 25k+ |
| sindresorhus/type-fest | TypeScript utility types collection | 14k+ |
| mattpocock/ts-reset | Fix built-in TypeScript types | 8k+ |
| total-typescript/beginners-typescript-tutorial | Start here for TypeScript basics | 8k+ |
| pinojs/pino | GE's logging standard — read docs for config | 14k+ |
| Effect-TS/effect | Typed effects system — watch for future adoption | 8k+ |
| trpc/trpc | Type-safe API reference (Hono RPC is lighter) | 35k+ |
| colinhacks/zod | Validation library — read docs for advanced patterns | 35k+ |
STARTER_TEMPLATES¶
| Template | When |
|---|---|
| honojs/starter | Starting a new Hono project — official templates |
| drizzle-team/drizzle-orm/examples | Drizzle integration examples — check before implementing |
RESOURCES:BLOGS_AND_NEWSLETTERS¶
| Source | Focus | Frequency |
|---|---|---|
| totaltypescript.com/articles | TypeScript deep dives | Weekly |
| blog.yusu.ke | Hono internals and philosophy | Monthly |
| event-driven.io | Event Sourcing, CQRS, architecture | Biweekly |
| apisyouwonthate.com | API design patterns | Monthly |
| orm.drizzle.team/docs | Drizzle official docs (canonical) | On release |
| nodejs.org/en/blog | Node.js releases and security updates | On release |
| architecture-weekly.com | Software architecture newsletter | Weekly |
RESOURCES:CONFERENCE_TALKS¶
| Talk | Speaker | Topic |
|---|---|---|
| "Hono v3 and v4" (JSConf JP 2023) | Yusuke Wada | Hono design philosophy and roadmap |
| "There are no slow languages" | Matteo Collina | Node.js performance myths debunked |
| "Vertical Slice Architecture" | Jimmy Bogard (NDC) | Feature-first vs layer-first architecture |
| "Total TypeScript" (various) | Matt Pocock | Advanced TypeScript patterns (YouTube) |
| "Event Sourcing in 1 hour" | Oskar Dudycz | Practical ES/CQRS introduction |
RESOURCES:BOOKS¶
| Book | Author | Relevance |
|---|---|---|
| Total TypeScript (2026) | Matt Pocock | TypeScript mastery — GE's language |
| Build APIs You Won't Hate | Phil Sturgeon | API design patterns used by GE |
| Node.js Design Patterns (4th ed) | Mario Casciaro | Node.js architecture patterns |
| Designing Data-Intensive Applications | Martin Kleppmann | Architecture foundations (PostgreSQL, event systems) |
| SQL Performance Explained | Markus Winand | PostgreSQL query optimization |
LEADERS:COMPANIES¶
CLOUDFLARE¶
RELEVANCE: Hono's primary sponsor, Yusuke Wada works there. Pushes Web Standards. Hono was born for Workers.
VERCEL¶
RELEVANCE: Next.js (GE uses for SSR), edge runtime, Matt Pocock previously worked there. Drives TypeScript ecosystem.
DRIZZLE_TEAM¶
RELEVANCE: GE's ORM provider. Small, focused team. Ship fast, respond to issues.
PLATFORMATIC¶
RELEVANCE: Matteo Collina's company. Built on Fastify. Good for understanding Node.js production patterns even if GE uses Hono.
LEADERS:AGENTIC_NOTE¶
FOR_AGENTS_WRITING_CODE:
- When implementing a pattern, check if the relevant thought leader has documented best practices
- When encountering an edge case in Drizzle, check GitHub issues before inventing a workaround
- When unsure about TypeScript types, reference Matt Pocock's articles or type-fest
- When debugging Node.js performance, reference Matteo Collina's talks
- When designing APIs, reference Phil Sturgeon's patterns
- NEVER blindly follow a blog post without verifying against official docs
- PREFER official docs over Medium articles — Medium content has no review process