<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>apeg.dev</title>
<link>https://apeg.dev/</link>
<atom:link href="https://apeg.dev/feed.xml" rel="self" type="application/rss+xml"/>
<description>Forward deployed engineering, agentic AI and CPU inference, written from real engagements and measured results. By Arun Prasath E G.</description>
<language>en-us</language>
<lastBuildDate>Tue, 15 Sep 2026 09:00:00 GMT</lastBuildDate>
<image><url>https://apeg.dev/logo.png</url><title>apeg.dev</title><link>https://apeg.dev/</link></image>
<item>
<title>Forward deployed engineering: how the engagement actually runs</title>
<link>https://apeg.dev/forward-deployed-engineer/how-it-runs/</link>
<guid isPermaLink="true">https://apeg.dev/forward-deployed-engineer/how-it-runs/</guid>
<pubDate>Mon, 14 Sep 2026 09:00:00 GMT</pubDate>
<dc:creator>Arun Prasath E G</dc:creator>
<description>Forward deployed engineering as an operating model, from the records of real engagements: what is written before day one, what ships every week, how the build stays safe at speed, how credentials and platform rules are handled, what the handover contains, and when the model does not fit.</description>
<enclosure url="https://apeg.dev/forward-deployed-engineer/how-it-runs/og.png" type="image/png" length="0"/>
</item>
<item>
<title>What is a forward deployed engineer?</title>
<link>https://apeg.dev/forward-deployed-engineer/</link>
<guid isPermaLink="true">https://apeg.dev/forward-deployed-engineer/</guid>
<pubDate>Mon, 14 Sep 2026 09:00:00 GMT</pubDate>
<dc:creator>Arun Prasath E G</dc:creator>
<description>A forward deployed engineer builds the AI system inside the customer's business, with the customer's data, under the customer's rules. What the job actually is, from someone who does it.</description>
<enclosure url="https://apeg.dev/forward-deployed-engineer/og.png" type="image/png" length="0"/>
</item>
<item>
<title>What a forward deployed engineer does inside your company</title>
<link>https://apeg.dev/forward-deployed-engineer/for-owners/</link>
<guid isPermaLink="true">https://apeg.dev/forward-deployed-engineer/for-owners/</guid>
<pubDate>Mon, 14 Sep 2026 09:00:00 GMT</pubDate>
<dc:creator>Arun Prasath E G</dc:creator>
<description>What changes in the first month, what the owner is asked to decide, what the owner is not asked to do, and what the owner's team owns at the end. From the decisions files and handover documents of real engagements.</description>
<enclosure url="https://apeg.dev/forward-deployed-engineer/for-owners/og.png" type="image/png" length="0"/>
</item>
<item>
<title>AI in retail: what actually gets built inside a retail chain</title>
<link>https://apeg.dev/forward-deployed-engineer/retail/</link>
<guid isPermaLink="true">https://apeg.dev/forward-deployed-engineer/retail/</guid>
<pubDate>Mon, 14 Sep 2026 09:00:00 GMT</pubDate>
<dc:creator>Arun Prasath E G</dc:creator>
<description>What AI in retail looks like from inside a retail chain's operating platform: the data reconciliation that comes before any model, the monthly forecast worked by hand, the five feeds that make it store-aware, the model ladder, open-to-buy, and where AI is the wrong call.</description>
<enclosure url="https://apeg.dev/forward-deployed-engineer/retail/og.png" type="image/png" length="0"/>
</item>
<item>
<title>Forward deployed engineer vs solutions engineer vs sales engineer vs solutions architect</title>
<link>https://apeg.dev/forward-deployed-engineer/vs-solutions-engineer/</link>
<guid isPermaLink="true">https://apeg.dev/forward-deployed-engineer/vs-solutions-engineer/</guid>
<pubDate>Mon, 14 Sep 2026 09:00:00 GMT</pubDate>
<dc:creator>Arun Prasath E G</dc:creator>
<description>The four roles side by side: when each one works, what each one owns, and which one you actually need. Plus how a forward deployed engineer differs from a software engineer and an AI engineer.</description>
<enclosure url="https://apeg.dev/forward-deployed-engineer/vs-solutions-engineer/og.png" type="image/png" length="0"/>
</item>
<item>
<title>Self-hosted LLM: what keeping your data in the building actually requires</title>
<link>https://apeg.dev/writing/self-hosted-llm-without-a-gpu/</link>
<guid isPermaLink="true">https://apeg.dev/writing/self-hosted-llm-without-a-gpu/</guid>
<pubDate>Fri, 11 Sep 2026 09:00:00 GMT</pubDate>
<dc:creator>Arun Prasath E G</dc:creator>
<description>A self-hosted LLM is the answer when your data cannot leave the building. What leaves in a normal deployment, the four ways to keep it in, how to size by workload rather than by model, which open-weight models fit, what it costs to run after day one, and when self-hosting is the wrong call.</description>
<enclosure url="https://apeg.dev/writing/self-hosted-llm-without-a-gpu/og.png" type="image/png" length="0"/>
</item>
<item>
<title>Running Gemma-4 26B at 124 tokens/sec on a CPU, no GPU</title>
<link>https://apeg.dev/writing/running-gemma4-26b-on-a-cpu/</link>
<guid isPermaLink="true">https://apeg.dev/writing/running-gemma4-26b-on-a-cpu/</guid>
<pubDate>Tue, 30 Jun 2026 09:00:00 GMT</pubDate>
<dc:creator>Arun Prasath E G</dc:creator>
<description>A 26B mixture-of-experts model on a desktop CPU with no graphics card: about 40 tokens/sec single-stream lossless, about 124 aggregate when batched. The byte budget, the quantization recipe, the measured memory bandwidth, the dead ends, and the exact commands to reproduce it.</description>
<enclosure url="https://apeg.dev/writing/running-gemma4-26b-on-a-cpu/og.png" type="image/png" length="0"/>
</item>
</channel>
</rss>
