FastAPI production best practices — domain-organized project structure, async correctness, DI patterns with per-request caching and chaining, Pydantic v2 split create/update/response models, Pydantic Settings v2, async testing with httpx.AsyncClient.
Git workflow best practices — Git Flow branch prefixes, Conventional Commits format, atomic commits with imperative mood, pre-commit hygiene, pull --rebase before push, no force-push to shared branches, max 400 LOC per PR, squash on merge for clean main history.
Engineering rules for building an interactive (online) gaming platform that can pass a GLI-19 technical certification — server-authoritative game outcomes with no game logic on the client, one authoritative system clock, the records a gaming system must maintain (per-game play record, per-theme aggregates with…
Security-engineering rules for an interactive gaming platform under the GLI Gaming Security Framework (GLI-GSF-1) — the deep security-controls layer beneath GLI-19's technical-security appendix, owning the infrastructure and network security territory (DNS, firewalls, remote access, hardening, segmentation, IDS/IPS…
Python gRPC async-first Kubernetes-native best practices using grpc.aio — server bootstrap with graceful shutdown, shared per-process channel factory, canonical decorator pattern for cross-cutting concerns, maxconnectionage for HPA rebalancing, client-side LB via dns:/// + roundrobin over a headless Service (no se.
Engineering best practices for money / payments / ledger systems — Decimal or integer minor units (never float), the two-layer idempotency model (client-driven idempotencykey + chain-CAS for state transitions, never conflated), double-entry ledger architecture (Accounts + Transfers, debit=credit invariant at DB level.
Python observability best practices using OpenTelemetry — SDK bootstrap with off-switch contract and idempotency guard, auto-instrumentation (gRPC / SQLAlchemy / FastAPI / Logging), the LoggingInstrumentor + structlog correlation pattern with custom log hook and CleanLoggingHandler, two-tier log field taxonomy, span…
pytest async-first testing best practices — test layer structure, fixture design, async testing with pytest-asyncio, test data with factoryboy + faker, HTTP mocking with respx, time mocking with freezegun, property-based testing with hypothesis, DB transaction-rollback isolation, flush() pattern for chained fixtures.