Being 10x (or whatever multiplier) faster at programming doesn't mean you're going to be 10x faster in designing a product or any other aspect that goes into making a good product.
Even if you hired an actual programmer, it'd take a massive amount of time to build a Photoshop clone.
Of course, at the end Photoshop is lines of code and it could be output as is, end to end. One problem is that users aren't generally giving very precise design documents which would narrow the way to interpret them into code in precisely one way. Or that a design document at any level of precision, other than code, couldn't be interpreted in multiple ways when it comes to a specific implementation.
LLMs also take a relatively long time to output acceptable code, often taking tens of minutes before giving you a small diff. The larger the codebase, the longer it usually takes to start producing code, even over an hour.
> Of course, at the end Photoshop is lines of code and it could be output as is, end to end
And yet it’s not.
> LLMs also take a relatively long time to output acceptable code, often taking tens of minutes before giving you a small diff. The larger the codebase, the longer it usually takes to start producing code, even over an hour.
The problem is that they don’t generate acceptable code, they generate code that needs to be edited to be acceptable. That has always been the slow part of engineering. Waiting an hour for a bugfix even if it cost $75 in tokens would be cheaper than hiring an engineer but only if it worked. And it’s a bit like hiring a snake oil salesman - it passes the sniff test but it’s only when you’re drowning in the fact that your ai now takes 4 hours to fix the same bugs, and it introduces new bugs _and_ you don’t have anyone who can reduce that complexity that you see the reality. For a lot of us, that is immediately clear from first glance at the output of Claude and codex and the likes.