<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>tools on Agile Software Development</title>
    <link>https://agilesoftdev.com/tags/tools/</link>
    <description>Recent content in tools on Agile Software Development</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agilesoftdev.com/tags/tools/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Prompt Engineering Is a Software Discipline, Not a Workaround</title>
      <link>https://agilesoftdev.com/prompt-engineering-is-a-software-discipline-not-a-workaround/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://agilesoftdev.com/prompt-engineering-is-a-software-discipline-not-a-workaround/</guid>
      <description>The phrase prompt engineering acquired a skeptical connotation early — something between a joke about talking to chatbots and a transitional skill that would be obsoleted as models improved. Neither characterization was accurate, and teams that dismissed it on those grounds have paid a real productivity cost.
Prompting a code generation model effectively is a software discipline because it shares the fundamental characteristics of all software work: it requires precise specification of desired behavior, systematic handling of edge cases, and iterative refinement based on observed output.</description>
    </item>
    
  </channel>
</rss>
