[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-knowledge-base-habit-en":3,"blog-adjacent-knowledge-base-habit-en":30,"blog-related-knowledge-base-habit-en":66},{"id":4,"slug":5,"title":6,"excerpt":7,"content":8,"cover":9,"tone":10,"author":11,"publishedAt":12,"updatedAt":12,"readingMinutes":13,"featured":14,"tags":15,"category":19,"seoSettings":29},98,"knowledge-base-habit","A Knowledge Base Is a Habit","A knowledge base does not get used because it exists. It exists when every problem starts there.","\u003Cp>We bought several knowledge tools. The first two died and their open rates slid. The current one has stayed alive for three years, and the difference is habits, not software.\u003C\u002Fp>\n\u003Ch2>Make writing natural\u003C\u002Fh2>\n\u003Cp>When a search fails, the first step of solving is to create the document: conclusion first, details after.\u003C\u002Fp>\n\u003Cp>Documents may be rough. A single command or troubleshooting note is fine; prose is not required.\u003C\u002Fp>\n\u003Cp>Every meeting ends with the host writing decisions and actions into the right page within five minutes.\u003C\u002Fp>\n\u003Ch2>Make reading reliable\u003C\u002Fh2>\n\u003Cp>Every document has an owner. The page shows the last editor and date, and anything untouched for a year is flagged for verification.\u003C\u002Fp>\n\u003Cp>Decisions never live in comment threads. They go into documents; chat is reference only.\u003C\u002Fp>\n\u003Cp>One onboarding task is fixing outdated docs, announced in the group when done.\u003C\u002Fp>\n\u003Cp>A knowledge base lives or dies by usage. It earns the name only when every question starts there.\u003C\u002Fp>","","slate","佳益方圆团队","2026-06-25T10:57:00+08:00",1,false,[16,17,18],"Team Culture","Knowledge Management","Documentation",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},4,0,"team-culture","Team and Culture","Company events, tech sharing, team building and hiring culture that show the daily life of the Jiayifangyuan team.","users","blue","article",30,{},{"previous":31,"next":49},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":37,"updatedAt":37,"readingMinutes":13,"featured":14,"tags":38,"category":42},79,"acceptance-dispute-retro","Retrospective: The Cost of Vague Acceptance Criteria","The system was finished and the client said it was not what they wanted. Every argument returned to one line: it was never specified.","indigo","2026-06-27T10:57:00+08:00",[39,40,41],"Retrospective","Acceptance","Requirements",{"id":43,"parentId":21,"slug":44,"name":45,"description":46,"icon":47,"cover":9,"tone":26,"kind":27,"sortOrder":48,"count":21},3,"project-retrospective","Project Retrospectives","Real project records from zero to one, covering problems, solutions, lessons learned and final outcomes.","clipboard-check",40,{"id":50,"slug":51,"title":52,"excerpt":53,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":55,"updatedAt":55,"readingMinutes":13,"featured":14,"tags":56,"category":60},117,"supply-chain-gap","Digital Fault Lines in Supply Chains","Every company has its own systems; connecting them is where the gaps appear.","teal","2026-06-23T10:57:00+08:00",[57,58,59],"Industry Watch","Supply Chain","Digitalisation",{"id":61,"parentId":21,"slug":62,"name":57,"description":63,"icon":64,"cover":9,"tone":26,"kind":27,"sortOrder":65,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20,[67,77,88],{"id":68,"slug":69,"title":70,"excerpt":71,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":72,"updatedAt":72,"readingMinutes":13,"featured":14,"tags":73,"category":76},89,"thirty-minute-weekly","The Thirty-Minute Weekly Share","No new technology, no industry trends. Just the pitfalls of the week and how they were solved.","2026-10-11T09:00:00+08:00",[16,74,75],"Knowledge Sharing","Growth",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":78,"slug":79,"title":80,"excerpt":81,"content":9,"cover":9,"tone":82,"author":11,"publishedAt":83,"updatedAt":83,"readingMinutes":13,"featured":14,"tags":84,"category":87},90,"what-code-review-is-for","What Code Review Is Really For","Review is not fault-finding. It is letting another mind walk through your code.","cyan","2026-09-29T10:13:00+08:00",[16,85,86],"Code Review","Engineering Practice",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":89,"slug":90,"title":91,"excerpt":92,"content":9,"cover":9,"tone":54,"author":11,"publishedAt":93,"updatedAt":93,"readingMinutes":13,"featured":14,"tags":94,"category":95},91,"docs-start-with-templates","Documents Start With Templates","People avoid writing docs mostly because they do not know where to start. A template solves most of it.","2026-09-17T11:26:00+08:00",[16,18,17],{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]