<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Software Engineering on Agile Congruence</title>
    <link>https://agilecongruence.com/tags/software-engineering/</link>
    <description>Recent content in Software Engineering on Agile Congruence</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Apr 2025 14:04:34 +0000</lastBuildDate>
    <atom:link href="https://agilecongruence.com/tags/software-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>This might kill your vibe, but I’m not worried about AI replacing Software Engineers</title>
      <link>https://agilecongruence.com/posts/this-might-kill-your-vibe/</link>
      <pubDate>Wed, 23 Apr 2025 14:04:34 +0000</pubDate>
      <guid>https://agilecongruence.com/posts/this-might-kill-your-vibe/</guid>
      <description>&lt;p&gt;I started learning to code in the late 1990’s using gcc, make, and emacs.&lt;/p&gt;
&lt;p&gt;The 2000’s were a huge pivot point in Software Engineering. Three major changes which were very related came together to fundamentally change how software saw built. First, modern IDE’s changed how coding was done. Second, high level languages like Java, C#, and Python became more usable. Third, agile fundamentally changed the way that engineers worked with businesses.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
