• Problem: When the caret sat after a block decorator inside an element whose DOM slot has a before boundary, the block cursor got appended after the slot's trailing decoration, outside the range the editor manages (#9680).
• What I did: Changed $updateDOMBlockCursorElement to insert the cursor before slot.before, falling back to append when there is no boundary or it was detached. Added unit tests for both cases.
• Result: Merged by @etrepum. The new test fails before the fix and passes after, and the lexical, rich-text and selection unit suites stay green. Custom slot layouts now keep the cursor where the editor expects it.

• Problem: Kotlin 2 client generation always added _alias and _projection parameters to projection methods, so a GraphQL field with an argument of the same name produced duplicate parameters and failed to compile (#930).
• What I did: Renamed the generated alias and projection parameters only when they collide with a field argument, so existing schemas keep the same names. Added codegen tests that compile client queries using _alias and _projection arguments.
• Result: Merged by @iuliiasobolevska, who kept the commit and added a follow-up for related shadowing cases. Slated for the 8.8.1 release.

• Problem: The Python OpenAPI plugin checked allowed_base_urls with a raw path-prefix match, so /api/../admin and /api/%2e%2e/admin passed an /api allowlist. For the literal dot-segment path, httpx actually requested /admin (#14662).
• What I did: Checked the prefix after dot-segment normalization in both raw and percent-decoded forms, preserving internal empty segments to match httpx. Added tests for the escapes and for paths that must still pass, like /api/./users and /api/.
• Result: Merged by @eavanvalkenburg. The tested dot-segment escapes are rejected by the OpenAPI URL allowlist, and /apiusers is still rejected.

• Problem: On Windows, the postgres-mcp-server PG-wire path broke because psycopg's async mode does not support the default Proactor event loop (#4825).
• What I did: Set WindowsSelectorEventLoopPolicy at the start of the server entry point, before startup validation or MCP creates a loop, so other platforms keep their default. Added mocked tests for both the Windows and non-Windows paths.
• Result: Merged by @kennthhz. The PG-wire startup path now selects the Windows event-loop policy required by psycopg; mocked tests cover Windows and non-Windows policy selection.

• Problem: React Aria's ColorField ignored a parent Form's validationBehavior, unlike TextField and NumberField (#10862).
• What I did: Read FormContext through useSlottedContext and resolved the value as prop, then form, then 'native', matching the other fields. Added a regression test that validationBehavior="aria" gives aria-required without native required.
• Result: Merged by @devongovett. ColorField now inherits Form ARIA validation behavior, matching the existing TextField and NumberField pattern.

Conceptual patterns across separate projects; arrows do not assert one integrated deployment.

flowchart LR
  subgraph Client
    B[Browser<br/>Next.js · React]
  end
  subgraph Runtime
    WS[WebSocket agent server<br/>seq ordering · RESUME replay]
    API[FastAPI / Express gateway<br/>rate limits · RLS · circuit breaker]
  end
  subgraph Models_Tools_Data["Models · Tools · Data"]
    OR[OpenRouter / Workers AI<br/>project-specific routing]
    MCP[MCP servers · tool calling]
    VAD[WebRTC VAD · speech]
    RAG[BM25 / TF-IDF retrieval<br/>eval gates]
  end
  subgraph Ops
    CI[GitHub Actions CI<br/>F1 gates · offline eval]
    DEP[Docker · Cloudflare · GitHub Pages]
  end
  B <--> WS
  B --> API
  WS --> MCP
  API --> OR
  API --> RAG
  B --> VAD
  MCP --> OR
  CI --> DEP

The card lists tools I use or explore. The manifests below verify declared dependencies in these repos, rather than installed versions or live deployment.

Engineering principles

• Measure everything; ship the gate with the number
• Local-first whenever possible; CI must not depend on a live API
• Reliability over novelty — an agent with guardrails beats a flashier one without
• AI should augment, not obscure, the system
• Developer experience matters; simple systems scale better

Details: INTERVIEW_NOTES.md

Writing

• Technical writings RSS

Trajectory

Contribution graph · yearly snapshot JSON