- Entry date
- 1 August 2025
- Category
- Tooling
- Access
- 🔓 Public
Twenty-four versions of a working .NET system, kept alive on purpose — proof that competent stewardship is sometimes the harder, better call than a rewrite.
- v24
- current production version
- .NET Framework + Entity Framework 6.2
- stack maintained across years, not rewritten
Honest evaluation
Twenty-four versions in active production is real, measured evidence for the stewardship claim; no modernisation-roadmap claim is made or implied.
What would prove or disprove it further
What would prove or disprove it further: the point where the cost of staying finally exceeds the cost of migrating — a feature the current architecture genuinely can't absorb, or a dependency that stops being supportable — would be the real test of whether stewardship remains the right call indefinitely, or just for the twenty-four versions so far.
The evidence — full reasoning behind the verdict
Verdict: proven. The claim was narrow and specific: that competent long-term stewardship of a working system is itself a real, demonstrable capability, sometimes the correct call over a rewrite. Twenty-four versions of active, maintained production software — new report formats, new validation rules, new payment paths, all absorbed without a framework change — is a real, measured track record for that claim, not an argument by assertion.
The mechanism is straightforward: a rewrite has real costs (risk, downtime, retraining users on new UI) that have to be weighed against the cost of staying on a working stack, and for this system staying has won the argument for two dozen versions running. That's not a claim that the stack is modern or that a rewrite is coming — the report is explicit that no modernisation roadmap is being claimed — it's a claim that the system has been kept genuinely well-maintained, which is a different and narrower thing than "not old."
Not every entry in this archive is about the newest stack. This one is about the opposite skill — keeping a working system working, version after version, across a tech-stack generation.
What it was
A car-park management system: season passes, validation cards, parking levels, and payment tracking, now at version 24 of a product that has been running and evolving for years.
What we built
Shipped & measuredA working production system on .NET Framework (Windows Forms), Entity Framework 6.2, SQL Server, and Report Viewer. No rewrite, no framework churn — the same architectural family carried forward and extended across two dozen versions as requirements changed: new report formats, new validation rules, new payment paths.
What we learned — including the honest negative
The lesson here runs against the grain of most of this portfolio, which is full of new stacks and rapid iteration. Not everything needs to become a React app. A tech-stack decision made years ago, kept working and well-maintained, is sometimes the right call over a rewrite — the cost of a rewrite (risk, downtime, retraining users on new UI) has to be weighed against the cost of staying, and staying won here for two dozen versions running.
The honest edge to name plainly: this report doesn't claim a modernisation roadmap or an eventual rewrite is coming. The claim is narrower and, we think, more useful — that long-term stewardship of a working system is itself a real, demonstrable capability, not a consolation prize next to building something new.
Where it went / status
In active production, at version 24, still being maintained. It sits next to the newer, fully modern parking-adjacent work built the same year as a deliberate contrast in the record: two different right answers to two different situations.
What is still open — kept visible
The honest edges, next to the wins. This is what turns 🔬 into 🟢 — honestly.
- An older stack kept alive by deliberate choice, not neglect — "not modern" and "not maintained well" are different claims, and only the first is true here.
- No modernisation-roadmap claim is made in this report; the value shown is sustained working software, not a migration story.
Sources
- vocabotics project audit — Car-park Management System (v24, .NET/Entity Framework), Aug 2025vocabotics internal project history · as of August 2025