็™ป้Œฒใ—ใฆๆ‹›ๅพ…ใƒชใƒณใ‚ฏใ‚’ๅ…ฑๆœ‰ใ™ใ‚‹ใจใ€ๅ‹•็”ปๅ†็”Ÿๅ ฑ้…ฌใจ็ดนไป‹ๅ ฑ้…ฌใ‚’็ฒๅพ—ใงใใพใ™ใ€‚

Saurav | CloudYeti
@ravsau
AI Advisor and Educator | focused on AI cost optimization and ROI ex-Amazon Building
ๅ‚ๅŠ  July 2011
245 ใƒ•ใ‚ฉใƒญใƒผไธญ    270 ใƒ•ใ‚กใƒณ
How do you estimate software projects in the age of AI agents? I gave ChatGPT the prompt in the screenshot. It estimated 18 months and $2 million for the migration scenario I described. That prompt is basically describing Asanaโ€™s Enzyme migration. Asana had estimated the migration would take at least 5 years and roughly $6 million. Using Codex, they finished it in about ๐Ÿ ๐ฐ๐ž๐ž๐ค๐ฌ ๐Ÿ๐จ๐ซ ๐š๐ซ๐จ๐ฎ๐ง๐ $๐Ÿ๐Ÿ,๐ŸŽ๐ŸŽ๐ŸŽ. Bunโ€™s recent migration is another example of agents doing work that would normally take years much faster. Jarred Sumner estimated that porting Bun from Zig to Rust manually would take 3 experienced engineers about a year. Using Claude agents, they migrated ๐Ÿ“๐Ÿ‘๐Ÿ“,๐ŸŽ๐ŸŽ๐ŸŽ+ ๐ฅ๐ข๐ง๐ž๐ฌ ๐จ๐Ÿ ๐™๐ข๐  ๐ข๐ง ๐Ÿ๐Ÿ ๐๐š๐ฒ๐ฌ, with roughly $165,000 in model usage. Not every project will be like this. Some have dependencies, integrations, and a lot of coordination that still take real time. But for work thatโ€™s well-defined, verifiable, and can be parallelized, agents can completely change the math. Maybe thatโ€™s the new variable in software estimation: how much of the work can be broken into independent, ๐ฏ๐ž๐ซ๐ข๐Ÿ๐ข๐š๐›๐ฅ๐ž tasks and run in parallel by agents? A project that looks like years of engineering effort can look very different once you answer that.
ใ‚‚ใฃใจ่ฆ‹ใ‚‹