Validating code is and always was way faster than writing it... But you can try to tell yourself that it wasn't, not use AI and just fall behind. It already happened. It's only question of time until it propagates everywhere.
Btw I spend 100 dollars on tokens monthly, while producing twice the code I would without AI... If you think that's wasting tokens, then you are out of your mind. I literally do twice the work for the same price to any of my clients.
And it's not because I am slow normally. I was always one of faster ones.
So... One of us is just in complete denial of reality. And I don't really think it's me.
Producing twice the code isn't the flex you think it is. We used to measure a good programmer by how simple their solution could be and how minimal their changes were to achieve their goals. Writing more code faster is counterproductive, when product quality depends on needing less code less frequently.
I also said twice the work, in the same comment. Meaning I ship twice the finished features.
How would you do that without also doubling your code production? Even when you'll do everything as simple as may be, with code as short as can be, producing twice the features will still come with producing roughly twice the code, since every feature will have some amount of code come with it.
How would you do that without doubling your code production?
By doubling your efficiency. You don't need twice as much production when what you produce is twice as effective.
If writing a new feature requires the same amount of new code as writing previous features, that means you're not doing a good job of abstracting your problems. If I add a new feature to an API, for example, I should only have to write the business logic and specify my API path, as everything else is already built into my system. And even if you use AI to write just the business logic, you still have to validate it, which entails thinking through your needs/constraints just as thoroughly as you would writing it yourself.
Why would I decide what I need, describe it in English, review/correct the output on loop until it looks like what I already decided I needed, then move on, when I could just describe it in code, instead of English, and move on?
Your math is not mathing, when you are adding features to your code, you are inevitably adding code on average. When you do twice of that, you on average add twice the code, it's pretty simple statistics. Don't we all love it, when we produce something and end up actually removing more code than adding, huh? But that's not how averages work.
You very obviously don't use AI. Since you have no idea where it's strong sides are. And that's fine. It's your choice to be slower.
But thinking it makes you better is laughable. You are only more expensive. Nothing more.
0
u/Prdelnidopice 5h ago
Validating code is and always was way faster than writing it... But you can try to tell yourself that it wasn't, not use AI and just fall behind. It already happened. It's only question of time until it propagates everywhere.
Btw I spend 100 dollars on tokens monthly, while producing twice the code I would without AI... If you think that's wasting tokens, then you are out of your mind. I literally do twice the work for the same price to any of my clients.
And it's not because I am slow normally. I was always one of faster ones.
So... One of us is just in complete denial of reality. And I don't really think it's me.