<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Budget on Kuldeep Singh</title>
        <link>https://thinkuldeep.com//tags/budget/</link>
        <description>Recent content in Budget on Kuldeep Singh</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en</language>
        <lastBuildDate>Sun, 03 Aug 2025 10:58:08 -0400</lastBuildDate><atom:link href="https://thinkuldeep.com/tags/budget/index.xml" rel="self" type="application/rss+xml" />
        <item>
            <title>Engineering Budget Planning in the AI Era</title>
            <link>https://thinkuldeep.com//post/engineering-budget-planning-in-ai-era/</link>
            <pubDate>Sun, 03 Aug 2025 10:58:08 -0400</pubDate>
            
            <guid>https://thinkuldeep.com//post/engineering-budget-planning-in-ai-era/</guid>
            <description>Every year, engineering leaders sit around conference tables with finance partners discussing one question:
&amp;ldquo;How should we optimize the engineering budget?&amp;rdquo;
Unfortunately, &amp;ldquo;optimize&amp;rdquo; often becomes synonymous with &amp;ldquo;reduce.&amp;rdquo;
Can we reduce headcount? Can AI replace developers? Can we outsource more work? Can we delay hiring? Can we spend less on learning? These questions may improve the next quarterly financial report, but rarely do they build better engineering organizations.
As Artificial Intelligence becomes part of every software engineering team&amp;rsquo;s daily workflow, another question has become increasingly common.</description>
        </item>
        
    </channel>
</rss>