<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>scale on My learning and diary</title>
    <link>https://jackliusr.github.io/tags/scale/</link>
    <description>Recent content in scale on My learning and diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 25 Sep 2026 20:00:00 +0800</lastBuildDate><atom:link href="https://jackliusr.github.io/tags/scale/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI at scale in another sense with agent &#43; sandbox &#43; self-evolving &#43; PTC</title>
      <link>https://jackliusr.github.io/posts/2026/09/ai-at-scale-in-another-sense-with-agent--sandbox--self-evolving--ptc/</link>
      <pubDate>Fri, 25 Sep 2026 20:00:00 +0800</pubDate>
      
      <guid>https://jackliusr.github.io/posts/2026/09/ai-at-scale-in-another-sense-with-agent--sandbox--self-evolving--ptc/</guid>
      <description>When talking about AI at scale, I have always thought about it from the model-serving infrastructure perspective:
 How many GPUs do we need? How do we scale inference? How do we reduce latency and cost? How do we serve millions of concurrent requests? How do we efficiently distribute models across GPU clusters?  But there is another way to think about AI at scale.
Instead of scaling the AI model itself, what if we scale software development across ordinary users?</description>
    </item>
    
  </channel>
</rss>
