<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Jamal Yusuf</title><link>https://jamal.dev/</link><description>Recent content in Home on Jamal Yusuf</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jamal.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>What My Side Projects Are Really About</title><link>https://jamal.dev/writing/what-my-side-projects-are-really-about/</link><pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/what-my-side-projects-are-really-about/</guid><description>&lt;p&gt;There is a particular kind of silence that arrives after a long day of architecture reviews and compliance checkpoints. The laptop is still warm. The room is dark. And somewhere in the back of my mind, a question starts tapping like a finger on glass: &lt;em&gt;what would it feel like if this were simpler, sharper, more human?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;That is usually when a side project begins.&lt;/p&gt;
&lt;p&gt;I do not build these tools to pad a portfolio. In my view, they are something closer to field notes — small, honest experiments in how software can support the way people actually think, focus, perceive, and play. Some are practical. Some are strange. All of them teach me something I bring back to the serious work.&lt;/p&gt;</description></item><item><title>The Boring Go Layer Between Your RAG Demo and Production</title><link>https://jamal.dev/writing/go-rag-ingestion-pipelines/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/go-rag-ingestion-pipelines/</guid><description>&lt;p&gt;RAG demos are seductive. Chunk a PDF. Embed. Retrieve. Watch the answer sparkle. Applause. Next slide.&lt;/p&gt;
&lt;p&gt;Production RAG is a &lt;strong&gt;pipeline problem&lt;/strong&gt; — documents that change, access policies that differ by team, embeddings that stale, audits that ask where a paragraph came from three quarters ago. The demo never shows that part. The on-call engineer lives there.&lt;/p&gt;
&lt;p&gt;I keep choosing Go for the unglamorous middle between source systems and vector indexes. Not because Python cannot embed. Because &lt;strong&gt;operations is a language choice too&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Validating Agent Outputs in Go Before They Touch Production</title><link>https://jamal.dev/writing/go-validate-agent-outputs/</link><pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/go-validate-agent-outputs/</guid><description>&lt;p&gt;An agent that sounds right is the most dangerous kind of wrong.&lt;/p&gt;
&lt;p&gt;I have seen it in healthcare workflows — confident JSON, clean prose, a downstream system that accepts the payload and only screams twenty minutes later when reconciliation fails. The model did its job. The &lt;strong&gt;system&lt;/strong&gt; failed to treat probability like probability.&lt;/p&gt;
&lt;p&gt;In Go, I fix that with a boring layer between the model and the world: &lt;strong&gt;validate before side effects&lt;/strong&gt;. Always.&lt;/p&gt;</description></item><item><title>Context Is the Kill Switch: Go, Cancellation, and LLM Timeouts</title><link>https://jamal.dev/writing/go-context-llm-timeouts/</link><pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/go-context-llm-timeouts/</guid><description>&lt;p&gt;The first time I watched an agent runaway eat a month&amp;rsquo;s inference budget in an afternoon, nobody blamed the model. They should have blamed &lt;strong&gt;the missing kill switch&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The model kept going because nothing told it to stop. Tool calls chained. Retries compounded. Goroutines — or their equivalent — waited politely for a provider that had already left the building.&lt;/p&gt;
&lt;p&gt;In Go, the kill switch has a name: &lt;code&gt;context.Context&lt;/code&gt;. And I think it is the most underrated tool in production LLM orchestration.&lt;/p&gt;</description></item><item><title>The Case for Sharp Design Systems in 2026</title><link>https://jamal.dev/writing/sharp-design-systems/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/sharp-design-systems/</guid><description>&lt;p&gt;There is a particular kind of interface that smiles at you while hiding its hierarchy.&lt;/p&gt;
&lt;p&gt;Rounded cards. Muted gradients. Friendly empty states. Everything slightly soft, slightly same — as if the design is afraid to tell you where to look first. I kept running into this in professional tools: dashboards that felt approachable until you needed an answer in under ten seconds. Then the softness became noise.&lt;/p&gt;
&lt;p&gt;I named my response &lt;strong&gt;REDLINE&lt;/strong&gt; — a design system for interfaces that &lt;strong&gt;commit&lt;/strong&gt;. Not playful. Not decorative. Not trying to be your friend. Trying to be &lt;strong&gt;clear&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Building Production-Grade AI Agents at Enterprise Scale</title><link>https://jamal.dev/writing/production-ai-agents-enterprise/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/production-ai-agents-enterprise/</guid><description>&lt;p&gt;An agent that cannot reach production systems is not an agent. It is a &lt;strong&gt;demo with ambition&lt;/strong&gt; — and in healthcare, ambition without integration is just risk in a nicer font.&lt;/p&gt;
&lt;p&gt;I learned this leading multi-agent platforms wired into claims, membership, and payment flows — real latency SLAs, real audit requirements, real members on the other end of every invocation.&lt;/p&gt;
&lt;h2 id="integration-over-isolation"&gt;Integration over isolation&lt;/h2&gt;
&lt;p&gt;The value was never &amp;ldquo;another tab with a chat box.&amp;rdquo; Experts wanted help &lt;strong&gt;inside the flow of work&lt;/strong&gt; — grounded in operational context, historical data they could defend, and APIs that did not lie.&lt;/p&gt;</description></item><item><title>Why Go Remains the Best Language for LLM Orchestration</title><link>https://jamal.dev/writing/go-llm-orchestration/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/go-llm-orchestration/</guid><description>&lt;p&gt;I have orchestrated LLM workloads in more than one language. Python gets you to demo fast. Go gets you to &lt;strong&gt;sleep&lt;/strong&gt; — or at least to on-call with fewer surprises.&lt;/p&gt;
&lt;p&gt;That is not ideology. It is fifteen years of distributed systems scar tissue talking.&lt;/p&gt;
&lt;h2 id="the-concurrency-advantage"&gt;The concurrency advantage&lt;/h2&gt;
&lt;p&gt;Agent orchestration is not one request. It is dozens of concurrent flows — tool calls, retrieval hops, validation steps, retries with independent timeout budgets — all competing for resources while a human waits on the other end.&lt;/p&gt;</description></item><item><title>Engineering Leadership in the Age of Generative AI</title><link>https://jamal.dev/writing/engineering-leadership-genai/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/engineering-leadership-genai/</guid><description>&lt;p&gt;The cloud shift asked teams to learn new deployment physics. Generative AI asks something stranger: &lt;strong&gt;learn new collaboration physics&lt;/strong&gt; — with tools that sound confident while being probabilistic, fast while being wrong in creative ways.&lt;/p&gt;
&lt;p&gt;Leading through that shift is not a tooling problem dressed up as strategy. It is a learning problem at organizational scale.&lt;/p&gt;
&lt;h2 id="lead-with-curiosity-not-fear"&gt;Lead with curiosity, not fear&lt;/h2&gt;
&lt;p&gt;I have seen two failure modes up close. Blanket restriction — &amp;ldquo;no AI until Legal finishes a novel.&amp;rdquo; Unchecked adoption — &amp;ldquo;ship the chatbot, ask forgiveness later.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Why Most Enterprise AI Agents Fail</title><link>https://jamal.dev/writing/why-enterprise-ai-agents-fail/</link><pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/why-enterprise-ai-agents-fail/</guid><description>&lt;p&gt;I have watched smart teams ship impressive agent demos — and then watch those same agents fail the only test that matters: &lt;strong&gt;would an expert trust this under pressure?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The model is rarely the villain. The retrieval design is.&lt;/p&gt;
&lt;h2 id="the-expert-retrieval-gap"&gt;The expert retrieval gap&lt;/h2&gt;
&lt;p&gt;Most enterprise AI agents are built around a comforting pipeline: chunk, embed, retrieve, generate. It looks scientific. It scales on slides. It also assumes experts think in paragraphs — flat, interchangeable, equally worthy of attention.&lt;/p&gt;</description></item><item><title>The Go Advantage for Production Agentic Systems</title><link>https://jamal.dev/writing/go-advantage-agentic-systems/</link><pubDate>Wed, 10 Dec 2025 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/go-advantage-agentic-systems/</guid><description>&lt;p&gt;Agentic systems are distributed systems wearing a chat costume. The sooner you accept that, the fewer 3 a.m. pages you earn.&lt;/p&gt;
&lt;p&gt;I have been building Go backends since 2011 — Kafka pipelines, membership APIs, payment flows, the unglamorous center of enterprise operations. When multi-agent workflows arrived, I did not reach for a new religion. I reached for &lt;strong&gt;the same primitives that kept the event backbone alive&lt;/strong&gt;.&lt;/p&gt;
&lt;h2 id="why-go-for-agent-orchestration"&gt;Why Go for agent orchestration&lt;/h2&gt;
&lt;p&gt;Multi-agent workflows are coordination problems: fan-out, join, timeout budgets, partial failure, human escalation. Go&amp;rsquo;s concurrency model — goroutines, channels, context cancellation — maps to those problems without pretending parallelism is free.&lt;/p&gt;</description></item><item><title>Governing GenAI at Scale</title><link>https://jamal.dev/writing/governing-genai-at-scale/</link><pubDate>Sat, 22 Nov 2025 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/governing-genai-at-scale/</guid><description>&lt;p&gt;Governance has a branding problem. Say the word in an engineering standup and watch shoulders drop. I understand why — too often it means slow reviews, vague anxiety, and a PDF no one read.&lt;/p&gt;
&lt;p&gt;But here is the reframe that actually worked in healthcare: &lt;strong&gt;good governance is a force multiplier&lt;/strong&gt;. When teams know the guardrails, they move faster inside them. Ambiguity is what kills velocity.&lt;/p&gt;
&lt;h2 id="governance-is-enablement"&gt;Governance is enablement&lt;/h2&gt;
&lt;p&gt;In regulated environments, governance is not about saying no. It is about creating &lt;strong&gt;safe paths to yes&lt;/strong&gt; — predictable tiers, instrumented controls, and clarity about what Tuesday&amp;rsquo;s compliance conversation will look like.&lt;/p&gt;</description></item><item><title>LLM Governance Framework</title><link>https://jamal.dev/work/ai-systems/llm-governance-framework/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/ai-systems/llm-governance-framework/</guid><description>A practical governance model for responsible GenAI adoption in regulated healthcare — clear enough to speed teams up, rigorous enough to survive audit season.</description></item><item><title>Enterprise Agent Platform</title><link>https://jamal.dev/work/ai-systems/enterprise-agent-platform/</link><pubDate>Mon, 01 Sep 2025 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/ai-systems/enterprise-agent-platform/</guid><description>Designing and deploying a multi-agent platform integrated with real-time healthcare data pipelines — where agents earn trust the same way APIs do, one observable invocation at a time.</description></item><item><title>Engineering Governance at Scale</title><link>https://jamal.dev/work/leadership/engineering-governance/</link><pubDate>Wed, 01 Jan 2025 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/leadership/engineering-governance/</guid><description>Building governance frameworks that accelerate delivery without sacrificing reliability — guardrails clear enough that teams run, not stumble.</description></item><item><title>GenAI Team Transformation</title><link>https://jamal.dev/work/leadership/genai-team-transformation/</link><pubDate>Thu, 01 Aug 2024 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/leadership/genai-team-transformation/</guid><description>Leading enterprise-wide Generative AI adoption through training, enablement, and cultural change — because tools do not transform teams; learning loops do.</description></item><item><title>Databricks Lakehouse Platform</title><link>https://jamal.dev/work/platforms/databricks-lakehouse/</link><pubDate>Fri, 01 Mar 2024 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/platforms/databricks-lakehouse/</guid><description>Enterprise lakehouse strategy unifying analytics, ML, and GenAI workloads on a governed data foundation — because agents are only as honest as the data they retrieve.</description></item><item><title>Kafka Event Backbone</title><link>https://jamal.dev/work/platforms/kafka-event-backbone/</link><pubDate>Thu, 01 Jun 2023 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/platforms/kafka-event-backbone/</guid><description>Rebuilding a mission-critical event streaming platform that became the organization&amp;rsquo;s nervous system — and later, the feed AI agents could trust.</description></item><item><title>About</title><link>https://jamal.dev/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/about/</guid><description>&lt;p&gt;I am a technology leader, architect, researcher, and lifelong student of complex systems. My work sits at the intersection of enterprise architecture and the science of human expertise — studying how the best minds perceive, decide, and build, then engineering platforms that put those patterns into production.&lt;/p&gt;
&lt;p&gt;For over fifteen years I have designed and operated mission-critical distributed systems in highly regulated healthcare, telecom, and privacy-sensitive environments — Go backends, Kafka pipelines, and reliability engineering at enterprise scale.&lt;/p&gt;</description></item><item><title>Accessibility Statement</title><link>https://jamal.dev/legal/accessibility/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/legal/accessibility/</guid><description>&lt;p&gt;Jamal Yusuf is committed to making &lt;a href="https://jamal.dev/"&gt;Jamal.dev&lt;/a&gt; accessible to people with disabilities. I aim to conform to widely recognized accessibility practices, including the &lt;strong&gt;Web Content Accessibility Guidelines (WCAG) 2.1 Level AA&lt;/strong&gt; where reasonably practicable for a personal professional website.&lt;/p&gt;
&lt;h2 id="measures-taken"&gt;Measures Taken&lt;/h2&gt;
&lt;p&gt;Accessibility considerations on the Site include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Semantic HTML structure and heading hierarchy on primary templates&lt;/li&gt;
&lt;li&gt;Keyboard-accessible navigation and interactive controls where supported&lt;/li&gt;
&lt;li&gt;Visible focus states on links and buttons&lt;/li&gt;
&lt;li&gt;Text alternatives for meaningful images where implemented&lt;/li&gt;
&lt;li&gt;Sufficient color contrast in core light and dark themes&lt;/li&gt;
&lt;li&gt;Responsive layouts for different screen sizes and zoom levels&lt;/li&gt;
&lt;li&gt;Respect for &lt;code&gt;prefers-reduced-motion&lt;/code&gt; where motion effects are used&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="known-limitations"&gt;Known Limitations&lt;/h2&gt;
&lt;p&gt;Some areas may present accessibility challenges, including:&lt;/p&gt;</description></item><item><title>Architecture &amp; Engineering</title><link>https://jamal.dev/work/architecture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/architecture/</guid><description>Designing systems that are reliable, observable, governable, and built to last — in environments where failure has real consequences.</description></item><item><title>Centene Corporation — AI Platform Leadership</title><link>https://jamal.dev/work/case-studies/centene-genai/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/case-studies/centene-genai/</guid><description>&lt;p&gt;Generative AI did not arrive at Centene as a polite feature request. It arrived as a &lt;strong&gt;platform shift&lt;/strong&gt; — the kind that rearranges how teams learn, review, build, and govern. The mandate was clear enough: move faster. The constraint was equally clear: this is healthcare. Members are not beta testers.&lt;/p&gt;
&lt;h2 id="what-made-this-hard"&gt;What made this hard&lt;/h2&gt;
&lt;p&gt;The bottleneck was rarely the model. It was &lt;strong&gt;capability formation&lt;/strong&gt; — do engineers know how to build governed agents? Do reviewers know what to ask? Do leaders know how to measure value without counting tokens like vanity metrics?&lt;/p&gt;</description></item><item><title>Connect</title><link>https://jamal.dev/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/contact/</guid><description/></item><item><title>Decision-Making Under Pressure</title><link>https://jamal.dev/research/decision-making-under-pressure/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/research/decision-making-under-pressure/</guid><description>Studying how experts maintain clarity and performance in high-stakes, time-sensitive environments.</description></item><item><title>Disclaimer</title><link>https://jamal.dev/legal/disclaimer/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/legal/disclaimer/</guid><description>&lt;p&gt;The information on &lt;a href="https://jamal.dev/"&gt;Jamal.dev&lt;/a&gt; (the &amp;ldquo;Site&amp;rdquo;) is provided for &lt;strong&gt;general informational and educational purposes&lt;/strong&gt; only.&lt;/p&gt;
&lt;h2 id="not-professional-advice"&gt;Not Professional Advice&lt;/h2&gt;
&lt;p&gt;Content on the Site — including articles, research notes, case studies, architecture descriptions, and presentations — reflects personal professional experience, research, and opinions. It is &lt;strong&gt;not&lt;/strong&gt; legal, medical, financial, investment, or other licensed professional advice.&lt;/p&gt;
&lt;p&gt;You should not rely on Site content as a substitute for advice tailored to your situation. Consult qualified professionals before making decisions that may affect your organization, systems, compliance posture, or legal obligations.&lt;/p&gt;</description></item><item><title>Enterprise GenAI Adoption</title><link>https://jamal.dev/research/enterprise-genai-adoption/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/research/enterprise-genai-adoption/</guid><description>Studying how regulated organizations adopt Generative AI responsibly — production agents, governance, team enablement, and the human systems that determine whether adoption sticks.</description></item><item><title>Expert Vision Framework</title><link>https://jamal.dev/research/expert-vision-framework/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/research/expert-vision-framework/</guid><description>A proprietary research framework combining AI, behavioral analytics, and cognitive science to model and accelerate expert performance across domains.</description></item><item><title>Eye-Tracking &amp; Expert Perception</title><link>https://jamal.dev/research/eye-tracking-expert-perception/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/research/eye-tracking-expert-perception/</guid><description>Mapping how experts visually scan, prioritize, and extract signal — using Eyegaze systems and Interactive Minds research tooling built for serious perception work.</description></item><item><title>Human-AI Collaboration</title><link>https://jamal.dev/research/human-ai-collaboration/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/research/human-ai-collaboration/</guid><description>Designing agentic systems and interfaces that amplify human expertise rather than abstract it.</description></item><item><title>Open Source &amp; Experiments</title><link>https://jamal.dev/work/open-source/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/open-source/</guid><description>Tools, prototypes, and playful systems where curiosity meets code — most of them born from a question I could not stop thinking about.</description></item><item><title>Privacy Policy</title><link>https://jamal.dev/legal/privacy-policy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/legal/privacy-policy/</guid><description>&lt;p&gt;This Privacy Policy describes how &lt;strong&gt;Jamal Yusuf&lt;/strong&gt; (&amp;ldquo;I,&amp;rdquo; &amp;ldquo;me,&amp;rdquo; or &amp;ldquo;my&amp;rdquo;) collects, uses, and shares information when you visit &lt;a href="https://jamal.dev/"&gt;Jamal.dev&lt;/a&gt; (the &amp;ldquo;Site&amp;rdquo;). This Site is operated from the United States and is intended for a general audience.&lt;/p&gt;
&lt;h2 id="information-i-collect"&gt;Information I Collect&lt;/h2&gt;
&lt;h3 id="information-you-provide"&gt;Information you provide&lt;/h3&gt;
&lt;p&gt;If you contact me by email or through LinkedIn, I receive the information you choose to send (such as your name, email address, and message content). I use that information only to respond and maintain a professional correspondence record as needed.&lt;/p&gt;</description></item><item><title>Real-Time Claims Modernization</title><link>https://jamal.dev/work/case-studies/real-time-claims-modernization/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/work/case-studies/real-time-claims-modernization/</guid><description>&lt;p&gt;Batch claims processing is one of those systems that works until it does not — until a member is waiting, an operator is refreshing a screen, and everyone realizes that &amp;ldquo;overnight&amp;rdquo; is a euphemism for &lt;strong&gt;too late&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;The goal was not novelty. It was &lt;strong&gt;reality in real time&lt;/strong&gt; — without taking down the plane while we rebuilt the engine.&lt;/p&gt;
&lt;h2 id="the-constraint-everyone-felt"&gt;The constraint everyone felt&lt;/h2&gt;
&lt;p&gt;Mission-critical healthcare operations do not get maintenance windows with applause. Zero downtime was not a slide-deck ambition. It was the price of admission. Every migration step needed a rollback story that did not depend on heroics at 2 a.m.&lt;/p&gt;</description></item><item><title>REDLINE Design System</title><link>https://jamal.dev/research/redline-design-system/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/research/redline-design-system/</guid><description>A modern, high-contrast design system built around precision, confidence, and visual clarity — sharp geometry, disciplined red, and production-ready patterns for web apps, dashboards, and tools.</description></item><item><title>Speaking</title><link>https://jamal.dev/speaking/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/speaking/</guid><description>I speak about architecture, engineering leadership, the science of expertise, and building systems that respect both technology and human performance.</description></item><item><title>Systems Thinking</title><link>https://jamal.dev/research/systems-thinking/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/research/systems-thinking/</guid><description>Connecting technology, cognition, and organizational learning — how complex systems behave, fail, adapt, and teach us when we pay attention to the whole.</description></item><item><title>Terms of Use</title><link>https://jamal.dev/legal/terms-of-use/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://jamal.dev/legal/terms-of-use/</guid><description>&lt;p&gt;These Terms of Use (&amp;ldquo;Terms&amp;rdquo;) govern your access to and use of &lt;a href="https://jamal.dev/"&gt;Jamal.dev&lt;/a&gt; (the &amp;ldquo;Site&amp;rdquo;), operated by &lt;strong&gt;Jamal Yusuf&lt;/strong&gt; (&amp;ldquo;I,&amp;rdquo; &amp;ldquo;me,&amp;rdquo; or &amp;ldquo;my&amp;rdquo;). By accessing the Site, you agree to these Terms. If you do not agree, do not use the Site.&lt;/p&gt;
&lt;h2 id="use-of-the-site"&gt;Use of the Site&lt;/h2&gt;
&lt;p&gt;You may use the Site for lawful, personal, and professional informational purposes. You agree not to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use the Site in any way that violates applicable law or regulation&lt;/li&gt;
&lt;li&gt;Attempt to gain unauthorized access to the Site, servers, or related systems&lt;/li&gt;
&lt;li&gt;Interfere with or disrupt the Site&amp;rsquo;s operation or security&lt;/li&gt;
&lt;li&gt;Scrape, harvest, or automate access in a manner that imposes unreasonable load&lt;/li&gt;
&lt;li&gt;Misrepresent your affiliation with me or use the Site to distribute malware or spam&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="intellectual-property"&gt;Intellectual Property&lt;/h2&gt;
&lt;p&gt;Unless otherwise noted, the Site and its original content — including text, layout, branding, graphics, and code — are owned by Jamal Yusuf or used with permission and are protected by applicable copyright, trademark, and other intellectual property laws. The site source code (JYV3, version 1.0.0) is licensed under &lt;a href="https://creativecommons.org/licenses/by-nc/4.0/"&gt;Creative Commons Attribution-NonCommercial 4.0&lt;/a&gt;; commercial use is not permitted without prior written permission.&lt;/p&gt;</description></item></channel></rss>