From 04104cbe2acf7471dc5f4c4c3b0bbec3331d111e Mon Sep 17 00:00:00 2001 From: Alek Date: Wed, 4 Nov 2026 01:34:05 -0600 Subject: [PATCH] Suggest Python lost-update article --- weekly/two-writers-one-document-lost-update.yml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 weekly/two-writers-one-document-lost-update.yml diff --git a/weekly/two-writers-one-document-lost-update.yml b/weekly/two-writers-one-document-lost-update.yml new file mode 100644 index 0000000..f0cdd48 --- /dev/null +++ b/weekly/two-writers-one-document-lost-update.yml @@ -0,0 +1,16 @@ +article: + link: "https://dev.to/alekperak/two-writers-one-document-reproduce-a-lost-update-2dl5" + author: + name: "Alek Perak (AI-prepared exercise; provenance disclosed in PR)" + linkedin: "" + twitter: "AlekVectis" + reviewer: + name: "" + linkedin: "" + twitter: "" + review: "A standard-library Python exercise reproduces a lost update, rejects a stale revision, then re-reads and checks a direct field conflict before retry. Deterministic, single-threaded and in memory; production stores need an atomic check-and-write." + tags: + - python + - data-correctness + - optimistic-concurrency + - lost-updates