Skip to content

Ball Lightning AB
Portfolio & archive

Software, integrations, and digital projects by Nicolas Brulay. Maintained as a company presence, portfolio, and home for selected non-competing side projects.

Activity
Contribution GraphMarAprMayJun
242 activities/4 months
Less0 contributions1 contributions2 contributions3 contributions4 contributionsMore
Nicolas Brulay

Nicolas Brulay

Founder, Ball Lightning AB

I am a project manager and full-stack developer with shipped work across MMOs, clinic websites, enterprise data systems, blockchain integrations, and integration-heavy product delivery. I work full-time at Hultafors Group as Product & Service Owner - Integrations. My focus is integration ownership: modernization, harmonization, strategy, AI, automation and the technical shape of how integration capabilities evolve over time. Ball Lightning AB remains maintained as a company presence, portfolio and archive for selected previous work, but I am not currently accepting new client engagements through it.

Recent notes from The Builder Coil

Occasional hobby, learning, and technical notes

BlogApr 22, 2026
Browser Smoke Suite: Cost-Efficient Route Validation for Shipping API Dojo v2

Issue #17 added a minimal Playwright smoke suite to complement unit/integration coverage. I built a cost-efficient browser test layer for checkpoint validation and future mirror sites.

Read: Browser Smoke Suite: Cost-Efficient Route Validation for Shipping API Dojo v2
BlogApr 21, 2026
Proof of Concept: Validating Seeded Randomization and Content Families in Shipping API Dojo v2

Issue #8 implemented a proof of concept for minimum viable randomization and content families. I validated MCQ shuffling, lesson drill ordering, scenario sequencing, and SSR-safe behavior under TanStack Start.

Read: Proof of Concept: Validating Seeded Randomization and Content Families in Shipping API Dojo v2
BlogApr 16, 2026
Technical Scoping: How Shipping API Dojo v2 Designed Its Content-Family Foundation

Before building Shipping API Dojo v2, I needed a complete technical blueprint. I scoped content families, seeded randomization, auth/billing/email/domain strategy, and the decisions that shaped the architecture.

Read: Technical Scoping: How Shipping API Dojo v2 Designed Its Content-Family Foundation