[{"data":1,"prerenderedAt":162},["ShallowReactive",2],{"use-case:zhihu-ai-replacing-programmers-search:en":3,"related-use-cases:zhihu-ai-replacing-programmers-search:social-research:en":127},{"id":4,"title":5,"authorized":6,"body":7,"capabilities":14,"category":15,"contentStructure":16,"context":17,"conversation":18,"dataStory":19,"description":76,"evidence":77,"extension":87,"goal":88,"limitations":89,"locale":96,"meta":97,"navigation":6,"path":98,"performedAt":82,"platforms":99,"prompt":101,"published":6,"redacted":6,"relatedArticles":102,"relatedCases":103,"results":104,"screenshots":109,"seo":110,"slug":111,"sourceType":112,"stem":113,"steps":114,"tools":124,"translationKey":111,"updated":82,"__hash__":126},"useCases\u002Fuse-cases\u002Fzhihu-ai-replacing-programmers-search\u002Fen.md","Search Zhihu for discussions about programmers being replaced by AI",true,{"type":8,"value":9,"toc":10},"minimark",[],{"title":11,"searchDepth":12,"depth":12,"links":13},"",2,[],[],"social-research",null,"A research and content team currently needs to understand how Zhihu frames the question of AI replacing programmers. The immediate need is a current evidence map that can support a careful article or product discussion without overstating consensus.",[],{"userQuestion":20,"problemToSolve":21,"answer":22,"publicDisclosure":23,"targetTitle":24,"metrics":25,"comparison":42,"decisionShift":55,"reusableSteps":65,"nextActions":71},"How does Zhihu currently discuss AI replacing programmers, and can I treat that as consensus?","Stay inside this retrieval's coverage and high-interaction items before deciding how far an article can go.","The upvote-sorted retrieval returned 20 raw items and accepted 18. The top item had 2,791 upvotes and 479 comments. This is the current sample, not Zhihu-wide consensus.","The user authorized publication of retrieval parameters, result counts and native metrics. Personal accounts and contact details remain redacted.","程序员被AI取代",[26,30,34,38],{"label":27,"value":28,"note":29},"Raw results","20","limit=20",{"label":31,"value":32,"note":33},"Accepted results","18","After normalization",{"label":35,"value":36,"note":37},"Highest upvotes","2,791","479 comments",{"label":39,"value":40,"note":41},"Next page","Not requested","No continuation hash",{"title":43,"description":44,"unit":45,"targetLabel":46,"targetValue":47,"items":48},"Highest upvote counts on the returned page","Bars start at zero. These are top items from this page, not the distribution of Zhihu as a whole.","upvotes","Occupation-replacement question",2791,[49,52],{"label":50,"value":51},"10-year replacement question",2549,{"label":53,"value":54},"Devin discussion",1899,[56,59,62],{"label":57,"body":58},"Initial concern","The discussion already shows a clear consensus that programmers will be replaced.",{"label":60,"body":61},"What the data showed","High-interaction items mix replacement questions, junior-role risk and AI coding practice, with polarized attribution.",{"label":63,"body":64},"Revised judgment","Write an evidence map and the disputed claims. Do not present platform consensus or a forecast.",[66,67,68,69,70],"Fix the query, sort and result cap first.","Record raw, accepted and rejected counts.","Treat high-interaction items as a sample, not a census.","Do not imply completeness without a next-page token.","Keep contested attribution visible.",[72,73,74,75],"Rerun with a time window or different sort before claiming recent views.","Write only the recurring themes in this sample.","Do not infer Zhihu-wide sentiment from 18 items.","Keep multiple readings of contested layoff claims.","A current Zhihu search for discussions about programmers being replaced by AI, retaining the 20-result retrieval boundary and 18 accepted results without claiming exhaustive coverage.",[78,83],{"title":79,"body":80,"source":81,"capturedAt":82},"Current retrieval boundary","SignalDig returned 20 raw Zhihu items for \"程序员被AI取代\" with upvote sorting and no time filter; normalization accepted 18 and rejected 2. Captured on 2026-08-31.","SignalDig MCP: search_zhihu_articles","2026-08-31",{"title":84,"body":85,"source":86,"capturedAt":82},"Highest-ranked returned items","The returned page included items with 2,791 upvotes \u002F 479 comments, 2,549 \u002F 231, and 1,899 \u002F 141. These are native Zhihu counters from the current response.","Zhihu public results via SignalDig MCP","md","Search current Zhihu discussions, organize the recurring viewpoints and evidence boundaries, and define what can be responsibly explored next.",[90,91,92,93,94,95],"Only two keywords were used; phrasings like \"AI 编程替代\", \"程序员失业 AI\" or \"AI coding 影响\" may be missed.","Sorting by upvotes favors older posts with accumulated engagement and may understate recent views.","Results cover Zhihu public content only, not the whole Chinese internet or developer community.","No time filter was applied; results span 2023-2026 with very different discussion contexts.","The 30 deduplicated items are default search matches, not a representative sample of platform-wide sentiment.","The response contained 20 raw items and 18 accepted items; no continuation hash was returned, so additional pages were not requested.","en",{},"\u002Fuse-cases\u002Fzhihu-ai-replacing-programmers-search\u002Fen",[100],"Zhihu","@skill:Social Signal Research Search Zhihu for discussions about programmers being replaced by AI",[],[],[105,106,107,108],"Top returned items included the occupation-replacement question (2,791 upvotes \u002F 479 comments), the 10-year programmer replacement question (2,549 \u002F 231), and the Devin discussion (1,899 \u002F 141).","Recurring patterns: junior roles hit hardest (P4 hiring shrinking, junior \"training ground\" taken by AI), AI deepening competition rather than freeing people, a growing senior-vs-junior divide, and programmers broadly embracing AI.","The returned page mixes general replacement questions, programmer career risk, AI coding practice and junior-career concerns; this is a sample pattern, not platform-wide consensus.","Contested claims: Block cutting ~50% (70% of coders) is read by some as \"layoffs of already-unprofitable people\", showing polarized attribution.",[],{"title":5,"description":76},"zhihu-ai-replacing-programmers-search","authorized-user","use-cases\u002Fzhihu-ai-replacing-programmers-search\u002Fen",[115,118,121],{"title":116,"body":117},"Retrieve current Zhihu results","Called search_zhihu_articles with \"程序员被AI取代\", upvote sorting, no time filter and limit 20 on 2026-08-31. The response returned 20 raw items and 18 accepted items after normalization.",{"title":119,"body":120},"Aggregate and deduplicate","The current normalized response contains 18 accepted public items and 2 rejected items; the provider projection also matched related expressions such as \"AI取代初级程序员\".",{"title":122,"body":123},"Structure the report","Organized the findings into summary, recurring patterns, high-engagement evidence, interpretation and coverage limitations.",[125],"$research-social-signals","5QJqbeDKTAE4biKlP7WkbH1hHYekXdKuNto05623O2M",[128,132,136,140,141,147,152,157],{"slug":129,"category":15,"title":130,"description":131,"performedAt":82},"grok-for-excel-seo-signal","Assess Grok's opportunity after OpenAI limits Cursor model access","A current X research snapshot examining how OpenAI's Cursor access change may affect Grok's position in coding tools, with native post metrics and explicit coverage limits.",{"slug":133,"category":15,"title":134,"description":135,"performedAt":82},"wechat-seo-keyword-conflict-article-analysis","Measure how the latest WeChat official-account article is performing","A Social Signal Retrieval run that resolved the WeChat official account (account id and nickname redacted) behind an article, retrieved its latest 10 articles, and benchmarked the target article against the account baseline.",{"slug":137,"category":15,"title":138,"description":139,"performedAt":82},"xiaohongshu-account-growth-diagnosis","Diagnose why a Xiaohongshu account is underperforming and define its direction","A Social Signal Retrieval snapshot of 12 public Xiaohongshu notes, using native account counters and note-level metrics to identify the account's strongest recent topic and format signals.",{"slug":111,"category":15,"title":5,"description":76,"performedAt":82},{"slug":142,"category":143,"title":144,"description":145,"performedAt":146},"chatgpt-403-error-keyword-research","seo-research","Decide whether the \"ChatGPT 403 Forbidden\" error keyword cluster is worth targeting","A keyword demand-signal analysis of the \"ChatGPT 403\" error family that filtered for 50–500 monthly searches and difficulty under 30, then shaped the results into a two-article troubleshooting cluster instead of standalone pages.","2026-08-20",{"slug":148,"category":15,"title":149,"description":150,"performedAt":151},"deepseek-hardness-x-discussions","Find popular X discussions on DeepSeek Harness","A Social Signal Retrieval run that aggregated X, Xiaohongshu and Zhihu signals around the newly released DeepSeek Harness, and turned them into a priority-ranked posting plan with risk boundaries.","2026-08-14",{"slug":153,"category":15,"title":154,"description":155,"performedAt":156},"linkedin-post-engagement-analysis","Analyze 95 LinkedIn posts for a content-strategy shift and replicable engagement patterns","A Social Signal Retrieval run that paginated through all 95 returnable posts of a LinkedIn account, compared early and recent content, and extracted replicable patterns without making readership promises.","2026-08-12",{"slug":158,"category":143,"title":159,"description":160,"performedAt":161},"seo-keyword-opportunity-demand-research","Research real keyword-opportunity needs with Reddit and X signals","A cross-platform social-signal study that combined public Reddit and X discussions into an evidence matrix, identifying the decision confidence, risk checks, and demand context people need from a keyword-opportunity product.","2026-08-07",1788262612949]