How I work with JSON
summary
Argues that JSON itself is simple and the hard part is mapping to domain models, so prefer JSON DTOs (typed property bags using only JSON-native types and arrays, no DateTime) and minimal, explicit mapping over magic serializers; keep serializer settings simple (Newtonsoft or System.Text.Json only as plain serializers). Advocate handwritten contracts using JSON Schema / OpenAPI / AsyncAPI, validate messages at boundaries, and use quibble for JSON-aware comparisons in .NET rather than string diffs or reverse-engineered docs.
AI-written summary · about
chapters (7)
- 0:00Start
- 6:42PERFORMANCE?
- 14:25PURE SERIALIZATION
- 16:08ARBITRARY MAPPING
- 17:26AUTOMAGIC MAPPING
- 21:15MINIMAL MAPPING
- 30:40COMMUNICATION
related talks
01h 02mDesigning Wonderful .NET APIs
19mModern JSON Handling in a Macro-less Flutter Era
20mFalling in love with json
04mLightning Talk JSON Schema
25mFull-stack forms with JSON Schemas
56mDTO: Live Fast, Burn Bright
31mUnifying OpenAPI & AsyncAPI : Designing JSON Schemas+Examples.
27mBuilding Great Web APIs
