Best Practices¶

Notes on how systems behave in the wild: trade-offs, failure modes, and the parts of operations that survive contact with production.

These pages answer why and when more often than follow these steps in order. Code shows up when it clarifies a pattern — the point is judgment, not a runbook.

Start here¶

• Geospatial system architecture
• Failure-oriented system design
• System resilience and concurrency
• PostGIS patterns
• Parquet and GeoParquet · GeoParquet

Languages and runtimes¶

• Python
• Rust
• Go
• R

Data and platforms¶

• Database and data management
• PostgreSQL
• Machine learning and AI
• Docker and infrastructure
• Git and version control

Architecture and operations¶

• Architecture and design
• Operations and monitoring
• Data governance
• Security

Embedded and home lab¶

• ESP32 and embedded
• Power electronics
• Home automation

Diagrams¶

• Systems diagramming
• Mermaid → SVG workflow

Creative reference¶

• Creative and fun patterns — idempotency, Celery notes, and similar (not the same as Just for Fun tutorials)

Pick a section that matches the problem; cross-links inside each guide point to tutorials when you need a hands-on walkthrough.