[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-search-in-admin-en":3,"blog-adjacent-search-in-admin-en":30,"blog-related-search-in-admin-en":63},{"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},69,"search-in-admin","Designing Search in Admin Systems","Anyone can add a search box. The hard part is matching how users actually look for data.","\u003Cp>Admin search is usually one input doing a fuzzy match across all fields. Searching a client name returns orders and contracts too, and the right record is three pages down. The problem is design, not technology.\u003C\u002Fp>\n\u003Ch2>Three design points\u003C\u002Fh2>\n\u003Cp>Separate exact from fuzzy: identifiers such as numbers and phone numbers use exact match, names use fuzzy match.\u003C\u002Fp>\n\u003Cp>Offer filter combinations: status, time range and owner shorten the search far more than any fuzzy match.\u003C\u002Fp>\n\u003Cp>Order results with logic: most recently updated first, or by business importance, never by primary key.\u003C\u002Fp>\n\u003Ch2>Performance notes\u003C\u002Fh2>\n\u003Cp>Limit fuzzy scans on large tables, for example to the last year of data, or introduce a dedicated search index.\u003C\u002Fp>\n\u003Cp>Debounce and cancel requests so typing does not fire a query per keystroke.\u003C\u002Fp>\n\u003Cp>Good search saves three clicks and two pages of scrolling. It is one of the highest-value UX improvements in any admin system.\u003C\u002Fp>","","slate","佳益方圆团队","2026-03-01T12:07:00+08:00",1,false,[16,17,18],"Search","Admin","Product Design",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},2,0,"product-thinking","Product Thinking","Requirement analysis, user experience and product design methods, plus the thinking from business problems to product solutions.","lightbulb","blue","article",50,{},{"previous":31,"next":46},{"id":32,"slug":33,"title":34,"excerpt":35,"content":9,"cover":9,"tone":10,"author":11,"publishedAt":36,"updatedAt":36,"readingMinutes":13,"featured":14,"tags":37,"category":41},49,"log-writing-standards","Logging Standards: Still Readable Three Months Later","Logs are written for future colleagues and for yourself at three in the morning. Structure is the baseline.","2026-03-03T12:07:00+08:00",[38,39,40],"Logging","Standards","Engineering",{"id":13,"parentId":21,"slug":42,"name":40,"description":43,"icon":44,"cover":9,"tone":26,"kind":27,"sortOrder":45,"count":21},"engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",60,{"id":47,"slug":48,"title":49,"excerpt":50,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":51,"updatedAt":51,"readingMinutes":13,"featured":14,"tags":52,"category":56},29,"what-we-want-to-become","What Kind of Company We Want to Be in Ten Years","Not the largest, but the most trustworthy engineering team in the region.","2026-02-21T12:07:00+08:00",[53,54,55],"Startup","Strategy","Long Term",{"id":57,"parentId":21,"slug":58,"name":59,"description":60,"icon":61,"cover":9,"tone":26,"kind":27,"sortOrder":62,"count":21},6,"founder-notes","Founder Notes","Reflections from the founding team on business, management and product, documenting the growth of a software company.","pen-tool",10,[64,75,84],{"id":28,"slug":65,"title":66,"excerpt":67,"content":9,"cover":9,"tone":68,"author":11,"publishedAt":69,"updatedAt":69,"readingMinutes":13,"featured":14,"tags":70,"category":74},"grading-requirement-confidence","Grading the Confidence Behind Requirements","Treating requirements as facts is the most common cause of delay. Requirements differ in how reliable they are.","indigo","2026-10-15T09:00:00+08:00",[71,72,73],"Requirements","Product","Risk",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":20,"slug":76,"title":77,"excerpt":78,"content":9,"cover":9,"tone":68,"author":11,"publishedAt":79,"updatedAt":80,"readingMinutes":13,"featured":14,"tags":81,"category":83},"vertical-product-rules","The Watershed for Vertical Products: Writing Industry Defaults into the System","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.","2026-10-09T10:00:00+08:00","2026-10-18T15:58:14.661+08:00",[82,18],"Industry Products",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":85,"slug":86,"title":87,"excerpt":88,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":89,"updatedAt":89,"readingMinutes":13,"featured":14,"tags":90,"category":92},51,"mvp-boundary","Drawing the Boundary of an MVP","Minimum viable is not the fewest features; it is one complete business loop running end to end.","2026-10-03T10:13:00+08:00",[91,72,71],"MVP",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]