<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>History on Harlan D. Harris</title><link>https://harlanh.tech/tags/history/</link><description>Recent content in History on Harlan D. Harris</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>harlan.harris@gmail.com (Harlan Harris)</managingEditor><webMaster>harlan.harris@gmail.com (Harlan Harris)</webMaster><lastBuildDate>Wed, 18 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://harlanh.tech/tags/history/index.xml" rel="self" type="application/rss+xml"/><item><title>IZE meets AI -- semantic search, smarter labels, and agentic orientation</title><link>https://harlanh.tech/2026/03/ize-meets-ai-semantic-agentic-search/</link><pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/03/ize-meets-ai-semantic-agentic-search/</guid><description>
&lt;p&gt;This is the last post in the &lt;a href="https://harlanh.tech/2026/02/ize-revisiting-hierarchical-search-technology-pc-era/"&gt;IZE series&lt;/a&gt;. In the &lt;a href="https://harlanh.tech/2026/03/generalize-ize-hierarchies/"&gt;previous installment&lt;/a&gt;, I looked at two ways to generalize the IZE algorithm itself: preferring consistent facets and searching for trees with better goodness scores. Here I want to ask a different question: what does the AI revolution of the last few years actually change about what could be built here?&lt;/p&gt;
&lt;p&gt;I see three distinct opportunities, at different layers of the system.&lt;/p&gt;</description></item><item><title>Could We Build IZE Again?</title><link>https://harlanh.tech/2026/03/could-we-build-ize-again/</link><pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/03/could-we-build-ize-again/</guid><description>
&lt;p&gt;In the &lt;a href="https://harlanh.tech/2026/03/what-came-after-ize-three-domains-three-answers/"&gt;previous installment of this series&lt;/a&gt;, I looked at what came after IZE -- faceted search, clustering algorithms, and the various ways web search, personal information management, and e-commerce tried to solve similar problems to what IZE was attacking. None of them ended up doing what IZE did. The question I want to take up here is: could we build something like IZE today? I think the answer is yes, for at least one domain. IZE's hierarchical search algorithm is worth revisiting for e-commerce operators with medium-to-large catalogs who want to help new customers orient themselves. Modern catalog metadata makes it easier to implement than ever.&lt;/p&gt;</description></item><item><title>What Came After IZE? Three Domains, Three Answers</title><link>https://harlanh.tech/2026/03/what-came-after-ize-three-domains-three-answers/</link><pubDate>Wed, 04 Mar 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/03/what-came-after-ize-three-domains-three-answers/</guid><description>
&lt;p&gt;In the &lt;a href="https://harlanh.tech/2026/02/how-ize-really-worked-patents-limits-esther-dyson/"&gt;previous post in this series&lt;/a&gt;, I discussed the technical details of IZE and its reception. Here I want to look at what came after — and where IZE-like ideas might still have potential.&lt;/p&gt;
&lt;p&gt;The short version: IZE was forgotten, but the ideas it embodied — hierarchical clustering, single-word splits, dynamic navigation — were re-invented independently in several different domains. Each domain found a different answer, for reasons that are worth understanding.&lt;/p&gt;</description></item><item><title>How IZE Really Worked - Algorithm, Patent, Limits, and Esther Dyson</title><link>https://harlanh.tech/2026/02/how-ize-really-worked-patents-limits-esther-dyson/</link><pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/02/how-ize-really-worked-patents-limits-esther-dyson/</guid><description>
&lt;p&gt;In the &lt;a href="https://harlanh.tech/2026/02/ize-revisiting-hierarchical-search-technology-pc-era/"&gt;first post in this series&lt;/a&gt;, I introduced IZE -- a DOS-era personal information manager with a novel approach to search and navigation. Here I want to go deeper into how it actually worked, what its limits were, and how it was received at the time.&lt;/p&gt;
&lt;h2 id="the-algorithm"&gt;The algorithm&lt;/h2&gt;
&lt;p&gt;The core of IZE was &lt;a href="https://patents.google.com/patent/US5062074A/en"&gt;patented&lt;/a&gt; by Paul Kleinberger (US5062074A, &amp;quot;Information retrieval system and method&amp;quot;). The basic algorithm is easy enough to describe:&lt;/p&gt;</description></item><item><title>IZE - Revisiting a hierarchical search technology from the PC era</title><link>https://harlanh.tech/2026/02/ize-revisiting-hierarchical-search-technology-pc-era/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><author>harlan.harris@gmail.com (Harlan Harris)</author><guid>https://harlanh.tech/2026/02/ize-revisiting-hierarchical-search-technology-pc-era/</guid><description>
&lt;p&gt;Sometimes revisiting old technology is the best way to understand how we got where we are -- and to see what alternative paths might have looked like. This is the first in a series of posts about &lt;a href="https://en.wikipedia.org/wiki/Persoft#:~:text=In%201987%2C%20the%20company%20acquired%20the%20rights%20to%20IZE"&gt;IZE&lt;/a&gt;,
a DOS-era personal information manager that I think has some interesting lessons for modern search and discovery.&lt;/p&gt;
&lt;p&gt;I'll admit my interest in IZE isn't purely academic. My father was a co-founder of the company that published it, and a cousin of his was the inventor of the underlying technology, which the company acquired. So I grew up with IZE around the house, and owned the polo shirt. That said, I think it's genuinely interesting on its own merits, and I'll try to make the case for that here.&lt;/p&gt;</description></item></channel></rss>