Case 01/Ness Digital Engineering Czech/Current engagement

A shared data architecture for complex regulatory workflows

Replacing duplicated form logic with a typed connection layer for a large, multi-module internal application.

Context

A greenfield regulatory application replacing part of a legacy system while adding new capabilities. Its many forms share complex data, validation, and related-entity rules that must remain consistent as the product grows.

My contribution

  • 01Design and implement a generic, typed connection contract between BFF models and frontend form state.
  • 02Build substantial form workflows alongside shared layouts, tables, search, validation, and API integration.
  • 03Co-author shared layout primitives and utilities, align implementation with UX, and support other frontend contributors as they adopt common patterns.

Decisions that shaped the work

  • 01Centralize mapping, dirty-state resolution, and full or partial serialization instead of repeating them inside every form.
  • 02Represent related-entity additions, updates, and removals explicitly so editing sends only the data that changed.
  • 03Introduce parity and descriptor-coverage tests to verify migrated mappings and prevent fields from being silently omitted.

Outcome & status

The connection layer became the default pattern across the application's forms, removing repeated mapping code and reducing the risk of incorrect update payloads. The product remains under active development; client-sensitive workflow details are intentionally omitted.