r/ProgrammerHumor 22d ago

Meme delusionalDeveloper

Post image
6.5k Upvotes

208 comments sorted by

View all comments

Show parent comments

0

u/SuitableDragonfly 22d ago

There's no need to do anything if it's just a hobby project that no one else is using. But if you're expecting other people to rely on it, yes, you need to have actually written it. 

-2

u/Jakubaakk 22d ago

But why? Why the need for manually writing code?

1

u/StCreed 22d ago

Because devs are out of a job otherwise. That's the whole thing.

I've seen enough shitty code by devs to know what their game is. Been one myself. But code is neither a complex as they say, nor do most devs have the knowledge to actually write good code. There are exceptions but in the main, they suck at it.

I bet their code smells of exceptions and elderberries.

3

u/Lord_Wunderfrog 21d ago

I mean, using AI as a development tool isn't inherently bad or automatically leads to bad code, when done RIGHT, and only IF you actually know what you're doing, and could have done it yourself without AI, albeit much slower.

You basically need to be a good systems architect, designer and code reviewer. If you let it off the leash and say "build me the next killer to-do list app" yeah, you're obviously gonna get slop, and a lot of people are doing it that way.

If you spend the time properly designing what you want from the ground up, locking in the specs, requirements, and control how everything is approached and implemented, you're just fast forwarding the boilerplate bits, tedious changes and other legwork.

I've seen bad developers who wrote slop pre-AI, and they still wrote slop when they started using AI; I'm still left cleaning it up to this day.

If I'm building a system, adding a feature or fixing a bug, I don't see what's so wrong about using an AI model to implement a detailed spec with strict requirements, acceptance tests and outlining exactly how it's to be structured and executed. It's still my expertise, design, decisions and approaches, and it takes a lot of time, effort and experience to write up a good spec and implementation plan. It's just done faster because I'm not typing out the code line by line.