[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-how-small-teams-learn-en":3,"blog-related-how-small-teams-learn-en":30,"blog-adjacent-how-small-teams-learn-en":62},{"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},23,"how-small-teams-learn","How a Small Team Learns New Technology","No training budget, no study time. Learning has to be folded into real projects.","\u003Cp>Every stack change makes the team anxious: too much to learn and no appetite for experimenting on client systems. Over the years we found a plain approach: make learning happen inside real work.\u003C\u002Fp>\n\u003Ch2>Three concrete habits\u003C\u002Fh2>\n\u003Cp>The first use of any new technology is an internal tool, such as a deployment script or a data cleaning utility, where real needs surface real problems.\u003C\u002Fp>\n\u003Cp>Introduce one new thing at a time. Changing the framework, the database and the deployment model together makes every failure untraceable.\u003C\u002Fp>\n\u003Cp>Learning ends with an output: an internal document or a half-hour session. If you cannot explain it, you have not learned it.\u003C\u002Fp>\n\u003Ch2>Mistakes we made\u003C\u002Fh2>\n\u003Cp>We once introduced a new frontend framework and a new backend language in the same client project. It slipped two months and half of it was rolled back.\u003C\u002Fp>\n\u003Cp>We also rewrote a stable module just to use something new. The client gained nothing and the team worked two extra weeks.\u003C\u002Fp>\n\u003Cp>Technology is not the goal; delivery is. Learning can be slow, but a client's system is not a sandbox.\u003C\u002Fp>","","slate","佳益方圆团队","2026-05-04T14:49:00+08:00",1,false,[16,17,18],"Startup","Technology","Learning",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},6,0,"founder-notes","Founder Notes","Reflections from the founding team on business, management and product, documenting the growth of a software company.","pen-tool","blue","article",10,{},[31,40,51],{"id":28,"slug":32,"title":33,"excerpt":34,"content":9,"cover":9,"tone":26,"author":11,"publishedAt":35,"updatedAt":35,"readingMinutes":13,"featured":14,"tags":36,"category":39},"quote-by-scope-not-hours","Why We Quote by Scope, Not by Man-Days","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.","2026-10-07T09:00:00+08:00",[16,37,38],"Pricing","Partnership",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":41,"slug":42,"title":43,"excerpt":44,"content":9,"cover":9,"tone":45,"author":11,"publishedAt":46,"updatedAt":46,"readingMinutes":13,"featured":14,"tags":47,"category":50},11,"three-lessons-from-first-client","Three Lessons From Our First Client","Our first project in 2019 was worth thirty thousand yuan and taught us more about contracts, acceptance and honesty than any course.","cyan","2026-09-25T10:13:00+08:00",[16,48,49],"Client","Contract",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"id":52,"slug":53,"title":54,"excerpt":55,"content":9,"cover":9,"tone":56,"author":11,"publishedAt":57,"updatedAt":57,"readingMinutes":13,"featured":14,"tags":58,"category":61},12,"choosing-clients-not-deals","Choosing Clients Matters More Than Choosing Projects","The same contract can grow a team or drain it. We now screen clients with three questions.","indigo","2026-09-13T11:26:00+08:00",[16,59,60],"Clients","Judgement",{"id":20,"parentId":21,"slug":22,"name":23,"description":24,"icon":25,"cover":9,"tone":26,"kind":27,"sortOrder":28,"count":21},{"previous":63,"next":79},{"id":64,"slug":65,"title":66,"excerpt":67,"content":9,"cover":9,"tone":56,"author":11,"publishedAt":68,"updatedAt":68,"readingMinutes":13,"featured":14,"tags":69,"category":73},121,"rpa-and-workflow","RPA and Workflow Automation: Overrated and Underrated","RPA demos well, but few enterprises get it running. Technology is overrated; process analysis is underrated.","2026-05-06T14:49:00+08:00",[70,71,72],"Industry Watch","RPA","Process Automation",{"id":74,"parentId":21,"slug":75,"name":70,"description":76,"icon":77,"cover":9,"tone":26,"kind":27,"sortOrder":78,"count":21},5,"industry-watch","In-depth analysis of internet, software and digital industry trends with our own point of view.","globe",20,{"id":80,"slug":81,"title":82,"excerpt":83,"content":9,"cover":9,"tone":45,"author":11,"publishedAt":84,"updatedAt":84,"readingMinutes":13,"featured":14,"tags":85,"category":89},44,"file-storage-evolution","File Storage: From Local Disk to Object Storage","Attachment features start simple, until clients upload multi-gigabyte videos and ask for per-file permissions.","2026-05-02T15:02:00+08:00",[86,87,88],"Storage","Architecture","Files",{"id":13,"parentId":21,"slug":90,"name":91,"description":92,"icon":93,"cover":9,"tone":26,"kind":27,"sortOrder":94,"count":21},"engineering","Engineering","Hands-on engineering practices in architecture, performance optimization, AI integration and cross-platform delivery from our R and D team.","cpu",60]