July 9, 2026 · Project Retrospectives
Retrospective: The Cascade Behind One Change
Splitting 'customer' into enterprise and individual looked like one field. It touched six modules.
An enterprise blog · Lanzhou · since 2019
What we learn, written down in public
July 9, 2026 · Project Retrospectives
Splitting 'customer' into enterprise and individual looked like one field. It touched six modules.
June 27, 2026 · Project Retrospectives
The system was finished and the client said it was not what they wanted. Every argument returned to one line: it was never specified.
June 15, 2026 · Project Retrospectives
The system went down at nine on a Monday morning because one connection was never closed.
June 3, 2026 · Project Retrospectives
A partner upgraded their API, the response shape shifted quietly, and our system broke two weeks later.
May 22, 2026 · Project Retrospectives
The first run errored, the second disagreed on totals, the third passed. Each failure exposed a different problem.
May 10, 2026 · Project Retrospectives
The core developer left and the successor spent a month before daring to change a line.
April 28, 2026 · Project Retrospectives
The vendor said nearly done every week, until a week before delivery revealed half the work was missing.
April 16, 2026 · Project Retrospectives
One unrelated change brought back a bug fixed three months earlier.
April 4, 2026 · Project Retrospectives
The campaign page was load-tested, but login and coupons were what fell over.