
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Elite Software Engineer</title>
      <link>https://blog.7x.network/blog</link>
      <description>Building a high performance teams and software</description>
      <language>en-us</language>
      <managingEditor>address@yoursite.com (Mike Camara)</managingEditor>
      <webMaster>address@yoursite.com (Mike Camara)</webMaster>
      <lastBuildDate>Fri, 27 Feb 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://blog.7x.network/tags/coding-agents/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://blog.7x.network/blog/from-violin-player-to-conductor-the-new-software-engineer-in-the-age-of-coding-agents</guid>
    <title>From Violin Player to Conductor: The New Software Engineer in the Age of Coding Agents</title>
    <link>https://blog.7x.network/blog/from-violin-player-to-conductor-the-new-software-engineer-in-the-age-of-coding-agents</link>
    <description>Reid Hoffman makes a specific point that cuts through the noise about AI &quot;replacing developers&quot;: the job does not disappear, but the center of gravity shifts. The software engineer moves away from being primarily a person who types code, and toward being a person who manages multiple coding agents. He compares it to the difference between playing an instrument and conducting an orchestra—the output still becomes music, but the work becomes coordination, direction, and quality control rather than manual performance. This post breaks down his framing, the conductor metaphor, what it means for engineering careers, and how to build the reflex before the shift accelerates.</description>
    <pubDate>Fri, 27 Feb 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (Mike Camara)</author>
    <category>ai</category><category>future-of-work</category><category>software-engineering</category><category>coding-agents</category>
  </item>

  <item>
    <guid>https://blog.7x.network/blog/the-session-pr-reviewing-how-the-code-was-made</guid>
    <title>The Session PR: Reviewing How the Code Was Made, Not Just What Changed</title>
    <link>https://blog.7x.network/blog/the-session-pr-reviewing-how-the-code-was-made</link>
    <description>Today&#39;s pull request is built around a diff. You review what changed, not how it came to be. With coding agents, that model is starting to leak: a clean diff can hide a messy session, skipped constraints, or a plan that was wrong for three iterations before it was right. This post explores a new kind of PR — one where the artifact under review is the agent session itself: the prompts, the tool calls, the rejected paths, the plan, and the human&#39;s choices along the way. It compares the idea to existing practices like AI review bots, stacked diffs, build provenance, and &quot;session provenance&quot;, and argues that making the session the primary review surface is genuinely new — and probably inevitable.</description>
    <pubDate>Mon, 04 May 2026 14:00:00 GMT</pubDate>
    <author>address@yoursite.com (Mike Camara)</author>
    <category>ai</category><category>coding-agents</category><category>code-review</category><category>pull-requests</category><category>agentic-engineering</category><category>software-engineering</category>
  </item>

    </channel>
  </rss>
