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
An agent can get most of a long task done and still miss something important, and I think integrations need the same split between the job finishing and the records actually being right.
A conversational assessment still needs deterministic scoring
Let the conversation collect the evidence and let a versioned rule set do the scoring, so a reviewer can rerun the result and get the same answer.
2025
One bulk query can beat thousands of careful loops
I've been working through data pipelines where perfectly reasonable queries add up to unreasonable runtimes. Moving the work into bulk operations helps a lot, but a bad bulk update can damage far more records before anyone notices, 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 looks objective, but there's usually a changing set of weights, thresholds and assumptions behind it. I want the rule version stored with every result so someone can reproduce it, explain it and tell whether the answer changed or the evidence did.
Long-running data jobs should be designed to stop
Big imports rarely fail at a convenient point. They need deliberate stopping points, a record of what's finished and a restart path that doesn't duplicate work that's already been accepted.
2024
Dates, dashboards and the work that has not processed
A dashboard can look current while timezone assumptions or a hidden row limit say otherwise. I'm putting unprocessed records, date rules and result limits on the screen, because people running operations need to see incomplete work before a customer complaint tells them about it.
Accounting integrations need explicit sync state
An accounting integration gets hard to support once the app can't say whether a record is waiting, synced, rejected or changed afterwards. I'm making sync state visible so retries and reconciliation have something to go on, and staff don't have to compare two systems by hand.