<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>AI Coding in Practice</title>
<link>https://lu.siney.top/</link>
<description>Hands-on writing on AI coding in practice.</description>
<language>en</language>
<atom:link href="https://lu.siney.top/feed.xml" rel="self" type="application/rss+xml"/>
<item>
<title>I Built a Fully Automated Short-Video Pipeline with Claude Code. Two Months In, Here&apos;s the Real Data</title>
<link>https://lu.siney.top/laopao/ai-coding-video-pipeline-honest-data/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-video-pipeline-honest-data/en/</guid>
<pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
<description>Script to finished video to scheduled publishing, zero human hands, daily posts on two platforms across three accounts. This is not a &apos;six figures a month&apos; post — most of my videos got two-digit view counts. But three things the data taught me are worth more than a hit would have been: topic tier, content-platform fit, and the ceiling baked into the format. Full architecture plus 9 things that broke.</description>
</item>
<item>
<title>Claude Code or Codex? You&apos;re Asking the Wrong Question</title>
<link>https://lu.siney.top/laopao/claude-code-vs-codex-which/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/claude-code-vs-codex-which/en/</guid>
<pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
<description>Every few days someone on a dev forum asks &apos;is Claude Code or Codex better right now&apos;, and the thread splits into two camps that never convince each other. My take: it never resolves because the question is wrong. They aren&apos;t an either/or—they&apos;re two tools with different feel. The pragmatic move is to keep both, switch by task and quota, and let cost decide your daily driver. And the ultimate selection criterion was always &apos;which one finishes the job within your limit&apos;—which requires getting the bill straight first.</description>
</item>
<item>
<title>AI Coding Kills Middle Managers First, Not Juniors or Seniors</title>
<link>https://lu.siney.top/laopao/ai-coding-mid-manager-squeeze/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-mid-manager-squeeze/en/</guid>
<pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
<description>Meta, Google, Amazon all flattened middle management before AI Coding hit scale; AI just turned that move from optional to mandatory. Three TL workflows — task allocation, review, cross-team alignment — get bypassed by senior ICs with agents, drowned by PR throughput, replaced by shared specs. Two paths left: collapse back to IC, or expand span upward.</description>
</item>
<item>
<title>Next Month, Big Tech Starts Auditing the Token Bill</title>
<link>https://lu.siney.top/laopao/ai-coding-token-cost-audit/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-token-cost-audit/en/</guid>
<pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
<description>For a year, companies rolled out AI coding tools on a &apos;just use it&apos; basis—nobody watched tokens. But once it goes from &apos;a few people trying&apos; to &apos;everyone, daily&apos;, the absolute bill clears finance&apos;s attention threshold. I bet cost auditing becomes a main thread within a month—and most teams can&apos;t answer the three questions (where did it go, how much was wasted, was it worth it) because vendor dashboards only show org-level totals. This is a tooling-category window.</description>
</item>
<item>
<title>Lagou Is Dead: A 13-Year Job Board Killed by AI Pulling Out All Three Middleman Steps at Once</title>
<link>https://lu.siney.top/laopao/lagou-shutdown-middleman-collapse/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/lagou-shutdown-middleman-collapse/en/</guid>
<pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
<description>Lagou — for most of the 2010s China&apos;s go-to job board for tech — didn&apos;t die at the tail end of a hiring winter. It&apos;s the marker event for AI&apos;s first replacement wave landing on middleman work: JD writing, resume screening and first-round interviews all got absorbed into corporate HR toolchains at once, leaving the platform with none of the three actions it lived on. Which middleman platform falls next? Three signals to watch, plus a sharper question: a lot of veterans are middlemen themselves and haven&apos;t noticed.</description>
</item>
<item>
<title>Why Vibe Coding Is Addictive: It Turns Coding Back Into a Game</title>
<link>https://lu.siney.top/laopao/vibe-coding-flow-game/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/vibe-coding-flow-game/en/</guid>
<pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
<description>Flow isn&apos;t mystical — it&apos;s just treating the task in front of you like a game. Games pull you into flow through three things: exploration, randomness, and a sense of achievement. Vibe coding happens to stuff all three back into writing software, which is exactly why it&apos;s addictive. But the same loop that delivers flow can also turn you into someone yanking a slot-machine lever. The veteran&apos;s job is to use the mechanic, not be used by it.</description>
</item>
<item>
<title>8-Line Spec Beats 8-Hour Prompts: The Real Payoff of Spec-Driven AI Coding</title>
<link>https://lu.siney.top/laopao/ai-coding-spec-vs-prompt/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-spec-vs-prompt/en/</guid>
<pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
<description>&apos;I spent the whole afternoon arguing with the AI to make it write the right thing&apos; — still a 2026 cliché. But teams that switched to writing 8-line specs upfront find AI&apos;s first-pass correctness jumps from 30% to 85%. This isn&apos;t a prompt-engineering trick. It&apos;s a software-engineering paradigm shift: the bottleneck has always been your inability to specify.</description>
</item>
<item>
<title>Building a Personal AI Coding Harness: 14 Traps Between &quot;It Runs&quot; and &quot;It Works&quot;</title>
<link>https://lu.siney.top/laopao/ai-coding-harness-14-traps/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-harness-14-traps/en/</guid>
<pubDate>Mon, 25 May 2026 00:00:00 GMT</pubDate>
<description>A harness isn&apos;t a pile of tools — it&apos;s the code that encodes your team&apos;s workflow as scheduling logic. A year of running one in production, sorted into 14 traps across 4 groups: economics (how you spend), robustness (how you don&apos;t crash), quality (how you ship), extensibility (how it evolves). Miss these and your harness stays a demo forever.</description>
</item>
<item>
<title>Experience Sediment 2.0: Stop Writing for Colleagues, Start Writing for Agents</title>
<link>https://lu.siney.top/laopao/ai-coding-experience-sediment/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-experience-sediment/en/</guid>
<pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
<description>Wikis, RFCs, and onboarding docs were written for &quot;a future colleague.&quot; Since 2024 the most frequent reader of all that has stopped being human — it&apos;s an agent. The reader changed; most senior engineers haven&apos;t changed how they write. Here&apos;s the three-layer architecture (cursorrules / spec kits / harness orchestration) and which lessons are worth feeding an agent at all.</description>
</item>
<item>
<title>The Hardest Part of Rolling Out AI Coding Isn&apos;t Tech — It&apos;s Two Kinds of Old-Timers</title>
<link>https://lu.siney.top/laopao/ai-coding-laodeng-two-types/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-laodeng-two-types/en/</guid>
<pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
<description>A year of pushing AI Coding into a 20-person team. The blocker was never technology — it was two specific people. The mocker tries Cursor twice, gets burned, and tells everyone it doesn&apos;t work. The blocker is a mid-level leader who stalls forever behind &apos;quality risk&apos; and &apos;compliance review.&apos; Different motives, different counters. Mix the playbooks and you lose.</description>
</item>
<item>
<title>How to Become a Super Individual: Taste Is the Ticket, Tokens Are the Fuel, Brainpower Is the Ceiling</title>
<link>https://lu.siney.top/laopao/super-individual-taste-token-brain/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/super-individual-taste-token-brain/en/</guid>
<pubDate>Sun, 24 May 2026 00:00:00 GMT</pubDate>
<description>The hottest 2026 narrative is the &apos;super individual&apos; or &apos;one-person company&apos;. Strip away the story and look at the structure: three deeply unequal resources decide whether you can pull this off — taste that defines product shape, ruthless compression of token spend, and a brain that simply cannot keep pace with AI. The first two are the price of entry. The third is the actual ceiling.</description>
</item>
<item>
<title>The AI-Era Couple Business: She Builds Audience, He Builds Product</title>
<link>https://lu.siney.top/laopao/ai-couple-shop/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-couple-shop/en/</guid>
<pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate>
<description>The strongest startup unit isn&apos;t a lone genius or a VC-backed team of ten — it&apos;s two people with deeply complementary skills. AI has collapsed the technical floor. What&apos;s actually scarce is user trust. The female partner&apos;s audience account is the optimal answer.</description>
</item>
<item>
<title>MCP One Year On: The Protocol Won, Vendor Moats Evaporated</title>
<link>https://lu.siney.top/laopao/ai-coding-mcp-year-one/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-mcp-year-one/en/</guid>
<pubDate>Mon, 18 May 2026 00:00:00 GMT</pubDate>
<description>A year ago MCP launched and everyone was betting on whether it would become another forgotten protocol. Verdict&apos;s in: it won. But winning meant flattening every IDE vendor&apos;s differentiation. Cursor can call Claude Code&apos;s servers, Windsurf can call Cursor&apos;s, tool wars degenerated from &apos;what integrations are exclusive to me&apos; to &apos;whose skin looks nicer.&apos;</description>
</item>
<item>
<title>AI Amplifies the Mid-Career, Not the Junior — A Counterintuitive Truth</title>
<link>https://lu.siney.top/laopao/ai-amplifies-mid-career/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-amplifies-mid-career/en/</guid>
<pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate>
<description>The default narrative says AI takes out mid-career first. Pull the data apart and the direction reverses — AI favors juniors on narrow, scripted tasks; it overwhelmingly favors mid-career on open-ended, ambiguous ones. Judgment, failure-smell, system thinking, organizational fluency: these four experience assets aren&apos;t replaced in the AI era. They get multiplied.</description>
</item>
<item>
<title>Code Review Is the Real AI-Era Bottleneck — And Your Team Isn&apos;t Doing It</title>
<link>https://lu.siney.top/laopao/ai-coding-review-bottleneck/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-review-bottleneck/en/</guid>
<pubDate>Invalid Date</pubDate>
<description>GitClear 2024 data: 8x growth in duplicated code blocks, rising short-term churn, refactoring share down from 25% to &lt;10%. DORA 2024: AI teams&apos; delivery stability is down 7.2%. My own 12 EM 1:1s match: PR size grew 2-3x, review time actually went *up* (AI code is harder to read), but &apos;approved without comments&apos; moved from occasional to default. Quality debt gets pushed 2-3 quarters out.</description>
</item>
<item>
<title>Digital Coders Explored: An Overhyped Narrative on Top of Under-Built Engineering</title>
<link>https://lu.siney.top/laopao/ai-coding-digital-engineer/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-digital-engineer/en/</guid>
<pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
<description>「Our AI digital engineer is live」 posts are everywhere. Look closer: 90% is a chatbot with an avatar. The engineering underneath — persistent identity, long-term memory, autonomous loop, collaboration interfaces — is the real lever for organizational productivity in 2026-2028.</description>
</item>
<item>
<title>Backend Falls First, Not Frontend: The Real Order of AI Replacement Across the Stack</title>
<link>https://lu.siney.top/laopao/ai-replaces-backend-first/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-replaces-backend-first/en/</guid>
<pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate>
<description>Everyone says frontend gets killed first. Wrong — AI eats backend first, native client last. Replacement speed isn&apos;t about code difficulty; it&apos;s about whether the full work loop closes in text.</description>
</item>
<item>
<title>AI Coding&apos;s Real Bottleneck in 2026: From Tokens to Your Physical Workstation</title>
<link>https://lu.siney.top/laopao/ai-coding-physical-bottleneck/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-physical-bottleneck/en/</guid>
<pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate>
<description>Tokens stopped being the AI Coding bottleneck. In 2026 what slows you down is whether your monitors fit 5 active streams, whether your RAM holds 3 agents in parallel, and whether your network handles every API round-trip reliably.</description>
</item>
<item>
<title>Cursor&apos;s $20B Peak: Users Are Quietly Migrating, And You Should Know Where</title>
<link>https://lu.siney.top/laopao/ai-coding-cursor-peak/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-cursor-peak/en/</guid>
<pubDate>Tue, 12 May 2026 00:00:00 GMT</pubDate>
<description>March 2026: Cursor closed its $20B Series D. Same window: DAU retention fell from 76% to 68%. That&apos;s not a contradiction — it&apos;s &apos;valuation prices the last 6 months, users vote with the next 6.&apos; Track where they&apos;re going, and you can read 2027&apos;s tool landscape today.</description>
</item>
<item>
<title>Measuring AI Coding Productivity: Why 5x Coding Doesn&apos;t Mean 5x Delivery</title>
<link>https://lu.siney.top/laopao/ai-coding-productivity-metrics/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-productivity-metrics/en/</guid>
<pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
<description>Mainstream AI Coding metrics only measure the coding segment, missing the full pipeline. Breaking the SDLC into 6 phases shows real productivity gain is 15-30% (not 5x), and the bottleneck has moved to Review and testing.</description>
</item>
<item>
<title>Vibe Coding&apos;s Security Debt: The Bill Comes Due in H2 2026</title>
<link>https://lu.siney.top/laopao/ai-coding-vibe-security-debt/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-vibe-security-debt/en/</guid>
<pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate>
<description>Vibe coding lets PMs, designers, ops &apos;just ship something.&apos; But AI-generated code carries three systemic vuln classes by default — SQL injection frequency is *higher* than in 2020, hardcoded secrets appear in 31% of vibe-coded repos, OAuth misimplementation remains a classic. The debt is already on the books. Settlement comes in H2 2026.</description>
</item>
<item>
<title>Chinese LLMs Won on Cost: DeepSeek + Qwen + Kimi at 1/10 the Per-Task Price of GPT/Claude</title>
<link>https://lu.siney.top/laopao/ai-coding-chinese-llms-winning/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-chinese-llms-winning/en/</guid>
<pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate>
<description>DeepSeek-Coder-V3, Qwen3-Max-Coder, and Kimi K2 deliver AI Coding at 1/10 the per-task cost of GPT-5.5 / Claude 4.x — with SWE-bench Verified scores within 10%. In enterprise batch-workload scenarios, this gap is disruptive. Western vendors are responding slowly. This isn&apos;t nationalism — it&apos;s an engineering ledger.</description>
</item>
<item>
<title>Local LLMs Are Already Daily-Driver Ready: M4 + GGUF, No Cloud Needed</title>
<link>https://lu.siney.top/laopao/ai-coding-local-llm-reality/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-local-llm-reality/en/</guid>
<pubDate>Thu, 07 May 2026 00:00:00 GMT</pubDate>
<description>&apos;Local models are always 2 generations behind frontier&apos; — that was true in 2024. Not in 2026. Qwen3-Coder 14B at Q5, on an M4 Pro: daily AI coding tasks at parity with GPT-5.5, and 30% of scenarios are *faster* (no network round-trip). Privacy, offline, zero marginal cost. The hardware wall is gone.</description>
</item>
<item>
<title>Junior Onboarding Is Broken: AI Stole Mentor Time, Nobody&apos;s Coaching the New Hires</title>
<link>https://lu.siney.top/laopao/ai-coding-junior-onboarding-broken/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-junior-onboarding-broken/en/</guid>
<pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate>
<description>AI doubles mid-level productivity — at the cost of zero mentoring time. Across 9 companies&apos; onboarding data, junior &apos;first-year growth curve&apos; is collapsing: time-to-independent-contribution stretched from 4 to 7 months, 3-year voluntary attrition jumped 90%. This is organizational damage that compounds and won&apos;t fully surface until 2027.</description>
</item>
<item>
<title>$10M ARR with 3 People: The Real Structure of Hyper-Solo Companies</title>
<link>https://lu.siney.top/laopao/ai-coding-solo-founder-structure/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-solo-founder-structure/en/</guid>
<pubDate>Tue, 05 May 2026 00:00:00 GMT</pubDate>
<description>&apos;3-person team, $10M ARR&apos; was hype in 2023. By 2026, there are 20+ documented cases. But these aren&apos;t &apos;solo hero&apos; stories — they share a precise structural recipe: 1 AI-leveraged engineer + 1 distribution lead + 1 customer success, with 8-12 AI agents replacing functional roles. See the structure or the narrative will fool you.</description>
</item>
<item>
<title>Leetcode Is Dead, But 90% of Companies Still Ask Leetcode</title>
<link>https://lu.siney.top/laopao/ai-coding-leetcode-still-asked/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-leetcode-still-asked/en/</guid>
<pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
<description>AI solves leetcode in 5 seconds. Yet in 2026, 90% of companies still ask vanilla leetcode questions. This isn&apos;t &apos;enterprises are slow&apos; — it&apos;s interviewers pretending AI doesn&apos;t exist. The result is collective cognitive misalignment, filtering out the genuinely strong and selecting for test-takers.</description>
</item>
<item>
<title>The &apos;Ferrari Uncle&apos; and 45 Years on One Craft: Senior Engineers Are Being Repriced in the AI Era</title>
<link>https://lu.siney.top/laopao/professional-premium-in-ai-era/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/professional-premium-in-ai-era/en/</guid>
<pubDate>Mon, 04 May 2026 00:00:00 GMT</pubDate>
<description>A 57-year-old dance professor goes viral for out-dancing a crowd of judges in suits, and everyone files it under &apos;midlife comeback.&apos; It isn&apos;t. It&apos;s a market signal: when production cost collapses, judgment becomes the entire price. Shallow skills keep depreciating, deep judgment keeps appreciating, and the gap is widening — plus what actually happened when I rolled out AI Coding across a 20-person team.</description>
</item>
<item>
<title>The Token Economy Collapse: From Pay-Per-Use to Unlimited Subscriptions — Who Pays the Subsidy</title>
<link>https://lu.siney.top/laopao/ai-coding-token-economy-collapse/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-token-economy-collapse/en/</guid>
<pubDate>Sun, 03 May 2026 00:00:00 GMT</pubDate>
<description>In 2024 everyone counted tokens. By 2026, &apos;Claude Code Max $200/mo unlimited&apos;, &apos;Codex Pro all-you-can-eat&apos;, &apos;Cursor unlimited&apos; are mainstream. The user wins — token-counting is over. Behind the scenes, four parties are losing: Anthropic, OpenAI, mid-tier tooling vendors, and heavy users themselves. See who subsidizes whom, and you&apos;ll see how this game ends.</description>
</item>
<item>
<title>Counteroffer vs. Jumping: What the Five-Year Math Actually Says</title>
<link>https://lu.siney.top/chengzhang/jump-or-stay/en/</link>
<guid isPermaLink="true">https://lu.siney.top/chengzhang/jump-or-stay/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>The &apos;I switched jobs and got a 30% raise&apos; story travels furthest and misleads most. Judging an offer by how much the base moves is a rookie calculation — the real return only shows up when you run three to five years of total compensation. Counteroffers aren&apos;t automatically the trap the internet says they are, either.</description>
</item>
<item>
<title>Why You&apos;re Not Getting Promoted: The Three Months Before the Packet</title>
<link>https://lu.siney.top/chengzhang/promotion-stuck/en/</link>
<guid isPermaLink="true">https://lu.siney.top/chengzhang/promotion-stuck/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>90% of &apos;I can&apos;t get promoted&apos; is not a capability problem — it&apos;s a narrative problem. A year of your work turns into five bullet points on a slide, and the committee is evaluating whether those five lines make them remember you. Doing the work and getting it told are two separate jobs; most people start the second one the week before the deadline.</description>
</item>
<item>
<title>AI Coding Flips English Disadvantage: How Non-Native Developers Are Quietly Winning</title>
<link>https://lu.siney.top/laopao/ai-coding-non-native-english-flip/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/ai-coding-non-native-english-flip/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>For 15 years, Chinese developers hit a ceiling on English: slow at reading docs, weak at commit messages, awkward in interviews. AI just demolished that wall. Claude writes your PR descriptions, parses papers, mediates 1:1 conversations — at a quality higher than 95% of native speakers. **This is a wildly underestimated reverse-tailwind window**.</description>
</item>
<item>
<title>Getting Out: The 18-Month Path from Decision to Exit</title>
<link>https://lu.siney.top/laopao/exit-strategy/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/exit-strategy/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>Somewhere around forty, tech veterans start thinking about getting out. The ones who leave with any dignity give themselves an 18-month runway from the moment they decide; the impulse version — fed up on Tuesday, resigned on Wednesday — mostly turns into regret inside six months. Leaving isn&apos;t a single move: it&apos;s money, skills, relationships, and your head, adjusted in parallel.</description>
</item>
<item>
<title>Reading the Next Industry Shift Two Years Early</title>
<link>https://lu.siney.top/laopao/industry-shift/en/</link>
<guid isPermaLink="true">https://lu.siney.top/laopao/industry-shift/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>The Chinese internet has flipped several times in thirty years: PC to mobile to O2O to short video to large models. Every flip broadcast its signals about two years ahead, and most people in the industry didn&apos;t notice until the coverage was everywhere. Two years early and you have time to move; two years late and you take whatever comes — the pay cut, the layoff, the career change you didn&apos;t choose.</description>
</item>
<item>
<title>Your First Month: How to Build Trust With a New Manager</title>
<link>https://lu.siney.top/xinren/first-month-with-boss/en/</link>
<guid isPermaLink="true">https://lu.siney.top/xinren/first-month-with-boss/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>A manager&apos;s read on a new hire is roughly 90% locked in within four weeks, and once they&apos;ve decided &apos;this one needs chasing,&apos; no amount of later diligence really overwrites it. The conversational rhythm you set in those first weeks defines how they use you for the next year — which is why treating month one as a waiting room is the most expensive new-hire mistake.</description>
</item>
<item>
<title>Six Months In and Already Want Out: Real Signal, or Just the Adjustment?</title>
<link>https://lu.siney.top/xinren/should-i-quit/en/</link>
<guid isPermaLink="true">https://lu.siney.top/xinren/should-i-quit/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>Of the people who want out six months into their first job, at least 70% are misreading &apos;I haven&apos;t adjusted&apos; as &apos;I picked wrong.&apos; New grads arrive expecting a curriculum, a manager who explains things patiently, and teammates who help each other out — none of the three hold anywhere. Three questions that separate a real signal from the adjustment.</description>
</item>
<item>
<title>Manager or IC: Three Questions to Ask Yourself Honestly</title>
<link>https://lu.siney.top/zishen/manager-or-ic/en/</link>
<guid isPermaLink="true">https://lu.siney.top/zishen/manager-or-ic/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>The IC track and the management track fork around senior/staff, and most people make the choice passively — the boss asks you to take the team, or nobody else is a plausible candidate. The costliest assumption is that management is the higher rung, a belief that runs especially deep in Chinese tech. They&apos;re parallel tracks: different work, different wiring.</description>
</item>
<item>
<title>Stuck Below Staff: The Jump from Executing to Setting Direction</title>
<link>https://lu.siney.top/zishen/p7-bottleneck/en/</link>
<guid isPermaLink="true">https://lu.siney.top/zishen/p7-bottleneck/en/</guid>
<pubDate>Sat, 02 May 2026 00:00:00 GMT</pubDate>
<description>Senior to staff is the hardest step on the IC ladder — around 70% of people sit here for two or three years, and some never get through and quietly stop trying. The reason usually isn&apos;t that they&apos;re not technical enough. It&apos;s that nobody told them the job changed identity: from executing well to deciding what gets executed.</description>
</item>
</channel>
</rss>
