<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title type="text">Andy Fitzgerald Consulting — Notes</title>
  <subtitle type="text">Short notes, clippings and book notes related to information architecture and structured content design for the modern web.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://preview.andyfitzgeraldconsulting.com/insights/feed-notes.xml"/>
  <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/"/>
  <id>https://preview.andyfitzgeraldconsulting.com/insights/feed-notes.xml</id>
  <updated>2026-11-05T00:00:00Z</updated>
  <author>
    <name>Andy Fitzgerald</name>
  </author>
  <entry>
    <title type="text">Taxonomy Manager Tree View Improvements</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/taxonomy-manager-tree-view-improvements/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/taxonomy-manager-tree-view-improvements/</id>
    <published>2026-11-05T00:00:00Z</published>
    <updated>2026-11-05T00:00:00Z</updated>
    <summary type="text">Usability and management enhancements for iterating and evolving your taxonomies in Sanity Studio</summary>
    <category term="Project Note"/>
    <category term="Taxonomy"/>
    <category term="Sanity"/>
    <content type="html">&lt;p&gt;This week I released a new version of the Taxonomy Manager plugin. It includes usability and management features that should make iterating and evolving your taxonomies in Sanity Studio easier:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;Tree view now supports drag and drop hierarchy editing&lt;/li&gt;&lt;li&gt;Top level concepts can be promoted to or demoted from &amp;quot;Top Concept&amp;quot; in the tree view&lt;/li&gt;&lt;li&gt;You can now add existing concepts as well as create new concepts from the tree view&lt;/li&gt;&lt;li&gt;Publication status is now included in the tree view&lt;/li&gt;&lt;li&gt;Concepts open for editing are highlighted in the tree view to help you easily spot where they are in the hierarchy&lt;/li&gt;&lt;li&gt;Content Releases are supported for those on qualifying Enterprise plans&lt;/li&gt;&lt;/ul&gt;&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/ed26a2f5d14f58d8405e619161a22b98e1283b33-3024x1898.png?rect=118,228,2906,1670&amp;amp;w=1200&amp;amp;auto=format&quot; width=&quot;1200&quot; height=&quot;690&quot; alt=&quot;A multicolumn view of the Sanity Taxonomy Manager plugin showing concept scheme and concept lists, a hierarchy view of the selected taxonomy, and a detail view of the selected term. &quot; /&gt;&lt;figcaption&gt;Sanity Taxonomy Manager Plugin version 6.2.0&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;This update was built with accessibility in mind from the start: the mouse-based interaction is an enhancement of functionality you&amp;#x27;ll find in the overflow menu for each concept, which offers full support for keyboard and screen reader users.&lt;/p&gt;&lt;p&gt;These features also support you freewheeling polyhierarchy enthusiasts out there. Concepts that appear in multiple places in the same hierarchy can be moved independently of each other, and when the concept is open you&amp;#x27;ll see a highlight on both instances (or more ... though good luck with that!)&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://preview.andyfitzgeraldconsulting.com/projects/#sanity-taxonomy-manager&quot;&gt;Read more about the Sanity Taxonomy Manager plugin&lt;/a&gt; &lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">Designing and Implementing Semantic Data Layers</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/designing-and-implementing-semantic-data-layers/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/designing-and-implementing-semantic-data-layers/</id>
    <published>2026-10-19T00:00:00Z</published>
    <updated>2026-10-19T00:00:00Z</updated>
    <summary type="text">A practical, actionable, architectural approach to making meaning explicit, consistent and durable.</summary>
    <category term="Book Note"/>
    <category term="Semantic Web"/>
    <category term="Interoperability"/>
    <category term="Technology Integration"/>
    <category term="Data Management"/>
    <content type="html">&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/3d26476b6785a9f620571be25ef48f8c22735899-334x500.png?bg=e82976&amp;amp;w=952&amp;amp;h=500&amp;amp;fit=fill&amp;amp;auto=format&quot; width=&quot;952&quot; height=&quot;500&quot; alt=&quot;Designing and Implementing Semantic Data Layers book cover&quot; /&gt;&lt;figcaption&gt;&lt;a href=&quot;https://www.goodreads.com/book/show/255520401&quot;&gt;Designing and Implementing Semantic Data Layers&lt;/a&gt;, by Dave Wells. Technics Publications, 2026&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;Aligning meaning across systems is a perennial enterprise problem. Tools get added, systems diverge, abstraction layers are “optimized” for pressing use cases, and shortcuts are taken. And that’s before mergers, market pivots, and shifts in strategy. &lt;/p&gt;&lt;p&gt;The result is a growing collection of what different people and systems mean when they say “customer,” “department,” or “protocol.” Dave Wells offers a practical, actionable solution using semantic layers: “a systematic, architectural approach to making meaning explicit, consistent and durable” (121).&lt;/p&gt;&lt;h2 id=&quot;key-concepts&quot;&gt;Key Concepts&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;“Trust in data is not a sentiment. It’s a capability, and semantics is how you build it” (12).&lt;/li&gt;&lt;li&gt;Separation of meaning from structure is crucial for building semantic layers that scale (21). &lt;/li&gt;&lt;li&gt;Definitions are required: “A model without definitions is only a diagram. A model with definitions is a semantic artifact” (46).&lt;/li&gt;&lt;li&gt;The hard work of aligning on definitions is organizational and interpersonal. “Getting subject matter experts to agree on a single definition of &lt;em&gt;customer&lt;/em&gt;” is challenging, but necessary — and can make the difference between an initiative that succeeds and one that stalls (88).&lt;/li&gt;&lt;li&gt;“A semantics-based architecture is not a single semantic layer [but rather a] deliberate network of semantic layers, each serving a specific purpose” (96). &lt;/li&gt;&lt;li&gt;Start small; provide value at each stage: “Incremental delivery is not a compromise. It is the right strategy” (120). &lt;/li&gt;&lt;/ul&gt;&lt;h2 id=&quot;impressions&quot;&gt;Impressions&lt;/h2&gt;&lt;p&gt;This is a brief book (122pp) packed with actionable ideas and strategies. Wells makes a convincing case for why semantic layers are more important now than ever, introduces the core concepts, then gets into the details of five kinds of semantic layers and their respective purposes. He then uses relatable use cases to illustrate how these layers are implemented across typical enterprise data systems. &lt;/p&gt;&lt;p&gt;A running theme is that you don’t create “a” semantic layer; you need an overlapping and interconnected set of layers that are designed and governed to achieve specific outcomes. Wells provides rubrics for choosing which types of layers are best suited for common outcomes. &lt;/p&gt;&lt;p&gt;Wells provides a brief introduction to semantic technology concepts, like RDF triples and ontologies, but if these are new concepts to you a more expansive introduction to the nuts and bolts of knowledge graphs might help you envision the practical applications more concretely. As Wells emphasizes throughout, however, the strategy he describes is “not a technology product. It’s a discipline, practiced through careful modeling, governed through clear ownership, and sustained through organizational commitment” (121). &lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">The Calm Before the Storm</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/the-calm-before-the-storm/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/the-calm-before-the-storm/</id>
    <published>2026-09-19T00:00:00Z</published>
    <updated>2026-09-19T00:00:00Z</updated>
    <summary type="text">Geoff Teehan on the particular moment we’re in with AI assisted software creation: developer scarcity is fading, but we still don&apos;t understand what abundance looks like. </summary>
    <category term="Web Clipping"/>
    <category term="AI Integration"/>
    <category term="Project Management"/>
    <content type="html">&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/43dc886abb7d72a9ee00fe02a973be8f4c1607ab-480x252.png?rect=32,0,448,252&amp;amp;w=448&amp;amp;h=252&amp;amp;fit=crop&amp;amp;auto=format&quot; width=&quot;448&quot; height=&quot;252&quot; alt=&quot;Margaret Hamilton with the Apollo Guidance Computer listings, 196&quot; /&gt;&lt;figcaption&gt;&lt;a href=&quot;https://design.lightspark.com/we-built-companies-around-the-cost-of-building&quot;&gt;We Built Companies Around the Cost of Building&lt;/a&gt;, lightspark.com&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;Geoff Teehan on the particular moment we’re in with AI assisted software creation:&lt;/p&gt;&lt;blockquote&gt;When digital cameras showed up, people used them like film cameras. Same pictures, they just stopped paying to develop them. Nobody was photographing their parking spot yet. That’s about where software is. Faster development is the same pictures without the developing costs. The parking-spot phase hasn’t started.&lt;/blockquote&gt;&lt;p&gt;Are we really prepared for a world where software creation requires the same amount of forethought as taking “fourteen nearly identical photographs of your lunch”? We’re soon to find out!&lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">Why Shortcuts Aren&apos;t the Road</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/why-shortcuts-arent-the-road/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/why-shortcuts-arent-the-road/</id>
    <published>2026-09-04T00:00:00Z</published>
    <updated>2026-09-04T00:00:00Z</updated>
    <summary type="text">As with most shortcuts, there’s a reason that the road isn’t laid down that way.</summary>
    <category term="Web Clipping"/>
    <category term="User Research"/>
    <category term="Project Management"/>
    <content type="html">&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/e217d4862260bb5a3a43094bbf0f45579e925e16-480x282.png?rect=0,6,480,270&amp;amp;w=480&amp;amp;h=270&amp;amp;fit=crop&amp;amp;auto=format&quot; width=&quot;480&quot; height=&quot;270&quot; alt=&quot;Product Picnic label superimposed over a drawing of an orange and an apple. &quot; /&gt;&lt;figcaption&gt;&lt;a href=&quot;https://productpicnic.beehiiv.com/p/taste-is-a-dead-end&quot;&gt;Taste is a dead end; what you should have is a point of view&lt;/a&gt;, productpicnic&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;Pavel Samsonov on the perils of “fake research”: &lt;/p&gt;&lt;blockquote&gt;As with most shortcuts, there’s a reason that the road isn’t laid down that way.&lt;/blockquote&gt;&lt;p&gt;Yes, by “fake” he means research an LLM made up. &lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">SHACL for the Practitioner</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/shacl-for-the-practitioner/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/shacl-for-the-practitioner/</id>
    <published>2025-11-15T00:00:00Z</published>
    <updated>2025-11-15T00:00:00Z</updated>
    <summary type="text">A non-academic introduction to SHACL with rich examples and real-world real world case studies. </summary>
    <category term="Book Note"/>
    <category term="Knowledge Graphs"/>
    <content type="html">&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/a7c9fad0b6caf074b7a9c704ece994b317e409ef-284x400.png?bg=c1c0c2&amp;amp;w=761&amp;amp;h=400&amp;amp;fit=fill&amp;amp;auto=format&quot; width=&quot;761&quot; height=&quot;400&quot; alt=&quot;SHACL for the Practitioner front cover&quot; /&gt;&lt;figcaption&gt;&lt;a href=&quot;https://www.goodreads.com/book/show/245855210-shacl-for-the-practitioner&quot;&gt;SHACL for the Practitioner&lt;/a&gt;, by Veronika Heimsbakk. Self-published, 2025&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;SHACL is the World Wide Web Consortium’s (W3C) standard for validating semantic web data. Standards like RDFS and OWL use inference to discover “new” information in graph data based on logical implications and “open world” assumptions. SHACL allows practitioners to constrain the conclusions semantic inference can draw based on established rules for graph entities and attributes. &lt;/p&gt;&lt;h2 id=&quot;key-concepts&quot;&gt;Key Concepts&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;SHACL can be used to catch logical inferences that are “correct” according to your semantic model, but make no sense in the real world.&lt;/li&gt;&lt;li&gt;SHACL is complementary to OWL, not a replacement for it (35). &lt;/li&gt;&lt;li&gt;SHACL doesn’t change your graph. When run, the SHACL engine delivers a report detailing constraint violations (76).&lt;/li&gt;&lt;li&gt;Most commercial semantic web tools support core SHACL constraints, though their implementation of the full standard still varies. &lt;/li&gt;&lt;/ul&gt;&lt;h2 id=&quot;impressions&quot;&gt;Impressions&lt;/h2&gt;&lt;p&gt;My enthusiasm for this (admittedly niche) topic is twofold: First, &lt;em&gt;SHACL for the Practitioner&lt;/em&gt; means that we now have a complete set of approachable, reader-friendly books for the semantic web technologies that form the foundations of knowledge graphs (RDFS, OWL, SPARQL, SHACL).&lt;br/&gt;&lt;br/&gt;Second, Veronika&amp;#x27;s clear, accessible style takes what could quickly become a technically obtuse topic and frames it as a pragmatic, down to earth complement to OWL and RDFS.&lt;br/&gt;&lt;br/&gt;While SHACL isn&amp;#x27;t otherwise a starting place I would recommend to someone new to semantic web technologies, part one of this book, &amp;quot;Back to Basics&amp;quot;, is hands down the clearest holistic overview I&amp;#x27;ve seen of what the semantic stack seeks to accomplish and how the technologies fit together. Even if you need to come back to the rest of the book for a second pass after you&amp;#x27;ve covered the other technologies elsewhere, this initial framing provides an admirable map for the rest of the semantic web territory.&lt;br/&gt;&lt;br/&gt;Parts two and three provide an introduction to the nuts and bolts of designing, writing, and applying SHACL to validate data (of course), and then a selection of real-world case studies (&amp;quot;SHACL Stories&amp;quot;) that illustrate the wide variety of applications for which SHACL provides practical data validation at scale. The coverage of SHACL shapes and constraints is concise and to-the-point, and kept relatable with a common example throughout. Some of the case studies were more accessible to me than others, but I suspect this is just right: everyone will bring their own background and experience to these stories, and there&amp;#x27;s a range of topics here to accommodate that.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">Designing Content Authoring Experiences</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/designing-content-authoring-experiences/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/designing-content-authoring-experiences/</id>
    <published>2025-03-15T00:00:00Z</published>
    <updated>2025-03-15T00:00:00Z</updated>
    <summary type="text">Well designed authoring experiences make doing the right things easy and doing the wrong things hard.</summary>
    <category term="Book Note"/>
    <category term="Governance"/>
    <category term="Structured Content"/>
    <content type="html">&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/daf74a7c6ebd55a9e8078d07113c9f1fe60682f0-324x500.png?bg=e9eaea&amp;amp;w=952&amp;amp;h=500&amp;amp;fit=fill&amp;amp;auto=format&quot; width=&quot;952&quot; height=&quot;500&quot; alt=&quot;Front cover of Designing Content Authoring Experiences&quot; /&gt;&lt;figcaption&gt;&lt;a href=&quot;https://www.goodreads.com/book/show/223598420-designing-content-authoring-experiences&quot;&gt;Designing Content Authoring Experiences&lt;/a&gt;, by Greg Dunlap. Splash Hit Publishing, 2025&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;&lt;em&gt;Designing Content Authoring Experiences&lt;/em&gt; centers on learning who your users are and how they operate, then designing workflows that make it easy for them to create quality, well-structured content (and that make it difficult to create inchoate jumbles of wordmess). Crucially, Greg Dunlap also provides examples aplenty of what this looks like in practice and methods for how designers can work with authors and stakeholders to achieve these ends in the design process.&lt;/p&gt;&lt;h2 id=&quot;key-concepts&quot;&gt;Key Concepts&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;Good author experience design requires a careful balance of structure and flexibility (19).&lt;/li&gt;&lt;li&gt;“Unless designed very carefully, page builders and block-based editors remove the content’s semantic meaning” (27).&lt;/li&gt;&lt;li&gt;“Removing flexibility is &lt;em&gt;always &lt;/em&gt;harder than adding it. […] Authors will always ask for more” (33).&lt;/li&gt;&lt;li&gt;Authoring tools should focus on making “doing the right things easy and doing the wrong things hard” (45).&lt;/li&gt;&lt;li&gt;A CMS is not a writing tool; it’s a publishing tool (128).&lt;/li&gt;&lt;li&gt;Don’t forget to design training! (131)&lt;/li&gt;&lt;/ul&gt;&lt;h2 id=&quot;impressions&quot;&gt;Impressions&lt;/h2&gt;&lt;p&gt;The book&amp;#x27;s examples focus on CMS design, but the insights they provide aren’t limited to those contexts. CMS use cases are legion and there is clearly a lot designers can do to make those experiences better. This book isn&amp;#x27;t about the technical details of any one system, however, and advice for adapting established patterns to user needs focuses on the user needs, not the patterns themselves. It&amp;#x27;s hard to say how CMS design and functionality will evolve over the next few years, but the need for human-friendly ways to interact with those systems will undoubtedly remain.&lt;br/&gt;&lt;br/&gt;Dunlap and his editors have done the hard work of making this book short, engaging, and actionable. In the spirit of the A Book Apart (RIP) publications, this is a brief book for people who make things that can be read over a weekend (or in one sitting if you&amp;#x27;re a fast reader—I&amp;#x27;m not). Having read a few ponderous and wandering tomes in my time, I am grateful for the effort that goes into creating short work that is direct and to the point.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">Proust and the Squid</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/proust-and-the-squid/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/proust-and-the-squid/</id>
    <published>2016-07-28T00:00:00Z</published>
    <updated>2016-07-28T00:00:00Z</updated>
    <summary type="text">Learning to read creates physical changes in the brain that directly affect  how we think.</summary>
    <category term="Book Note"/>
    <category term="Mental Models"/>
    <content type="html">&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/4909fb6d6cd243dd765a0fda6d9f34e63e0650e7-600x904.jpg?bg=646454&amp;amp;w=1200&amp;amp;h=630&amp;amp;fit=fill&amp;amp;auto=format&quot; width=&quot;1200&quot; height=&quot;630&quot; alt=&quot;Book cover for Proust and the Squid&quot; /&gt;&lt;figcaption&gt;&lt;a href=&quot;https://www.goodreads.com/book/show/289751.Proust_and_the_Squid&quot;&gt;Proust and the Squid&lt;/a&gt;, by Maryanne Wolf. Houghton Mifflin, 2007&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;The process of learning to read creates physical changes in the brain that directly affect how that brain works and how we think. Understanding this process (neuroplasticity) in the reading brain prepares us to better understand the changes we’re currently undergoing as we “make the transition from a reading brain to an increasingly digital one.”&lt;/p&gt;&lt;h2 id=&quot;key-concepts&quot;&gt;Key Concepts&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;The efficient reading brain — which takes years to develop — literally has “more time to think” (54).&lt;/li&gt;&lt;li&gt;Contrary to spoken language, “there are neither genes nor biological structures specific only to reading. Instead, in order to read, each brain must learn to make new circuits by connecting older regions originally designed and genetically programmed for other things” (168).&lt;/li&gt;&lt;li&gt;“The new circuits and pathways that the brain fashions in order to read become the foundations for being able to think in different, innovative ways” (271).&lt;/li&gt;&lt;/ul&gt;&lt;h2 id=&quot;impressions&quot;&gt;Impressions&lt;/h2&gt;&lt;p&gt;The first part of this book focuses on the plasticity of the brain and the ways that learning to read changes it. Wolf illustrates this story with historical accounts of writing in early societies and plenty of good ol’ neuroscience. Later chapters focus more closely on reading development in children and dyslexia before returning in a brief final chapter to the effects of digital technology on how our brains work.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">Gall&apos;s Law When Complexity Comes Cheap</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/galls-law-when-complexity-comes-cheap/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/galls-law-when-complexity-comes-cheap/</id>
    <published>2000-01-01T00:00:00Z</published>
    <updated>2000-01-01T00:00:00Z</updated>
    <summary type="text">AI makes building complexity easy, but the reasons behind beginning with simple systems that work don&apos;t change. </summary>
    <category term="Web Clipping"/>
    <category term="Collaborative Design"/>
    <content type="html">&lt;figure&gt;&lt;img src=&quot;https://cdn.sanity.io/images/7v0qvet6/production-26/cbe0181b1adbcea99419a4636c29db3b26d1b045-480x270.jpg?w=480&amp;amp;h=270&amp;amp;fit=crop&amp;amp;auto=format&quot; width=&quot;480&quot; height=&quot;270&quot; alt=&quot;Jorge Arango&quot; /&gt;&lt;figcaption&gt;&lt;a href=&quot;https://jarango.com/2026/06/26/still-holds-galls-law/&quot;&gt;Still Holds: Gall’s Law&lt;/a&gt;, jarango.com&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;Jorge Arango:&lt;/p&gt;&lt;blockquote&gt;AI removes these constraints. An afternoon with Claude can yield a comprehensive spec for a very complex system. Further sessions can architect the system and build an initial release that includes bells, whistles, timpani, harps, violas, and all the other instruments in the orchestra. All this, at a fraction of the cost and time it would’ve taken in the past.&lt;/blockquote&gt;&lt;p&gt;I love that this theme comes up again in the design of AI systems, that were (supposedly) going to take care of all of this for us.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">On Accountability</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/on-accountability/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/on-accountability/</id>
    <published>2000-01-01T00:00:00Z</published>
    <updated>2000-01-01T00:00:00Z</updated>
    <summary type="text">Where are the cash-backed LLM guarantees?</summary>
    <category term="Note"/>
    <category term="Automation"/>
    <category term="AI Integration"/>
    <content type="html">&lt;p&gt;The day the provider of an LLM-backed service offers a cash guarantee against the potential harm their product could cause your organization if their language model goes off the rails, I’ll worry about the job security of capable, accountable human designers. Until then, I think the thing to do is ride out the chaos of the moment.&amp;nbsp; &lt;/p&gt;</content>
  </entry>
  <entry>
    <title type="text">Sidestepping the Stingy Web</title>
    <link rel="alternate" type="text/html" href="https://preview.andyfitzgeraldconsulting.com/insights/sidestepping-the-stingy-web/"/>
    <id>https://preview.andyfitzgeraldconsulting.com/insights/sidestepping-the-stingy-web/</id>
    <published>2000-01-01T00:00:00Z</published>
    <updated>2000-01-01T00:00:00Z</updated>
    <summary type="text">I&apos;m so over platforms lock-in.</summary>
    <category term="Note"/>
    <category term="Interoperability"/>
    <category term="Digital Communication"/>
    <category term="Digital Presence"/>
    <content type="html">&lt;p&gt;I’ve begun thinking of some products as being &amp;quot;stingy&amp;quot; with sharing. Yes, I’m looking at you, LinkedIn 🧐. These are places that make it hard for me to share &lt;em&gt;my&lt;/em&gt; content (like reviews) in ways that work for me beyond their platform — by, say, providing direct links. Also stingy is how hard it is to find anything again on LinkedIn (being stingy with others&amp;#x27; content as well as my own). This is, surely, because they want you engaged in &amp;quot;the stream.&amp;quot; I don’t fancy it. &lt;/p&gt;&lt;p&gt;This kind of think is why I’m increasingly drawn to RSS and publishing to individual, open sites. The &amp;quot;generous web,&amp;quot; if you will. Or at the very least, as I like to think, the web the way Tim intended it.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Notes&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;A note about sites like LinkedIn being &amp;quot;stingy&amp;quot; with sharing — and allowing me to share &lt;em&gt;my&lt;/em&gt; content (like reviews). By, say, providing direct links. Also how hard it is to find anything again on LinkedIn (being stingy with others&amp;#x27; and my content) — because they want you engaged in &amp;quot;the stream.&amp;quot;&lt;br/&gt;Why I like RSS and publishing to individual, open sites. ... the &amp;quot;generous web&amp;quot;? Or at least, as I like to think, the web the way Tim intended it.&lt;/p&gt;</content>
  </entry>
</feed>
