<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Experiments on Bil Arikan</title><link>https://bil.arikan.ca/categories/experiments/</link><description>Recent content in Experiments on Bil Arikan</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bil.arikan.ca/categories/experiments/index.xml" rel="self" type="application/rss+xml"/><item><title>Code-as-video with Editframe --- video production as a dev workflow</title><link>https://bil.arikan.ca/posts/code-as-video-with-editframe/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://bil.arikan.ca/posts/code-as-video-with-editframe/</guid><description>The first experiment closed with a question : can an agent take structured product information and turn it into a short, repeatable video composition? This second experiment is the answer. The interesting part is not the seconds. It is what this workflow does to the way Learning Program Owners, Learning Designers, and Learning Developers traditionally split the work.</description></item><item><title>Hello world with Editframe --- video production as a dev workflow</title><link>https://bil.arikan.ca/posts/video-production-to-dev-workflow-editframe-test-drive/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://bil.arikan.ca/posts/video-production-to-dev-workflow-editframe-test-drive/</guid><description>Can video production start to look more like a dev workflow, where the composition is code, the output is reproducible, and the agent can help move through the rough edges? Experiment 01 &amp;ndash; a hello-world Editframe project, scaffolded, iterated, and rendered locally, with the failure points captured for the next pass.</description></item><item><title>From blocked to built : decomposing a stuck project with human + AI collaboration</title><link>https://bil.arikan.ca/posts/from-blocked-to-built/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://bil.arikan.ca/posts/from-blocked-to-built/</guid><description>&lt;p&gt;A content adaptation project had been stalled for months. Existing material existed, but no team had a clear mandate to adapt it, the source content&amp;rsquo;s training modality was wrong for the target audience, and the resourcing case was too thin to justify a traditional approach. The guiding question I was working with : &lt;strong&gt;can a single practitioner move a stuck, multi-stakeholder project to a validated proposal using AI-assisted work decomposition &amp;mdash; and if so, what does that actually look like?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Claude Skills and the Copilot Parallel : A Practitioner's Map</title><link>https://bil.arikan.ca/posts/claude-skills-copilot-mapping/</link><pubDate>Sat, 18 Apr 2026 08:00:00 -0400</pubDate><guid>https://bil.arikan.ca/posts/claude-skills-copilot-mapping/</guid><description>Building the same workflow in Claude takes an hour; in Copilot it means Power Automate and three to five hours. That gap is real &amp;mdash; and it&amp;rsquo;s architectural. Here is how Claude&amp;rsquo;s skill system maps to M365 Copilot, and what the comparison reveals about where each system was designed to be used.</description></item></channel></rss>