<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Use Cases on E7Coding</title><link>https://www.e7coding.com/en/tags/use-cases/</link><description>Recent content in Use Cases on E7Coding</description><generator>Hugo</generator><language>en</language><managingEditor>Joy</managingEditor><webMaster>Joy</webMaster><lastBuildDate>Mon, 20 Jul 2026 14:00:00 +0800</lastBuildDate><atom:link href="https://www.e7coding.com/en/tags/use-cases/index.xml" rel="self" type="application/rss+xml"/><item><title>Use Cases: How Palantir Lands in Manufacturing, Healthcare, Energy, and Defense</title><link>https://www.e7coding.com/en/posts/palantir-use-cases-patterns/</link><pubDate>Mon, 20 Jul 2026 14:00:00 +0800</pubDate><author>Joy</author><guid>https://www.e7coding.com/en/posts/palantir-use-cases-patterns/</guid><description>&lt;p&gt;&lt;img src="https://www.e7coding.com/images/palantir-supply-chain-action-loop-en.svg" alt="Palantir supply chain action loop: the repeatable pattern behind use cases" loading="lazy" decoding="async" /&gt;
&lt;/p&gt;
&lt;p&gt;The easiest mistake when reading Palantir case studies is to turn them into a customer list.&lt;/p&gt;
&lt;p&gt;This agency used it. This hospital used it. This manufacturer used it. This energy company used it. Those facts matter, but they do not explain the software.&lt;/p&gt;</description></item></channel></rss>