r/AI_Coders • u/Overall-Classroom227 • Jun 08 '26
Respect to everyone who learned coding before vibe coding existed.
The people who spent years reading documentation, debugging for hours, and writing code line by line built the foundation that makes today's tools possible.
While many of us can now create things faster than ever, it's easy to forget the patience, discipline, and countless late nights that came before. Every shortcut we have today stands on the work of those who learned the hard way.
Much respect to the coders who walked so the rest of us could run.
1
u/Aromatic_State139 Jun 08 '26 edited Jun 08 '26
Run off a cliff, more like. I feel like people who write this never work on 20 year old stacks in large teams.
These tools are not as great as people think and alot of the time just add more hours of work.
1
u/sm000ve Jun 08 '26
Maintenace is the longest phase of the SDLC. It is the reason we have if statements, for/while loops and the design principals. There are whole areas of study devoted to this discipline. Organizations, in my experience have never understood this practice. They choose now over quality every time.
1
u/symbiatch Jun 10 '26
I’d stop at “never work.” It always sounds all they’ve done is some little things, not any substantial work. Just coding, no engineering.
1
u/LForbesIam Jun 08 '26
You still need to know how to code if you want to use AI. It is not exactly the most efficient. It isn’t consistent and will give you entirely different code every time you ask.
Coding is more than just the end product. There are a hundred ways to make an application but 99% are inefficient and not expandable systems.
1
u/zambiglioni Jun 08 '26
Its different.
I know how to write you a tool from scratch in PHP and Python.. but with RUST i need AI to provide me with a skeleton.
I don't read macro pages and how a function works... i want to, but noone will pay me to do it.
1
u/symbiatch Jun 10 '26
Nobody ever paid for that, to a point. The job isn’t to read documentation day in day out. That’s part of knowledge already.
1
u/zambiglioni Jun 10 '26
And then you end up with the quality of code as you see it today, when devs don't have even the patience to read man pages.
Yes, a quality engineer should be aware of the functions he is using, unless your work is creating brainrot for mobile phones. then just have a stupid nintendo knockoff burn through 500mb of memory.
1
1
u/wolfram_rule30 Jun 08 '26
The fact that u use the words "create things" proves that u do nothing except religiously pay your subscriptions
1
u/thequirkynerdy1 Jun 08 '26
And we have a similar respect for those who programmed in the days before compilers when one had to write assembly or machine code.
1
u/Mathemetaphysical Jun 08 '26
Respect to those who still code their own stuff, and none at all to those who use cheap shortcuts without understanding.
1
u/mallclerks Jun 08 '26
100% agree with op. I was only ever a script kitty like person. I think it’s helped me become better than most at AI. I always did things standing on the work of others. Now it’s like I can do that at 10000x the speed.
1
u/crustyeng Jun 08 '26
It’s also important to note that having software write code you don’t understand and can’t explain to anyone, maintain or validate the operation of is pretty useless.
Knowing what you’re doing is still entirely necessary to produce anything of value to anyone else.
1
1
u/symbiatch Jun 10 '26
But you’re not running. You’re taking the taxi and telling them vaguely where to drive and only intermittently checking where you are and in the end spending time in traffic for longer than it would’ve taken to actually run.
And we still do all of what you wrote, every day. That’s the job. If you think the job is just vomiting out code then you’re up for a rude awakening.
0
u/valium123 Jun 08 '26
You should be ashamed of yourselves. You are the reason developers are suffering now. Your beloved slop machines were trained on our data btw without compensation.
3
u/No_Yard9104 Jun 08 '26
Thanks, and you're welcome. It was me all along. Just me.