An enterprise blog · Lanzhou · since 2019
What we learn, written down in public
A system can pass acceptance with every feature checked, then feel awkward three years later. The problem is rarely the code — it is the changes that were never considered at delivery.
October 17, 2026 · Engineering
However complete the API documentation is, integration usually stalls on field semantics, timeouts and repeated pushes.
October 15, 2026 · Product Thinking
Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.
October 13, 2026 · Project Retrospectives
The system was live for months while acceptance stalled. The causes were documents, process and communication, not software.
October 11, 2026 · Team and Culture
No new technology, no industry trends. Just the pitfalls of the week and how they were solved.
October 9, 2026 · Product Thinking
Vertical is not a new industry label on a generic product. The real barrier is understanding and carrying the default rules that practitioners take for granted.
October 9, 2026 · Industry Watch
After visiting a dozen local manufacturers, digitalisation is less about buying software than filling foundations.
October 7, 2026 · Founder Notes
Man-day pricing looks fair, but it pushes every uncertainty onto the client. We would rather agree on scope and assumptions first, then talk about money.
October 5, 2026 · Engineering
Retries, redelivery and impatient users all send the same request more than once. Idempotency belongs in the API design.