Delivery and QA
Architecture, production readiness and quality practices for software that must keep working.
- Blog posts
- 33
- Focused clusters
- 02
Focused clusters
Start with the cornerstone
- Smart City Architecture Best Practices: MQTT, LoRaWAN, Kubernetes and TerraformA vendor-neutral guide to building smart-city platforms that survive production: MQTT at the edge, LoRaWAN and ChirpStack for private sensor networks, FIWARE/NGSI-LD and SensorThings for interoperability, Terraform for repeatable infrastructure, and Kubernetes only when the team can operate it.
- QA for AI-Generated CodeA risk-based verification guide for AI-assisted code, covering trust boundaries, failure paths, dependencies, concurrency, operational evidence, and the limits of any review.
Get the next Delivery and QA field note
One concise email when we publish. No tracking pixels, and no inbox filler.
Latest in this collection
Delivery & QAEU Battery Passport Software Architecture for 2027
Turn the 18 February 2027 deadline into a buildable identity, data, access, QR, and lifecycle architecture.
Delivery & QAEU Data Act: Connected-Product API Checklist
Prepare the Article 3 access-by-design duty for products placed on the market after 12 September 2026, while the Data Act already applies generally.
Delivery & QACursor Origin vs GitHub: Should Your Team Switch?
Cursor now hosts code, but Origin is still an early beta. Compare sync behavior, CI, governance, price and a low-risk pilot before moving your source of truth.
Delivery & QAMoneyPrinterTurbo Review 2026: Free AI Video, Real Costs
MoneyPrinterTurbo turns a topic into a narrated short, but free code is only the start. See its setup, hidden costs, licensing, platform risk and production fit.
Delivery & QAOdoo API integration: the five limits that decide your architecture
Odoo Cloud treats one call per second as acceptable use, every JSON-2 call is its own transaction, and XML-RPC has a removal date. What that forces on an integration.
Delivery & QAAI in Grocery Retail: An MPREIS Opportunity Map
An independent outside-in analysis of demand forecasting, fresh-food workflows, the customer app and a pragmatic 90-day validation path for grocery retail.
Complete article directory
- EU Battery Passport Software Architecture for 2027
- EU Data Act: Connected-Product API Checklist
- Cursor Origin vs GitHub: Should Your Team Switch?
- MoneyPrinterTurbo Review 2026: Free AI Video, Real Costs
- Odoo API integration: the five limits that decide your architecture
- AI in Grocery Retail: An MPREIS Opportunity Map
- Stateful LLM Platform Production Architecture
- Tirol Kliniken (TILAK): A Digital Operations Opportunity Map
- TIWAG Digital Energy: A Software and AI Opportunity Map
- AI 3D Model Generators for Game Development: 2026 Guide
- Fintech Architecture Remediation Without a Rewrite
- Agentic Testing vs Test Automation: 2026 Pilot Guide
- Tampermonkey Workflow Automation
- Will AI Kill Cross-Platform Frameworks?
- Floci vs LocalStack: AWS Emulator Review for CI in 2026
- Git Worktrees vs Jujutsu for AI Coding Agents: 2026 Decision Guide
- External QA Benchmark: What We Find in the First 30 Days
- Programming Languages Matter Less. Software Engineering Matters More.
- The Future of Enterprise Software
- What Software Maintenance Costs After Launch: A DACH SaaS Benchmark
- Smart City Architecture Best Practices: MQTT, LoRaWAN, Kubernetes and Terraform
- The Factory Returns
- Agile De-engineering
- Lovable, Bolt, and Replit App Due Diligence
- The Vibe-Code Production-Readiness Checklist
- What It Costs to Make a Vibe-Coded App Production-Ready
- QA for AI-Generated Code
- From Lovable and Cursor Prototype to Production: The Migration Checklist
- Vibe-Coded Software Audit: What to Check Before Launch
- React Native vs Flutter for DACH Hiring in 2026
- LoRaWAN vs NB-IoT vs Sigfox: Budget an IoT Pilot
- Software Is a Living Product
- What Test-Driven Development Can and Cannot Prove