<?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>SoftwareArchitecture on Calyntro Blog</title><link>https://calyntro.com/blog/tags/softwarearchitecture/</link><description>Recent content in SoftwareArchitecture on Calyntro Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 07 Apr 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://calyntro.com/blog/tags/softwarearchitecture/index.xml" rel="self" type="application/rss+xml"/><item><title>AI in Software Engineering: Between Vision and Craftsmanship</title><link>https://calyntro.com/blog/posts/ai-in-software-engineering-vision-and-craftsmanship/</link><pubDate>Mon, 07 Apr 2025 00:00:00 +0000</pubDate><guid>https://calyntro.com/blog/posts/ai-in-software-engineering-vision-and-craftsmanship/</guid><description>&lt;p&gt;A question recently surfaced in my LinkedIn feed that I haven&amp;rsquo;t been able to shake:
&lt;em&gt;How will the next generation of software developers gain experience when AI takes over the writing?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The analogy offered was that of a conductor — someone who doesn&amp;rsquo;t need to play the violin to judge whether the orchestra is in harmony. It&amp;rsquo;s a compelling metaphor. But I think it lets us off the hook too easily.&lt;/p&gt;</description></item></channel></rss>