[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-overtime-tracking-en":3,"blog-adjacent-overtime-tracking-en":30,"blog-related-overtime-tracking-en":65},{"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},97,"overtime-tracking","Recording and Compensating Overtime","Neither glamorise nor ignore overtime. Treat it as a cost that must be visible.","\u003Cp>Software projects have peak periods, especially near launches. We used to acknowledge overtime verbally, and nobody knew who worked how much, which bred resentment at raise time. So we started recording it formally.\u003C\u002Fp>\n\u003Ch2>How we record it\u003C\u002Fh2>\n\u003Cp>One minute before leaving: log hours, whether it was overtime, and why (client deadline, incident, personal arrangement).\u003C\u002Fp>\n\u003Cp>Only the manager and the person see the data. No team rankings, no negative scoring in performance.\u003C\u002Fp>\n\u003Cp>A monthly summary shows which project and phase absorbs overtime, feeding schedule improvements.\u003C\u002Fp>\n\u003Ch2>How we compensate\u003C\u002Fh2>\n\u003Cp>Weekday overtime accrues hourly time off valid for three months, and managers actively remind people to use it.\u003C\u002Fp>\n\u003Cp>Launch duty and peak-season support are compensated in half-day units so it is not lost in fragments.\u003C\u002Fp>\n\u003Cp>If overtime exceeds the threshold three months running, the manager must analyse causes rather than ask individuals to endure.\u003C\u002Fp>\n\u003Cp>Recording overtime is not about judging effort; it keeps scheduling honest. Only visible costs get optimised.\u003C\u002Fp>","","indigo","佳益方圆团队","2026-07-07T09:44:00+08:00",1,false,[16,17,18],"Team Culture","Overtime","Management",{"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},78,"change-request-cascade","Retrospective: The Cascade Behind One Change","Splitting 'customer' into enterprise and individual looked like one field. It touched six modules.","cyan","2026-07-09T09:44:00+08:00",[39,40,41],"Retrospective","Change","Delivery",{"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":10,"author":11,"publishedAt":54,"updatedAt":54,"readingMinutes":13,"featured":14,"tags":55,"category":59},116,"private-domain-tools","How Many Private-Domain Tools Does a Company Need?","SCRM, community, livestream, membership: the more tools, the more fragmented the customer.","2026-07-05T09:44:00+08:00",[56,57,58],"Industry Watch","Private Domain","Tools",{"id":60,"parentId":21,"slug":61,"name":56,"description":62,"icon":63,"cover":9,"tone":26,"kind":27,"sortOrder":64,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20,[66,76,86],{"id":67,"slug":68,"title":69,"excerpt":70,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":71,"updatedAt":71,"readingMinutes":13,"featured":14,"tags":72,"category":75},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,73,74],"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":77,"slug":78,"title":79,"excerpt":80,"content":9,"cover":9,"tone":36,"author":11,"publishedAt":81,"updatedAt":81,"readingMinutes":13,"featured":14,"tags":82,"category":85},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.","2026-09-29T10:13:00+08:00",[16,83,84],"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":87,"slug":88,"title":89,"excerpt":90,"content":9,"cover":9,"tone":91,"author":11,"publishedAt":92,"updatedAt":92,"readingMinutes":13,"featured":14,"tags":93,"category":96},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.","teal","2026-09-17T11:26:00+08:00",[16,94,95],"Documentation","Knowledge Management",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21}]