Event-Sourcing

Table of Contents Introduction Project Overview Recent Development Iterations Key Features & Improvements Challenges & Solutions Collaboration in Practice Mermaid Diagram: Secure Service Architecture Future Plans Conclusion Introduction Welcome to another behind-the-scenes look at the Scores project! In this post, Claude (the tool), Caroline (the AI coding assistant), and Stef Hock (the human developer) share how collaboration, creativity, and continuous improvement have shaped the latest development cycle. Our journey is guided by care, challenge, and a relentless drive to make Scores more secure, scalable, and innovative. ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents The Challenge: When Metrics Evolve The Why: Statistical Integrity Over Time The What: Snapshot-Based Versioning The How: Implementation Journey Database Migrations Domain Model Evolution Match Lifecycle Integration Projection Layer Updates API Enhancements Collaboration in Action The Results: What We Achieved Looking Forward The Challenge: When Metrics Evolve Imagine this scenario: You’ve carefully tuned your player statistics algorithms, assigning specific weights to different shot types—smashes get higher offensive weights, delicate chiquitas favor precision metrics. Six months later, after analyzing thousands of matches, you realize that smash weights should be adjusted from 1.0 to 0.95 to better reflect actual game dynamics. ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents Introduction The Challenge: Mixed Responsibilities Phase 0: Architectural Cleanup Phase 1: Static Imports and Consolidation Building the Projections Layer Achievements and ROI What’s Next Introduction Over the past few weeks, Caroline (our AI assistant) and I have been working on a significant architectural improvement to the Scores project - implementing a Dynamic Query Registry with proper separation between transactional and analytical concerns. This wasn’t just a refactoring exercise; it was a fundamental rethinking of how we handle queries in an event-sourced, CQRS-based system. ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents The Mixin Composition Challenge Why Mixins for Event Sourcing Building WithShots: Shot Tracking Building WithTiming: Match Events The Event Ordering Problem Testing Strategy with node:test Testing Individual Mixins Testing Composition Data-Driven Testing with Scenarios Key Learnings The Mixin Composition Challenge When Caroline, Claude, and I refactored our Match aggregate to use the Repository pattern, we wanted to separate concerns using TypeScript mixins. The aggregate needed to: ...

Disclaimer: This blog post is automatically generated from project documentation and technical proposals using AI assistance. The content represents our development journey and architectural decisions. Code examples are simplified illustrations and may not reflect the exact production implementation. Table of Contents About This Blog The Team The Project What We’re Building Recent Development Iterations What’s Next About This Blog Welcome to “Claude, Caroline and Me” - a development blog documenting the journey of building a modern real-time scoring system for padel matches. This blog captures the iterations, challenges, and solutions as we work together to create something functional and scalable. ...