<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Risk on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/risk/</link><description>Recent content in Risk on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 26 Sep 2025 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/risk/index.xml" rel="self" type="application/rss+xml"/><item><title>Where to Use AI FOR Development: A Practical Guide for Engineers and Managers</title><link>https://javapro-en.svenruppert.com/where-to-use-ai-for-development-a-practical-guide-for-engineers-and-managers/</link><pubDate>Fri, 26 Sep 2025 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/where-to-use-ai-for-development-a-practical-guide-for-engineers-and-managers/</guid><description>&lt;p&gt;There&amp;rsquo;s a lot of noise out there about AI generating code for you, creating tests, filing bugs, and possibly even conducting your sprint planning meetings. It&amp;rsquo;s easy to get swept up in the hype. You&amp;rsquo;ve probably seen claims like &amp;ldquo;AI can build your app from a prompt&amp;rdquo; or &amp;ldquo;Ship twice as fast with half the team&amp;rdquo;. Sounds appealing doesn&amp;rsquo;t it? The reality, as always, is more nuanced.&lt;/p&gt;
&lt;p&gt;In this article, I want to puncture some of the more inflated expectations and instead offer a grounded view of where AI can help in software development today. What works, what doesn&amp;rsquo;t, and what might be worth trying if you squint hard enough. The lens I want to use is risk. Because fundamentally, that&amp;rsquo;s what software development is: a careful game of managing risk against code.&lt;/p&gt;</description></item></channel></rss>