<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Engineering on Harlan D. Harris</title><link>https://harlanh.tech/tags/software-engineering/</link><description>Recent content in Software-Engineering on Harlan D. Harris</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>harlan@harris.name (Harlan Harris)</managingEditor><webMaster>harlan@harris.name (Harlan Harris)</webMaster><lastBuildDate>Tue, 03 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://harlanh.tech/tags/software-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>How Search and AI Product Teams are Different</title><link>https://harlanh.tech/2026/02/search-and-ai-teams-are-different/</link><pubDate>Tue, 03 Feb 2026 00:00:00 +0000</pubDate><author>harlan@harris.name (Harlan Harris)</author><guid>https://harlanh.tech/2026/02/search-and-ai-teams-are-different/</guid><description>
&lt;p&gt;Engineering leadership knows the standard playbook for product teams: the &lt;a href="https://www.producttalk.org/product-trios/"&gt;Product Trio&lt;/a&gt;, the &lt;a href="https://productschool.com/blog/product-fundamentals/spotify-model-scaling-agile"&gt;Spotify model&lt;/a&gt;, &lt;a href="https://productschool.com/blog/product-strategy/outcome-based-roadmap"&gt;outcome-based roadmaps&lt;/a&gt;, and so on. I've seen teams adopt these practices and still struggle when they add responsibility for advanced algorithms -- search, recommendations, predictive modeling, or generative AI -- without changing how the team is led. The processes and role expectations that work for a typical product team break down when the domain is heavily algorithmic. This post pulls together what I've learned and what others have written about building teams that own these systems.&lt;/p&gt;</description></item><item><title>Insights from a Predictive Model Pipeline Abstraction</title><link>https://harlanh.tech/2016/11/insights-from-a-predictive-model-pipeline-abstraction/</link><pubDate>Mon, 07 Nov 2016 00:00:00 +0000</pubDate><author>harlan@harris.name (Harlan Harris)</author><guid>https://harlanh.tech/2016/11/insights-from-a-predictive-model-pipeline-abstraction/</guid><description>
&lt;p&gt;&lt;em&gt;&lt;a href="https://medium.com/@HarlanH/insights-from-a-predictive-model-pipeline-abstraction-c8b47fd406da"&gt;This post was originally published on Medium&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;When building a complex system, it’s often helpful to think about the design of that system using patterns and abstractions. Architects and software engineers do so frequently, and the experience of implementing predictive modeling pipelines has recently led to a variety of patterns and best practices. For instance, when dealing with large amounts of streaming data, some organizations use the Lambda Architecture to handle both real-time and computationally-intensive use-cases.&lt;/p&gt;</description></item><item><title>Patterns for Connecting Predictive Models to Software Products</title><link>https://harlanh.tech/2016/07/patterns-for-connecting-predictive-models-to-software-products/</link><pubDate>Tue, 12 Jul 2016 00:00:00 +0000</pubDate><author>harlan@harris.name (Harlan Harris)</author><guid>https://harlanh.tech/2016/07/patterns-for-connecting-predictive-models-to-software-products/</guid><description>
&lt;p&gt;&lt;em&gt;&lt;a href="https://medium.com/@HarlanH/patterns-for-connecting-predictive-models-to-software-products-f9b6e923f02d"&gt;This post was originally published on Medium&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;You’re a data scientist, and you’ve got a predictive model — great work! Now what? In many cases, you need to hook it up to some sort of large, complex software product so that users can get access to the predictions. Think of LinkedIn’s People You May Know, which mines your professional graph for unconnected connections, or Hopper’s flight price predictions. Those started out as prototypes on someone’s laptop, and are now running at scale, with many millions of users.&lt;/p&gt;</description></item></channel></rss>