<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coding on Leafw&#39;s Blog</title>
    <link>https://leafw.net/en/tags/coding/</link>
    <description>Recent content in Coding on Leafw&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <managingEditor>wyr95626@gmail.com (Leafw)</managingEditor>
    <webMaster>wyr95626@gmail.com (Leafw)</webMaster>
    <copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
    <lastBuildDate>Sun, 16 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://leafw.net/en/tags/coding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>First Impressions of DeepSeek Harness: Everything Being a Plugin Is Too Cool</title>
      <link>https://leafw.net/en/deepseek-harness-first-impressions/</link>
      <pubDate>Sun, 16 Aug 2026 00:00:00 +0000</pubDate><author>wyr95626@gmail.com (Leafw)</author>
      <guid>https://leafw.net/en/deepseek-harness-first-impressions/</guid>
      <description>&lt;p&gt;DeepSeek Harness was released last Friday. Within a few hours, it was everywhere in AI communities in China and abroad.&lt;/p&gt;&#xA;&lt;p&gt;I downloaded it right away and tried it. If you only look at the default interface, the first impression is honestly a bit rough. There are not many feature entry points. It does not even have a client yet. The interaction details are not as complete as Codex, Claude Code, or WorkBuddy. Those products have already been polished for a while. You can open them and start working, and many workflows have already been thought through for you. DeepSeek Harness is still in Developer Preview, and the official README directly says that breaking changes may happen.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenAI and Microsoft Officially “Break Up”: The Most Important Alliance of the AI Era Finally Unbundles</title>
      <link>https://leafw.net/en/openai-microsoft-unbundling/</link>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><author>wyr95626@gmail.com (Leafw)</author>
      <guid>https://leafw.net/en/openai-microsoft-unbundling/</guid>
      <description>&lt;p&gt;&lt;img&#xA;        class=&#34;lazyload&#34;&#xA;        src=&#34;https://leafw.net/svg/loading.min.svg&#34;&#xA;        data-src=&#34;https://leafw-blog-pic.oss-cn-hangzhou.aliyuncs.com/blog/openai-microsoft-20260428/openai-microsoft-2026.png&#34;&#xA;        data-srcset=&#34;https://leafw-blog-pic.oss-cn-hangzhou.aliyuncs.com/blog/openai-microsoft-20260428/openai-microsoft-2026.png, https://leafw-blog-pic.oss-cn-hangzhou.aliyuncs.com/blog/openai-microsoft-20260428/openai-microsoft-2026.png 1.5x, https://leafw-blog-pic.oss-cn-hangzhou.aliyuncs.com/blog/openai-microsoft-20260428/openai-microsoft-2026.png 2x&#34;&#xA;        data-sizes=&#34;auto&#34;&#xA;        alt=&#34;https://leafw-blog-pic.oss-cn-hangzhou.aliyuncs.com/blog/openai-microsoft-20260428/openai-microsoft-2026.png&#34;&#xA;        title=&#34;https://leafw-blog-pic.oss-cn-hangzhou.aliyuncs.com/blog/openai-microsoft-20260428/openai-microsoft-2026.png&#34; /&gt;&lt;/p&gt;&#xA;&lt;p&gt;On April 27, 2026, OpenAI and Microsoft released statements at the same time: the two companies had revised their partnership agreement.&lt;/p&gt;&#xA;&lt;p&gt;You could call it a &amp;ldquo;breakup.&amp;rdquo; The reason is not hard to understand. Microsoft no longer has exclusive licensing rights to OpenAI&amp;rsquo;s models and products. OpenAI can offer products on any cloud platform. Microsoft will also stop paying revenue share to OpenAI. For the past few years, these two companies were almost treated as one AI camp. Now there is suddenly a line between them, and that is big news.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Collective Retreat of AI Coding Subscriptions: From Carnival to Tightening in One Quarter</title>
      <link>https://leafw.net/en/ai-coding-subscription-retreat/</link>
      <pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate><author>wyr95626@gmail.com (Leafw)</author>
      <guid>https://leafw.net/en/ai-coding-subscription-retreat/</guid>
      <description>&lt;h2 id=&#34;a-shutdown-notice&#34;&gt;A Shutdown Notice&lt;/h2&gt;&#xA;&lt;p&gt;On April 20, GitHub published a blog post with a restrained title: &amp;ldquo;Changes to GitHub Copilot Individual Plans.&amp;rdquo; The content was much less restrained:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;New signups for Pro, Pro+, and Student plans were paused&lt;/li&gt;&#xA;&lt;li&gt;Usage limits were tightened through both session limits and weekly limits&lt;/li&gt;&#xA;&lt;li&gt;Claude Opus was removed from the Pro plan&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The reason was direct: agentic workflows were consuming far more compute than expected, and &amp;ldquo;a small number of requests can now cost more than the subscription price itself.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>I Paused Vibecoding for a Month</title>
      <link>https://leafw.net/en/vibecoding-pause/</link>
      <pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><author>wyr95626@gmail.com (Leafw)</author>
      <guid>https://leafw.net/en/vibecoding-pause/</guid>
      <description>&lt;h2 id=&#34;how-i-stopped&#34;&gt;How I Stopped&lt;/h2&gt;&#xA;&lt;p&gt;Over the past few months, I had been using vibecoding almost obsessively. The term has become common enough by now: using AI to quickly build products, sometimes taking an idea from scratch to launch in just a few days, or even a few hours. I enjoyed that pace. I could have an idea at midnight, start coding the next day, and publish it over the weekend.&lt;/p&gt;&#xA;&lt;p&gt;During that period I built two apps and a client somewhat like a combination of Lobehub and local Claude Code. The number was not huge, but the last one gave me the strongest sense of frustration.&lt;/p&gt;</description>
    </item>
    <item>
      <title>In the LLM Era, the Programmer&#39;s Virtue of Laziness Is Disappearing</title>
      <link>https://leafw.net/en/llm-laziness-lost/</link>
      <pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><author>wyr95626@gmail.com (Leafw)</author>
      <guid>https://leafw.net/en/llm-laziness-lost/</guid>
      <description>&lt;h3 id=&#34;introduction&#34;&gt;Introduction&lt;/h3&gt;&#xA;&lt;p&gt;Have you had this experience too: you use an LLM to write code, produce thousands of lines in a day, and then look back only to realize that the truly valuable part may be no more than a few hundred lines?&lt;/p&gt;&#xA;&lt;p&gt;It sounds absurd, but it is becoming normal. Bryan Cantrill, CTO of Oxide and co-creator of DTrace, recently wrote &lt;a href=&#34;https://bcantrill.dtrace.org/2026/04/12/the-peril-of-laziness-lost/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreffer &#34;&gt;The Peril of Laziness Lost&lt;/a&gt;, aiming directly at the heart of the problem: &lt;strong&gt;LLMs are killing one of the programmer&amp;rsquo;s most important virtues: laziness.&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
