{ "schema": "https://mosthofaimran.com/schema/papers/1", "license": "https://creativecommons.org/licenses/by/4.0/", "note": "If you quote a claim, carry its confidence value with it. A 0.60 claim repeated as fact is no longer the author’s claim.", "count": 14, "papers": [ { "section": "5.1", "slug": "competence-porn", "identifier": "draft-imran-competence-porn-04", "title": "Competence Porn", "summary": "Watching a skilled person work occupies the same reward slot as being one, and the industry has industrialised the confusion.", "url": "https://mosthofaimran.com/papers/competence-porn/", "markdown": "https://mosthofaimran.com/papers/competence-porn.md", "state": "holding", "confidence": 0.8, "published": "2025-09-03", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A longitudinal study showing heavy consumers of technical content outperform matched peers on blind, time-boxed debugging tasks.", "Evidence the effect is generational rather than structural, appearing at equal rate in cohorts who entered the field before ranked feeds existed.", "A large publisher of technical content disclosing what fraction of the architectures it demonstrated reached production and survived twelve months, where that fraction is high." ], "retraction": null }, { "section": "5.2", "slug": "vibe-coding", "identifier": "draft-imran-vibe-coding-01", "title": "Vibe Coding and the IKEA Effect", "summary": "Assembly feels like understanding. It is not the same feeling twice.", "url": "https://mosthofaimran.com/papers/vibe-coding/", "markdown": "https://mosthofaimran.com/papers/vibe-coding.md", "state": "holding", "confidence": 0.75, "published": "2026-05-02", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A blind study in which engineers who assembled a system without reading its generated internals diagnose induced faults in it at the same rate and speed as engineers who wrote the equivalent system by hand.", "Evidence that the confidence gap in Section 3 closes with tooling rather than with reading, for example a generation workflow whose users predict failure modes as accurately as authors do.", "A demonstration that the effect is about ownership rather than comprehension, appearing at equal strength for code the engineer merely selected rather than assembled, which would make this a paper about a different mechanism." ], "retraction": null }, { "section": "5.3", "slug": "algorithmic-homophily", "identifier": "draft-imran-algorithmic-homophily-02", "title": "Algorithmic Homophily", "summary": "Your timeline is a cache with no invalidation policy. It returns the priors you arrived with, warmed.", "url": "https://mosthofaimran.com/papers/algorithmic-homophily/", "markdown": "https://mosthofaimran.com/papers/algorithmic-homophily.md", "state": "revising", "confidence": 0.6, "published": "2026-01-12", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A demonstration that technical opinion measured inside a subscription-shaped medium is no less varied than opinion measured outside it, on the same population and the same question, which would remove the effect this paper is about rather than its explanation.", "Evidence that deliberate exposure to disagreement, as described in Section 5, produces no measurable change in the accuracy of technical forecasts, which would leave the paper describing something real and useless.", "A mechanism that accounts for the private mailing list result in erratum 7.1 and predicts that ranking is nonetheless the dominant term, which would restore the original claim rather than the narrowed one." ], "retraction": null }, { "section": "5.4", "slug": "easy-button-tax", "identifier": "draft-imran-easy-button-tax-01", "title": "The Easy Button Tax", "summary": "Removed friction is relocated friction, and the invoice arrives during the incident.", "url": "https://mosthofaimran.com/papers/easy-button-tax/", "markdown": "https://mosthofaimran.com/papers/easy-button-tax.md", "state": "holding", "confidence": 0.85, "published": "2026-04-20", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A widely adopted abstraction that removed a class of friction and whose failure modes are demonstrably cheaper to diagnose than the friction it replaced, measured in operator time during incidents rather than in developer time during authoring.", "Evidence that the cost transfer described in Section 2 does not occur where the author and the operator are the same team, which would reduce this to an argument about organisational structure rather than about abstraction.", "A convenience layer shipping with an escape hatch that is exercised in its own test suite as a first-class path, adopted at scale, showing that the tax is a choice rather than a property." ], "retraction": null }, { "section": "5.5", "slug": "on-prem", "identifier": "draft-imran-on-prem-01", "title": "On-Premise Is Not a Downgrade", "summary": "Sovereignty as an architectural constraint, not a punishment.", "url": "https://mosthofaimran.com/papers/on-prem/", "markdown": "https://mosthofaimran.com/papers/on-prem.md", "state": "holding", "confidence": 0.9, "published": "2026-03-19", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A team that adopted the single-artifact discipline at design time and can show, over two years, that it consumed more total engineering hours than maintaining separate cloud and on-premise builds.", "Regulated estates routinely permitting outbound connections to vendor control planes, which would make the assumption list in Section 2 historical rather than current.", "A cloud-only system of comparable complexity demonstrating equivalent dependency hygiene, reproducibility and upgrade safety without any sovereignty constraint forcing it." ], "retraction": null }, { "section": "5.6", "slug": "retry-storm", "identifier": "draft-imran-retry-storm-01", "title": "The Retry Storm You Built On Purpose", "summary": "Backoff without jitter synchronises your clients into a distributed metronome.", "url": "https://mosthofaimran.com/papers/retry-storm/", "markdown": "https://mosthofaimran.com/papers/retry-storm.md", "state": "holding", "confidence": 0.95, "published": "2026-07-28", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A fleet of a thousand or more clients running deterministic exponential backoff with no jitter and no retry budget, surviving a sixty second dependency outage with no correlated arrival spike, measured at the dependency rather than at the client.", "Evidence that the default settings of the major client libraries now ship full jitter and a caller-side budget, which would make this a paper about a solved problem rather than a live one.", "A queueing analysis showing that at realistic client counts the benefit of jitter is dominated by other recovery effects, so that removing it changes nothing measurable." ], "retraction": null }, { "section": "5.7", "slug": "chestertons-fence", "identifier": "draft-imran-chestertons-fence-01", "title": "Chesterton's Fence Has a Git Blame", "summary": "Read the commit message before you delete the guard clause.", "url": "https://mosthofaimran.com/papers/chestertons-fence/", "markdown": "https://mosthofaimran.com/papers/chestertons-fence.md", "state": "holding", "confidence": 0.8, "published": "2026-02-14", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A codebase of substantial age where the instrument-then-remove procedure in Section 4 produced no measurable reduction in regressions from cleanup work, compared against a matched period of direct deletion.", "Evidence that guard clauses whose recorded reason has decayed are, in aggregate, no more likely to be load-bearing than newly written ones, which would make the caution in this paper an expensive superstition.", "Tooling that reliably reconstructs the intent behind a change from the surrounding artefacts, at accuracy high enough that the decay ladder in Section 2 stops mattering." ], "retraction": null }, { "section": "5.8", "slug": "rag-search", "identifier": "draft-imran-rag-search-01", "title": "RAG Is a Search Problem in a Trench Coat", "summary": "The chunking strategy is doing more work than the embedding model.", "url": "https://mosthofaimran.com/papers/rag-search/", "markdown": "https://mosthofaimran.com/papers/rag-search.md", "state": "holding", "confidence": 0.7, "published": "2026-01-30", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A published evaluation on a realistic corpus in which swapping the embedding model, holding chunking, query construction and retrieval strategy fixed, produces a larger gain in answer accuracy than fixing chunking while holding the model fixed.", "Context windows and attention costs reaching a point where whole-corpus prompting is economically routine, which would remove the retrieval stage this paper is about rather than improve it.", "Evidence that retrieval recall of the answer-bearing passage is not the binding constraint in production systems, for example generation reliably recovering answers absent from the retrieved context." ], "retraction": null }, { "section": "5.9", "slug": "ship-of-theseus", "identifier": "draft-imran-ship-of-theseus-01", "title": "The Ship of Theseus Passes Its Integration Tests", "summary": "Strangler-fig migrations, and the moment nobody can name when the new system became itself.", "url": "https://mosthofaimran.com/papers/ship-of-theseus/", "markdown": "https://mosthofaimran.com/papers/ship-of-theseus.md", "state": "draft", "confidence": 0.55, "published": "2026-08-09", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A completed incremental migration of substantial size where no identity declaration was made, and where ownership, invariants and the decommissioning of the old path nonetheless resolved cleanly within a year of the last route moving.", "Evidence that end-to-end invariants are preserved by route-level verification in practice, which would remove the specific decay this paper is worried about.", "A demonstration that the residual old system is retired at similar rates whether or not a decommissioning date was declared in advance, which would make Section 4 ceremony." ], "retraction": null }, { "section": "5.10", "slug": "vector-db-fad", "identifier": "draft-imran-vector-db-fad-02", "title": "Vector Databases Are a Fad", "summary": "Withdrawn in full. See errata 7.2.", "url": "https://mosthofaimran.com/papers/vector-db-fad/", "markdown": "https://mosthofaimran.com/papers/vector-db-fad.md", "state": "retracted", "confidence": null, "published": "2025-05-20", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [], "retraction": { "date": "2025-11-14T00:00:00.000Z", "reason": "The central claim failed. Retrieval quality at scale turned out to depend on index properties the author had dismissed, and the operational story matured faster than predicted.", "erratum": "7.2" } }, { "section": "5.11", "slug": "postmortem-owes-you", "identifier": "draft-imran-postmortem-owes-you-01", "title": "What a Postmortem Owes You", "summary": "A document that names no decision is a weather report.", "url": "https://mosthofaimran.com/papers/postmortem-owes-you/", "markdown": "https://mosthofaimran.com/papers/postmortem-owes-you.md", "state": "holding", "confidence": 0.9, "published": "2025-12-02", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "An organisation publishing narrative-only postmortems, naming no decision and no owner, that nonetheless shows a falling rate of repeat incidents in the same subsystem over eighteen months.", "Evidence that requiring a named decision measurably suppresses incident reporting, so that the cost in disclosure exceeds the gain in correction.", "A study showing that action items with an owner and a verification date are completed at the same rate as those without, which would remove the mechanism this paper rests on." ], "retraction": null }, { "section": "5.12", "slug": "service-boundaries-org-chart", "identifier": "draft-imran-service-boundaries-org-chart-01", "title": "Your Service Boundaries Are an Org Chart", "summary": "Conway's law, observed in the wild across three reorganisations.", "url": "https://mosthofaimran.com/papers/service-boundaries-org-chart/", "markdown": "https://mosthofaimran.com/papers/service-boundaries-org-chart.md", "state": "holding", "confidence": 0.85, "published": "2025-09-18", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A system of comparable size whose service graph remained materially unchanged across a reporting-line reorganisation, sustained for four quarters, with no deliberate effort to hold the architecture in place.", "Evidence that distributed and asynchronous working has flattened the communication cost gradient enough that team boundaries no longer predict interface boundaries.", "A demonstration that the correlation runs the other way in practice, with organisations reliably reshaping their reporting lines to match an architecture chosen first, at a rate high enough to make the inverse manoeuvre in Section 4 the normal case rather than the rare one." ], "retraction": null }, { "section": "5.13", "slug": "dashboard-nobody-opens", "identifier": "draft-imran-dashboard-nobody-opens-01", "title": "The Dashboard Nobody Opens", "summary": "On observability that measures the system's health rather than the operator's question.", "url": "https://mosthofaimran.com/papers/dashboard-nobody-opens/", "markdown": "https://mosthofaimran.com/papers/dashboard-nobody-opens.md", "state": "holding", "confidence": 0.75, "published": "2025-06-05", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A team whose dashboards are built from emitted signals rather than from operator questions, and whose new on-call engineers nonetheless answer the five triage questions in Section 3 within ninety seconds, without assistance, on an incident they have not seen before.", "Evidence that question-driven dashboards measurably slow diagnosis of novel failure modes, so that the breadth they discard costs more than the speed they buy.", "Query-side tooling that makes ad-hoc exploration fast enough that pre-built views stop mattering, at which point this paper is about a tool generation rather than about a practice." ], "retraction": null }, { "section": "5.14", "slug": "kubernetes-for-a-bicycle", "identifier": "draft-imran-kubernetes-for-a-bicycle-01", "title": "Kubernetes for a Bicycle", "summary": "On matching operational weight to actual load, written after I got this wrong twice.", "url": "https://mosthofaimran.com/papers/kubernetes-for-a-bicycle/", "markdown": "https://mosthofaimran.com/papers/kubernetes-for-a-bicycle.md", "state": "holding", "confidence": 0.7, "published": "2025-03-11", "revised": "2026-08-14", "expires": "2027-02-15", "expired": false, "retires": [ "A team of five or fewer engineers, with no dedicated platform role, running a full orchestration stack for eighteen months while spending less total time on the platform than on the product, measured rather than recalled.", "Managed orchestration reaching a point where the fixed costs listed in Section 3 are genuinely absorbed by the provider, including upgrade cadence, network policy and on-call knowledge, at which point the break-even in Section 4 moves far enough to invert the advice.", "Evidence that starting simple and migrating later costs more in aggregate than starting heavy, which is the inverse of the assumption this paper rests on and the one I would most like to see tested." ], "retraction": null } ] }