Software & Systems blogs
Featured blogs
Generated image: Villar David editorial
Blogs
Software & Systems
Posts filed under Software & Systems. View every category.
2026
Checking an integration after the job says it finished
A long agent run can complete most of its work and still miss an important requirement. I want the same distinction in production integrations: a completed run and a verified result are separate facts.
A conversational assessment still needs deterministic scoring
Keep the conversation and the scoring engine separate. The conversation captures evidence; a versioned rule set calculates the result and leaves a reviewer able to reproduce it.
2025
One bulk query can beat thousands of careful loops
I have been working through data pipelines where individually reasonable queries create unreasonable runtimes at scale. Moving the work into bulk operations changes throughput dramatically. A bad bulk update can damage far more records before anyone sees it, so the job needs a dry run, checkpoints and a way to reconcile the result.
If software produces a score, the rules need a version
A score can look objective while hiding a changing set of weights, thresholds and assumptions. I want the rule set versioned alongside the result so a reviewer can reproduce what happened, explain it to the person affected and distinguish a changed answer from changed evidence.
Long-running data jobs should be designed to stop
Large imports rarely fail at a convenient boundary. They need deliberate stopping points, a record of what completed and a restart path that does not duplicate accepted work.
2024
Dates, dashboards and the work that has not processed
A dashboard can look current while timezone assumptions or hidden processing limits tell a different story. I am putting unprocessed records, date rules and result limits into the interface because operational users need to see incomplete work rather than discover it through a customer complaint.
Accounting integrations need explicit sync state
An integration becomes difficult to support when the application cannot say whether a record is waiting, synced, rejected or changed afterwards. I am making sync state visible so retries and reconciliation have evidence and staff do not have to compare two systems by hand.