<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ruchit Kalathiya on Medium]]></title>
        <description><![CDATA[Stories by Ruchit Kalathiya on Medium]]></description>
        <link>https://medium.com/@ruchit_kalathiya?source=rss-48b85989c8d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bDhXuWHWFNuLpB4y6_3hog.png</url>
            <title>Stories by Ruchit Kalathiya on Medium</title>
            <link>https://medium.com/@ruchit_kalathiya?source=rss-48b85989c8d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:47:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ruchit_kalathiya/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Stop Writing Long Prompts. Build AI Systems Like This Instead.]]></title>
            <link>https://medium.com/simform-engineering/stop-writing-long-prompts-build-ai-systems-like-this-instead-511a2235f84b?source=rss-48b85989c8d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/511a2235f84b</guid>
            <category><![CDATA[copilot-prompts]]></category>
            <category><![CDATA[copilot-instruction]]></category>
            <category><![CDATA[copilot-skills]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[github-copilot]]></category>
            <dc:creator><![CDATA[Ruchit Kalathiya]]></dc:creator>
            <pubDate>Wed, 13 May 2026 12:04:48 GMT</pubDate>
            <atom:updated>2026-05-13T12:04:48.723Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Most developers building with AI agents are doing one of these wrong. Here’s how to fix it before it costs you.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnbGhCNf4fUgGneHoKEMhA.png" /><figcaption>Stop Writing Long Prompts. Build AI Systems Like This Instead.</figcaption></figure><p>Let me guess how your workflow looks.</p><p><strong>Week 1</strong>:<br>Everything feels magical<br>You type something. It works.</p><p><strong>Week 3:</strong><br>Outputs start drifting.<br>Same prompt, different results.</p><p><strong>Week 5:</strong><br>You’ve written a 2,000-word system prompt…<br>…and it still doesn’t enforce the one thing you care about.</p><p>Sound familiar, huh?</p><h3>The Real Problem (That Nobody Tells You)</h3><p>You’re using <strong>one thing</strong> (a prompt) to do <strong>three completely different jobs. </strong>And those jobs were never meant to live together.</p><p>That’s why: <br> • your agent feels inconsistent<br> • your team gets different results<br> • your prompts keep growing… but never stabilizing</p><p>The fix is surprisingly simple. There are <strong>three layers</strong>, not one:<br> • <strong>Prompts</strong><br> • <strong>Instructions</strong><br> • <strong>Skills</strong></p><p>And each one has a <strong>different purpose, lifetime, and role.</strong></p><h3>Why This Matters More Than You Think</h3><p>If you ignore this separation, you’ll hit a ceiling. Not because the AI is bad.</p><p>But because:<br> • your system has no structure<br> • your knowledge isn’t reusable<br> • your agent resets behavior every time</p><p>Meanwhile, teams that get this right aren’t “better at prompting.”</p><p>They just <strong>organize their system properly</strong>.</p><p>That’s it.</p><h3>Layer 1: Prompts — The Task Right Now</h3><p>A prompt is simply what you want done right now. It has no memory, doesn’t persist, and lives for a single interaction.</p><p>A good prompt is lean and focused:</p><pre>Review this PR: [PR contents]</pre><p>A bad prompt tries to do everything:</p><pre>Review this PR. Follow our style guide. Use camelCase. Check security first...</pre><p>That’s not a prompt — that’s a system crammed into the wrong place.</p><p>A useful rule of thumb: if your prompt feels permanent, it’s doing too much.</p><h3>Layer 2: Instructions — The Rules That Never Change</h3><p>Instructions are your always-on behavior layer. They define how the agent should behave across every interaction — without you repeating them.</p><p>This includes things like coding standards, naming conventions, tone, and security rules.</p><p>Unlike prompts, instructions are persistent. They’re automatically applied and don’t need to be invoked manually.</p><p>Think of them like this: you don’t remind a senior developer every day to write clean code — it’s already internalized. Instructions should do the same for your AI.</p><p>The key is specificity. “Write clean code” is vague. “Extract functions longer than 20 lines into smaller named functions” is actionable.</p><blockquote><strong><em>Industry fact:</em></strong><em> The awesome-copilot community repository contains over 120 real-world instruction files. Teams get </em>very<em> granular with this layer. Start with 3–5 covering your most critical standards. Add more as patterns emerge.</em></blockquote><p><strong>The classic mistake:</strong> Writing instructions that are actually task descriptions. “When reviewing code, first check for bugs, then style, then improvements” — that’s a procedure, not a behavioral rule. It belongs in a skill (coming up next).</p><h3>Layer 3: Skills — Reusable Playbooks</h3><p>If instructions define behavior, skills define execution.</p><p>Skills are reusable workflows — structured, multi-step processes that you want the agent to follow when a specific type of task appears.</p><p>For example, instead of repeating:<br> “Check security, then bugs, then style, then improvements…”</p><p>You define a skill that encodes this workflow once.</p><p>Skills are triggered when needed, not always active. That’s what makes them powerful — and efficient.</p><p><strong>Where skills live:</strong> .github/skills/ in your repository, automatically shared with everyone on the team.</p><h3>The Mistake Everyone Makes</h3><p>Most developers combine everything into one massive prompt:</p><pre>Be a code reviewer. Follow style guide. Check security first. Be polite...</pre><p>This mixes behavior, workflow, and task into a single block.</p><p>Three layers. One place. No separation.</p><p>That’s why it breaks.</p><h3>The Correct Setup (Same Result, Cleaner System)</h3><p>When you separate concerns properly, the system becomes much simpler.</p><p>Instructions handle what’s always true (like tone and security rules). Skills handle structured workflows (like how to perform a code review). And the prompt only contains the task:</p><pre>Review this PR: [PR contents]</pre><p>Same output. But now it’s consistent, reusable, and scalable across your team.</p><h3>A Mental Model That Sticks</h3><p>Imagine hiring a developer.</p><p>On day one, you give them an employee handbook (instructions), a task ticket (prompt), and a runbook (skills).</p><p>Now imagine instead giving them a ticket every day… with the entire handbook attached each time.</p><p>That’s exactly what long prompts are doing to your AI.</p><h3>What Changes When You Fix This</h3><p>Once you separate these layers, things start to click.</p><p>New developers onboard faster because the system already knows your conventions. Workflows become repeatable instead of dependent on who wrote the prompt. Updates become modular — you change one file instead of rewriting everything.</p><p>And most importantly, the agent stops feeling random and starts feeling intentional.</p><h3>The Truth About Prompt Engineering</h3><p>There’s a ceiling to prompt engineering — and it’s lower than most people think.</p><p>A perfect prompt inside a poorly structured system will still produce inconsistent results.</p><p>The best teams aren’t writing longer prompts. They’re building better systems around them.</p><h3>Start Here (10-Minute Fix)</h3><p>Take your current prompt and break it down:</p><ul><li>Anything that’s always true → move to instructions</li><li>Anything that’s a repeatable process → turn into a skill</li><li>What’s left → that’s your actual prompt</li></ul><p>Most people find that 70–80% of their prompt doesn’t belong there.</p><p>What remains is often just a few lines — not because you removed value, but because you finally put it in the right place.</p><h3>One Last Thought</h3><p>Most developers are still stuck in “prompt mode.” A few have started thinking in systems.</p><p>Once you see the difference, you don’t go back.</p><p>So I’m curious — are you still writing long prompts, or have you started separating your layers?</p><p><a href="https://www.simform.com/services/gen-ai-ml-development/">Simform</a> helps engineering teams adopt structured AI-driven development practices across the SDLC through reusable frameworks, agentic workflows, and accelerators like PexAI, enabling more consistent and scalable software delivery.</p><p><strong>References</strong></p><ol><li><a href="https://awesome-copilot.github.com/learning-hub/what-are-agents-skills-instructions/">Awesome GitHub Copilot — What are Agents, Skills, and Instructions</a></li><li><a href="https://awesome-copilot.github.com/learning-hub/creating-effective-skills/">Awesome GitHub Copilot — Creating Effective Skills</a></li><li><a href="https://awesome-copilot.github.com/learning-hub/defining-custom-instructions/">Awesome GitHub Copilot — Defining Custom Instructions</a></li><li><a href="https://agentskills.io/home">Agent Skills Open Specification</a></li><li><a href="https://medium.com/simform-engineering/agent-instructions-vs-skills-the-difference-most-developers-miss-a0d854203f36">Simform Engineering — Agent Instructions vs Skills</a></li></ol><p><strong>For more updates on the latest tools and technologies, follow the </strong><a href="https://medium.com/simform-engineering"><strong>Simform Engineering</strong></a><strong> blog.</strong></p><p><strong>Follow Us: </strong><a href="https://twitter.com/simform"><strong>X</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/simform/"><strong>LinkedIn</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=511a2235f84b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simform-engineering/stop-writing-long-prompts-build-ai-systems-like-this-instead-511a2235f84b">Stop Writing Long Prompts. Build AI Systems Like This Instead.</a> was originally published in <a href="https://medium.com/simform-engineering">Simform Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with AVFoundation: Part 1- Playing Sounds with AVAudioPlayer]]></title>
            <link>https://medium.com/simform-engineering/getting-started-with-avfoundation-part-1-playing-sounds-with-avaudioplayer-fd98c39e4be9?source=rss-48b85989c8d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd98c39e4be9</guid>
            <category><![CDATA[avfoundation]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[avaudioplayer]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swift]]></category>
            <dc:creator><![CDATA[Ruchit Kalathiya]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 10:07:00 GMT</pubDate>
            <atom:updated>2025-07-21T10:07:00.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ToWxC0MMK3aZ-HO-A0erng.png" /></figure><p>Have you ever wondered how your favourite iOS apps deliver those crisp sound effects, play your workout playlist, or record your voice memos with such clarity? Behind these seamless audio experiences lies Apple’s powerful AVFoundation framework. Whether you’re building the next hit music app or simply want to add some sound to your iOS project, understanding AVFoundation is your ticket to audio mastery.</p><p>In this first article of our AVFoundation series, we’ll dive into the basics of audio playback using AVAudioPlayer — the perfect starting point for any developer looking to integrate audio into their iOS applications.</p><h3>What is AVFoundation?</h3><p>AVFoundation is Apple’s framework for working with audiovisual media on iOS, macOS, tvOS, and watchOS platforms. Think of it as your Swiss Army knife for anything related to audio and video. It provides a rich set of interfaces for playing, recording, editing, and managing audiovisual media.</p><h3>Why Use AVFoundation for Audio?</h3><p>You might be thinking, “There are so many audio libraries out there. Why should I use AVFoundation?” Great question! Here’s why:</p><ul><li><strong>Native Integration</strong>: As part of Apple’s ecosystem, AVFoundation is optimized for performance on Apple devices and seamlessly integrates with other Apple frameworks.</li><li><strong>Comprehensive Capabilities</strong>: From simple audio playback to complex audio mixing, AVFoundation has you covered.</li><li><strong>Future-Proof</strong>: Regular updates from Apple ensure compatibility with the latest iOS versions and device capabilities.</li><li><strong>Scalability</strong>: Start simple with high-level classes like AVAudioPlayer, then graduate to more complex audio features as your needs evolve.</li></ul><h3>Key Audio Components in AVFoundation</h3><p>Before we jump into code, let’s get familiar with some key audio components in AVFoundation:</p><ul><li><strong>AVAudioPlayer</strong>: A straightforward class for playing audio from files or memory buffers.</li><li><strong>AVAudioRecorder</strong>: Records audio to a file.</li><li><strong>AVAudioEngine</strong>: Provides advanced audio processing capabilities.</li><li><strong>AVAudioSession</strong>: Manages audio behaviour in your app, including how it interacts with other audio on the device.</li></ul><p>Today, we’ll focus on AVAudioPlayer to get you started on your audio journey.</p><h3>Hands-On with AVAudioPlayer</h3><p>AVAudioPlayer is your go-to class for playing audio from files or memory buffers. It supports various audio formats (MP3, AAC, ALAC, etc.), allows for playback control, and even provides audio metering capabilities.</p><p>Let’s get our hands dirty with some code!</p><h3>Setting Up Your Project</h3><p>First things first — import AVFoundation in your Swift file:</p><pre>import UIKit<br>import AVFoundation</pre><h3>Loading and Initializing Local Audio Files</h3><p>To play an audio file, you need to:</p><ol><li>Create a URL pointing to your audio file</li><li>Initialize an AVAudioPlayer with that URL</li><li>Prepare the player for playback</li></ol><p>Here’s how:</p><pre>class AudioPlayerExample {<br>    var audioPlayer: AVAudioPlayer?<br>    <br>    func setupAudioPlayer() {<br>        // Get the path to the sound file inside your app&#39;s bundle<br>        guard let path = Bundle.main.path(forResource: &quot;awesome_track&quot;, ofType: &quot;mp3&quot;) else {<br>            print(&quot;Could not find audio file&quot;)<br>            return<br>        }<br>        let url = URL(fileURLWithPath: path)<br>        do {<br>            // Initialize the audio player<br>            audioPlayer = try AVAudioPlayer(contentsOf: url)<br>            <br>            // Prepare to play (loads the audio file into memory)<br>            audioPlayer?.prepareToPlay()<br>            <br>            print(&quot;Audio player ready to rock! 🎸&quot;)<br>        } catch {<br>            print(&quot;Error initializing audio player: \(error.localizedDescription)&quot;)<br>        }<br>    }<br>}</pre><blockquote>💡 <strong>Pro Tip</strong>: Always call prepareToPlay() after initializing your audio player. This loads the audio file into memory, reducing the delay when you actually hit play.</blockquote><h3>Playing, Pausing, and Stopping Audio</h3><p>Now that we have our player set up, let’s control the playback:</p><pre>// Play the audio<br>func playAudio() {<br>    if let player = audioPlayer, !player.isPlaying {<br>        player.play()<br>        print(&quot;Now playing! 🎵&quot;)<br>    }<br>}<br><br>// Pause the audio<br>func pauseAudio() {<br>    if let player = audioPlayer, player.isPlaying {<br>        player.pause()<br>        print(&quot;Paused! ⏸️&quot;)<br>    }<br>}<br>// Stop the audio (resets to beginning)<br>func stopAudio() {<br>    if let player = audioPlayer {<br>        player.stop()<br>        player.currentTime = 0 // Reset to beginning<br>        print(&quot;Stopped! ⏹️&quot;)<br>    }<br>}</pre><h3>Enhancing Playback: Looping, Volume Control, and Playback Rate</h3><p>AVAudioPlayer offers several properties to customize your audio playback:</p><pre>func configurePlayback() {<br>    guard let player = audioPlayer else { return }<br>    <br>    // Loop the audio (-1 for infinite loop, or specify number of times)<br>    player.numberOfLoops = -1<br>    <br>    // Adjust volume (0.0 to 1.0)<br>    player.volume = 0.7<br>    <br>    // Control playback rate (0.5 to 2.0 for iOS, with 1.0 being normal)<br>    // Note: This requires iOS 10.0+ and setting enableRate to true<br>    player.enableRate = true<br>    player.rate = 1.25<br>    <br>    print(&quot;Audio configured: looping infinitely at 1.25x speed with 70% volume! 🔊&quot;)<br>}</pre><h3>Audio Metering — Visualize Your Sound</h3><p>Want to create those cool audio visualizations? AVAudioPlayer has built-in metering capabilities:</p><pre>func enableMetering() {<br>    guard let player = audioPlayer else { return }<br>    <br>    // Enable metering<br>    player.isMeteringEnabled = true<br>    <br>    // Start a timer to update meters<br>    Timer.scheduledTimer(withTimeInterval: 0.1, repeats: true) { [weak self] _ in<br>        self?.updateMeters()<br>    }<br>}</pre><pre>func updateMeters() {<br>    guard let player = audioPlayer, player.isPlaying else { return }<br>    <br>    // Update meter values<br>    player.updateMeters()<br>    <br>    // Get average power for each channel<br>    let averagePower = player.averagePower(forChannel: 0)<br>    let peakPower = player.peakPower(forChannel: 0)<br>    <br>    // Convert from decibels to a more usable scale<br>    // dB values typically range from -160 to 0<br>    let normalizedValue = pow(10, averagePower / 20)<br>    <br>    print(&quot;Average power: \(normalizedValue)&quot;)<br>    <br>    // Here you could update UI elements like progress bars or animations<br>    // based on the normalizedValue<br>}</pre><h3>Handling Playback Completion and Errors</h3><p>To respond when audio finishes playing or when errors occur, implement the AVAudioPlayerDelegate protocol:</p><pre>class AudioPlayerExample: AVAudioPlayerDelegate {<br>    var audioPlayer: AVAudioPlayer?<br>    <br>    // Setup code...<br><br>    func setupWithDelegate() {<br>        // Other initialization code...<br>        audioPlayer?.delegate = self<br>    }<br>    <br>    // AVAudioPlayerDelegate methods<br>    func audioPlayerDidFinishPlaying(_ player: AVAudioPlayer, successfully flag: Bool) {<br>        if flag {<br>            print(&quot;Audio playback completed successfully! 🎉&quot;)<br>            // Perform actions after playback finishes<br>        } else {<br>            print(&quot;Audio playback did not finish successfully 😕&quot;)<br>        }<br>    }<br>    <br>    func audioPlayerDecodeErrorDidOccur(_ player: AVAudioPlayer, error: Error?) {<br>        if let error = error {<br>            print(&quot;Audio decoding error: \(error.localizedDescription)&quot;)<br>        }<br>    }<br>}</pre><h3>Putting It All Together</h3><p>Let’s create a simple view controller that uses all these components:</p><pre>class AudioViewController: UIViewController {<br>    var audioPlayer: AVAudioPlayer?<br>    <br>    // UI elements<br>    private let playButton = UIButton()<br>    private let pauseButton = UIButton()<br>    private let stopButton = UIButton()<br>    private let volumeSlider = UISlider()<br>    <br>    override func viewDidLoad() {<br>        super.viewDidLoad()<br>        setupUI()<br>        setupAudioPlayer()<br>    }<br>    <br>    private func setupUI() {<br>        // UI setup code...<br>        <br>        playButton.addTarget(self, action: #selector(playTapped), for: .touchUpInside)<br>        pauseButton.addTarget(self, action: #selector(pauseTapped), for: .touchUpInside)<br>        stopButton.addTarget(self, action: #selector(stopTapped), for: .touchUpInside)<br>        volumeSlider.addTarget(self, action: #selector(volumeChanged), for: .valueChanged)<br>    }<br>    <br>    private func setupAudioPlayer() {<br>        guard let path = Bundle.main.path(forResource: &quot;soundtrack&quot;, ofType: &quot;mp3&quot;) else {<br>            print(&quot;Audio file not found&quot;)<br>            return<br>        }<br>        do {<br>            audioPlayer = try AVAudioPlayer(contentsOf: URL(fileURLWithPath: path))<br>            audioPlayer?.delegate = self<br>            audioPlayer?.prepareToPlay()<br>            <br>            // Configure initial state<br>            audioPlayer?.volume = volumeSlider.value<br>        } catch {<br>            print(&quot;Error setting up audio player: \(error)&quot;)<br>        }<br>    }<br>    <br>    // MARK: - Actions<br>    @objc private func playTapped() {<br>        audioPlayer?.play()<br>    }<br>    <br>    @objc private func pauseTapped() {<br>        audioPlayer?.pause()<br>    }<br>    <br>    @objc private func stopTapped() {<br>        audioPlayer?.stop()<br>        audioPlayer?.currentTime = 0<br>    }<br>    <br>    @objc private func volumeChanged(_ slider: UISlider) {<br>        audioPlayer?.volume = slider.value<br>    }<br>}<br><br>// MARK: - AVAudioPlayerDelegate<br>extension AudioViewController: AVAudioPlayerDelegate {<br>    func audioPlayerDidFinishPlaying(_ player: AVAudioPlayer, successfully flag: Bool) {<br>        print(&quot;Audio finished playing&quot;)<br>        // Update UI or perform actions<br>    }<br>}</pre><h3>Common Pitfalls and How to Avoid Them</h3><p>As you venture into the world of AVFoundation, here are some common issues to watch out for:</p><h3>1. Audio Session Configuration</h3><p>Always configure your app’s audio session before playing audio. This determines how your audio interacts with the system:</p><pre>func configureAudioSession() {<br>    do {<br>        try AVAudioSession.sharedInstance().setCategory(.playback)<br>        try AVAudioSession.sharedInstance().setActive(true)<br>        print(&quot;Audio session configured! 🎧&quot;)<br>    } catch {<br>        print(&quot;Failed to configure audio session: \(error)&quot;)<br>    }<br>}</pre><h3>2. Memory Management</h3><p>Audio files can be large. If you’re working with multiple audio players, make sure to release them when they’re no longer needed:</p><pre>func cleanUp() {<br>    audioPlayer?.stop()<br>    audioPlayer = nil<br>    print(&quot;Audio resources released! 🧹&quot;)<br>}</pre><h3>3. File Format Compatibility</h3><p>Not all audio formats work on all devices. Stick to widely supported formats like MP3, AAC, and WAV for best compatibility.</p><h3>Conclusion</h3><p>Congratulations! 🎉 You’ve taken your first steps into the world of AVFoundation audio. With AVAudioPlayer, you now have the power to integrate rich audio experiences into your iOS applications.</p><p>In this article, we’ve covered:</p><ul><li>The basics of AVFoundation</li><li>Setting up and using AVAudioPlayer</li><li>Controlling audio playback</li><li>Customizing playback with looping and volume</li><li>Implementing audio metering</li><li>Handling playback completion and errors</li></ul><p>But this is just the beginning! In our next article, we’ll explore more advanced topics like AVAudioRecorder for capturing user audio. Stay tuned!</p><h3>Next Steps</h3><p>Ready to expand your AVFoundation knowledge? Here are some things to try:</p><ol><li>Create a simple music player app using the code examples from this article</li><li>Experiment with audio metering to create visualizations</li><li>Try playing multiple audio files simultaneously with separate AVAudioPlayer instances</li></ol><p>What audio features are you excited to add to your iOS apps? Let me know in the comments below!</p><blockquote><strong>For more updates on the latest tools and technologies, follow the </strong><a href="https://medium.com/simform-engineering"><strong>Simform Engineering Blog</strong></a><strong>.</strong></blockquote><blockquote><strong>Follow us: </strong><a href="https://twitter.com/simform"><strong>Twitter</strong></a><strong> | </strong><a href="https://www.linkedin.com/company/simform/"><strong>LinkedIn</strong></a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd98c39e4be9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simform-engineering/getting-started-with-avfoundation-part-1-playing-sounds-with-avaudioplayer-fd98c39e4be9">Getting Started with AVFoundation: Part 1- Playing Sounds with AVAudioPlayer</a> was originally published in <a href="https://medium.com/simform-engineering">Simform Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>