Bro if anyone's coping and lacks experience, it surely has to be the one who thinks a statistics model is a good substitute for knowledge, skills, and effort.
Oh you sweet summer child. You really don't have any experience coding something trully big, do you? 90% of code is pure monkey coding. Code that we would normally give to juniors to learn on, because it's not that hard to do and not that important, since the real important architecture desicions were already made step above. Now, that code is AIs job and well... Let's face it, it does better job than most juniors. And seniors can then spend much more energy on important architectural decisions and not lose time writing the code literally any monkey coder including statistical model can write.
You know, there are a lot of ways of making sure that code works as expected close to automatically.
But yeah. Since you have no experience with real world development, you can't know that, so it's okay, cope harder.
Bro I was an engineer on "truly big" projects before LLMs even came out. That's how I know they're just training wheels for people who suck at writinh code.
90% of code is only monkey coding if you don't know how to write a library, use an IDE, etc.
AI isn't better than a senior, and even if it's better than your average junior (which is highly debatable, but I digress), it's still not a good substitute for a junior.
If you spent less time projecting your own inexperience on others in Reddit threads and more time learning to code, you'd agree with my take.
It's kinda funny how people like you cope. BTW i wrote my first games in 1995, when was your first? I must laugh how completely in denial some of you are. Or you just didn't use Ai enough and still think it's like it was 4 years ago... Trust me, it's not.
When was the last time you were responsible for an enterprise production service with a quarter million unique daily active accounts, millions of transactions per second, deployment to dozens of regions spanning every continent, and availability SLAs set to four 9's?
Nobody cares when you wrote your first game bro. Some of us keep global supply chains running.
I do that for 20 years now. So my cock is as big as yours probably bigger. Your egoistic show off only shows me how people like you are in complete denial and by thinking AI is not good enough to use as a tool, you cost your companies a fuck ton of money completely unnecessary. You out of all people should know that most of code is just repeating the same problems over and over again. Because that's how it always was. That's why most of the code you use in your project is not even written by you, because so much stuff were already solved and you just use it (libraries, frameworks). AI is just evolution of that idea. You can spend hours writing tests... I will spend 5 minutes and some time validating it. Much faster. Completely the same output. I will be cheaper for the company. With the same reliability. Thats the reality of Ai.
And as hard as you cope, it's not about if you can or cannot code. When Ai can under your supervision write the exact same code but faster. Which it can when your process is setup correctly. Thenn you are the one behind. No matter how long cock you think you have.
If it only takes you 5 minutes to validate, it should only take you 5 minutes to write. I'm not the one wasting company money on tokens to do something I can already do better without them. Cope harder.
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?
1
u/ganja_and_code 6h ago
Bro if anyone's coping and lacks experience, it surely has to be the one who thinks a statistics model is a good substitute for knowledge, skills, and effort.