I don't think the realistic alternative here was “hire a team for a month and get a better semantic conversion” For a rewrite of this si...
I don't think the realistic alternative here was “hire a team for a month and get a better semantic conversion” For a rewrite of this size, the expensive part is deep understanding of the underlying system in order to preserve behavior while keeping performance, and above all that not freezing product work while doing it. Adding more engineers would just end up in managerial burden and review bottlenecks, to say the least. So even assuming the API cost estimate is high, I don't buy the “just hire engineers for a month” take. A team unfamiliar with the codebase would probably spend a large chunk of that month just building context and deciding how not to break everything. A team familiar with the codebase is even more valuable doing product work, bug fixes, and review of the existing codebase. So, in short, I do agree with the simple fact that this is still too expensive for most projects, but not with the idea that “a small team would trivially do better in a month”.
Posted by JavierFlores09 on Jul 9, 2026, 12:39 AM
Tags
Related issues
- Fake websites pretending to be legitimate websites in order to steal your passwords was considered a HUGE problem.
- 3.5 Flash was always too expensive for a "flash" model.
- I was hosting on a PC at home like 10 years ago.
- I live in walking distance of all these things, and the farthest I’ve gotten my kid to do things alone is to walk to and from school (a w...
- It was a long time ago, so I don't remember.
- I still like to buy my cheap and esoteric Chinese stuff from Amazon.
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
pricing (E-commerce)
Fake websites pretending to be legitimate websites in order to steal your passwords was considered a HUGE problem.
3.5 Flash was always too expensive for a "flash" model.
I don't think the realistic alternative here was “hire a team for a month and get a better semantic conversion” For a rewrite of this si...
I was hosting on a PC at home like 10 years ago.
I live in walking distance of all these things, and the farthest I’ve gotten my kid to do things alone is to walk to and from school (a w...
It was a long time ago, so I don't remember.
I still like to buy my cheap and esoteric Chinese stuff from Amazon.
My local area used to be great to find old used woodworking tools for cheap.
I don't think the realistic alternative here was “hire a team for a month and get a better semantic conversion” For a rewrite of this si...
I don't think the realistic alternative here was “hire a team for a month and get a better semantic conversion” For a rewrite of this size, the expensive part is deep understanding of the underlying system in order to preserve behavior while keeping performance, and above all that not freezing product work while doing it. Adding more engineers would just end up in managerial burden and review bottlenecks, to say the least. So even assuming the API cost estimate is high, I don't buy the “just hire engineers for a month” take. A team unfamiliar with the codebase would probably spend a large chunk of that month just building context and deciding how not to break everything. A team familiar with the codebase is even more valuable doing product work, bug fixes, and review of the existing codebase. So, in short, I do agree with the simple fact that this is still too expensive for most projects, but not with the idea that “a small team would trivially do better in a month”.
Comments (0)
No comments yet. Start the discussion.