864

submitted 1 year ago by genfood@feddit.de to c/programmer_humor@programming.dev

124 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] blackbirdbiryani@lemmy.world 145 points 1 year ago

For the love of God, if you're a junior programmer you're overestimating your understanding if you keep relying on chatGPT thinking 'of course I'll spot the errors'. You will until you won't and you end up dropping the company database or deleting everything in root.

All ChatGPT is doing is guessing the next word. And it's trained on a bunch of bullshit coding blogs that litter the internet, half of which are now chatGPT written (without any validation of course).

If you can't take 10 - 30 minutes to search for, read, and comprehend information on stack overflow or docs then programming (or problem solving) just isn't for you. The junior end of this feel is really getting clogged with people who want to get rich quick without doing any of the legwork behind learning how to be good at this job, and ChatGPT is really exarcebating the problem.

[-] chicken@lemmy.dbzer0.com 19 points 1 year ago

If you can’t take 10 - 30 minutes to search for, read, and comprehend information on stack overflow or docs

A lot of the time this is just looking for syntax though; you know what you want to do, and it's simple, but it is gated behind busywork. This is to me the most useful part about ChatGPT, it knows all the syntax and will write it out for you and answer clarifying questions so you can remain in a mental state of thinking about the actual problem instead of digging through piles of junk for a bit of information.

[-] wizardbeard@lemmy.dbzer0.com 14 points 1 year ago* (last edited 1 year ago)

The more you grow in experience the more you're going to realize that syntax and organization is the majority of programming work.

When you first start out, it feels like the hardest part is figuring out how to get from a to b on a conceptual level. Eventually that will become far easier.

You break the big problem down into discrete steps, then figure out the besy way to do each step. It takes little skill to say "the computer just needs to do this". The trick is knowing how to speak to the computer in a way that can make sense to the computer, to you, and to the others who will eventually have to work with your code.

You're doing the equivalent of a painter saying "I've done the hard part of envisioning it in my head! I'm just going to pay some guy on fiver to move the brush for me"

This is difficult to put into words, as it's also not about memorization of every language specific syntax pattern. But there's a difference between looking up documentation or at previous code for syntax, and trying to have chatGPT turn your psuedocode notes into working code.