A command model gives human operators, human builders, coding agents, and operating agents a shared language for work. The First Command Exposes The Real Design Problem Suppose we are building a package that validates datasets before they enter a modeling pipeline. The first version sounds small. It should read a file, apply a collection of rules, report any violations, and optionally write a machine-readable result for a later pipeline stage. ...
Coding agents can reason over code, but the retrieval tools in the loop need a deterministic map of the repository before that reasoning becomes reliable. The Agent Looked Competent Until The Repository Got Real Picture a team asking a coding agent to make a small change to a shared data contract. The task sounds ordinary. Add one validation rule, update the code path that consumes the field, make sure the tests still cover the behavior, and keep the downstream tools stable. The repository is not exotic. It has a Python package, a Rust worker, a small CLI, a Kotlin client, a few notebooks used by the ML team, some generated code, a coverage report, and enough Git history that certain files have clearly learned to change together. ...
Risk-adjustment software earns trust when it preserves enough of the scoring path for another person, or another tool, to inspect it. A Risk Score Is The End Of A Longer Path A risk-adjustment run rarely ends with the person who wrote the scoring command. An analytics team receives a subject file and a diagnosis file for a new reporting cycle. The data may come from claims, eligibility records, internal extracts, or a prepared research dataset. Someone runs the scoring workflow and produces a table of subject-level risk scores. The file is useful. It may feed a quality model, a review queue, a payment analysis, a monitoring dashboard, or an internal validation package. ...
After several months of agentic development, I found that generated code was abundant while confidence in the generated system stayed scarce. The Review Started To Matter More Than The Patch Picture the end of an agent-assisted coding session. The terminal says the tests pass. The agent has summarized the change with the usual confidence. A new module exists, the examples run, and the diff is larger than anything I would have written by hand in one sitting. I still have to read it. ...
After years of searching for stronger guarantees in exploratory numerical and ML programming. A small experimental function rarely announces when it has become infrastructure. It starts as a quick helper. Maybe I am inspecting a set of model outputs, adjusting an NLP evaluation script, or testing a statistical transformation that may not survive the afternoon. The function takes a dataframe, filters a cohort, normalizes a score, applies a threshold, returns a small artifact, and gives me enough signal to keep moving. ...
How Haskell confused me, Rust prepared me, F# made the idea click, and Python made me build the missing piece for data and ML workflows. A nightly feature pipeline fails while we are sleeping. Imagine a common failure case. A source table arrived late. One column has a new nullable value. A model metadata file is missing the training window. The pipeline is supposed to handle these cases because they are ordinary failures in data work. They are not developer mistakes in the same category as an index error or a broken invariant. ...
The practical question is where your hot path lives: in Python code, native libraries, or custom stateful logic. The Rewrite Question Usually Starts Too Late Suppose a data pipeline is slower than you want. It reads a few million rows, computes some derived columns, joins a dimension table, aggregates by user segment, and then runs a small amount of business logic over events. The code is in Python. Someone on the team has been learning Rust. The suggestion comes up quickly: maybe this should be rewritten. ...
A working hypothesis from repeated coding agents use: FP-style structure seems to make non-FP codebases easier for coding agents to understand, change, and verify. The Missing Variable In Agentic Coding Picture a Monday-morning task in a Python or TypeScript service. The request looks ordinary: add a validation rule, thread one more field through a pipeline, keep the old API stable, update the tests, and do not break the nightly job. You hand the task to a coding agent. In one repository the run feels clumsy. The agent reads too much, edits the wrong layer first, and produces a patch that looks plausible until you notice the missed edge case. In another repository the same class of task goes much better. The agent locks onto the relevant types, updates a few focused functions, adjusts the tests, and lands in the right area with much less wandering. ...
A TF-IDF vignette for designing around data flow, types, and contracts before code. In my November 9, 2025 post, Functional Programming in Python, I argued that FP is less about adopting a pure functional language and more about adopting a different engineering discipline. The core habits were simple: think in expressions, prefer immutability, isolate side effects, and model your domain explicitly. That line of argument tends to invite a practical question. If a team gives you a vaguely defined task on Monday morning, where does the work begin, and what does “FP-style” look like before the code exists? ...
Coding agents can write code, but reliable multi-step work depends on the harness around the model. Source: r/ClaudeCode The agent looked competent until the workflow got longer Picture a small infrastructure team trying to standardize how it uses a coding agent across a growing repository. At first the experience is encouraging. Someone asks the agent to add a CLI flag, wire a metrics endpoint, update a test, and explain the change. The answer is fast, the patch is plausible, and the team starts to feel that a large part of everyday engineering has become compressible. ...