Topic
How the system is designed
The design decisions the client feels in daily use: integrating with what already exists, keeping rules configurable, deciding every alert and protecting people who must not be identified.
The rule that changes every week does not belong in your code
Any change request that needs a deploy to swap a number, a deadline or a limit is an architecture decision that was made wrong earlier. In SheepGen, genetic interpretation became 1,103 rules registered as data, and a new marker recalculates all 735 flock reports in 4 minutes, with no developer in the loop. But parameterizing without a way to verify is worse than code: the same engine was validated against an independent implementation, with zero divergence across 55,050 readings.
16 min read
16 min read
Integrating with an ERP: what the other system decides for you
The architecture of an integration is not your choice: it is imposed by what the other system offers. Across three integrations we built — NextFit, Altimus and Controlle — the same question (what changed over there?) had three different answers, because the sources were different. And whatever the source does not provide becomes a limit on your product, not just a line of code.
15 min read
15 min read