<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bijay Rauniyar</title>
    <description>The latest articles on DEV Community by Bijay Rauniyar (@bijay_rauniyar_9f3466e812).</description>
    <link>https://dev.to/bijay_rauniyar_9f3466e812</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3991868%2F64c9574e-93e4-4fab-8d97-0344dea428a2.jpg</url>
      <title>DEV Community: Bijay Rauniyar</title>
      <link>https://dev.to/bijay_rauniyar_9f3466e812</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bijay_rauniyar_9f3466e812"/>
    <language>en</language>
    <item>
      <title>Will Software Development Eventually Be Estimated in Tokens?</title>
      <dc:creator>Bijay Rauniyar</dc:creator>
      <pubDate>Fri, 19 Jun 2026 05:44:17 +0000</pubDate>
      <link>https://dev.to/bijay_rauniyar_9f3466e812/will-software-development-eventually-be-estimated-in-tokens-136k</link>
      <guid>https://dev.to/bijay_rauniyar_9f3466e812/will-software-development-eventually-be-estimated-in-tokens-136k</guid>
      <description>&lt;p&gt;&lt;strong&gt;Will Software Development Eventually Be Estimated in Tokens?&lt;/strong&gt;&lt;br&gt;
Recently, I had an interesting thought while working with AI coding tools.&lt;/p&gt;

&lt;p&gt;For years, we’ve estimated software projects using hours, days, sprints, and story points. That’s how most teams plan and track work.&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F48fmjmwqx9uwyxxs8ja3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F48fmjmwqx9uwyxxs8ja3.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But AI is changing how we build software.&lt;/p&gt;

&lt;p&gt;Today, many developers use AI to generate code, write tests, explain existing code, create documentation, and even help with system design discussions.&lt;/p&gt;

&lt;p&gt;A task that previously took a day might now take a few hours with the help of AI.&lt;/p&gt;

&lt;p&gt;This made me wonder:&lt;/p&gt;

&lt;p&gt;What are we actually estimating now?&lt;/p&gt;

&lt;p&gt;Traditionally, we estimated human effort.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Build a new API: 2 days&lt;/li&gt;
&lt;li&gt;Add a dashboard: 3 days&lt;/li&gt;
&lt;li&gt;Integrate a payment gateway: 5 days&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But when AI is involved, the effort starts looking different.&lt;/p&gt;

&lt;p&gt;The engineer may spend less time writing code and more time:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Understanding requirements&lt;/li&gt;
&lt;li&gt;Reviewing AI-generated code&lt;/li&gt;
&lt;li&gt;Validating business logic&lt;/li&gt;
&lt;li&gt;Testing edge cases&lt;/li&gt;
&lt;li&gt;Making architectural decisions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Could AI usage become part of estimation?&lt;/p&gt;

&lt;p&gt;I’m not saying story points will disappear.&lt;/p&gt;

&lt;p&gt;Business complexity, dependencies, testing, and communication will always matter.&lt;/p&gt;

&lt;p&gt;However, I can imagine a future where teams also think about:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AI consumption&lt;/li&gt;
&lt;li&gt;Compute costs&lt;/li&gt;
&lt;li&gt;Human review effort&lt;/li&gt;
&lt;li&gt;Testing and validation effort&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Instead of:&lt;/p&gt;

&lt;p&gt;This feature will take 5 developer days.&lt;/p&gt;

&lt;p&gt;Could we someday hear something like:&lt;/p&gt;

&lt;p&gt;This feature requires significant AI assistance, several review cycles, and a day of testing.&lt;/p&gt;

&lt;p&gt;Engineers are still the decision makers&lt;/p&gt;

&lt;p&gt;Personally, I don’t think AI will replace software engineers.&lt;/p&gt;

&lt;p&gt;If anything, AI makes engineering judgment more important.&lt;/p&gt;

&lt;p&gt;Understanding the problem, making trade-offs, designing systems, and ensuring quality are still human responsibilities.&lt;/p&gt;

&lt;p&gt;The tools are changing.&lt;/p&gt;

&lt;p&gt;The responsibility isn’t.&lt;/p&gt;

&lt;p&gt;What do you think?&lt;/p&gt;

&lt;p&gt;Am I overthinking this, or do you believe AI could eventually influence how software projects are estimated?&lt;/p&gt;

&lt;p&gt;I’d love to hear how other engineers see this evolving.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>softwareengineering</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
