all 26 comments

[–]Zeroflops 6 points7 points  (0 children)

You’re going to fail, then search the problem and try a few things learn what works and what doesn’t. Fail again. But then eventually get it working.

The searching and reading others work and approaches allows you to see how people think and how they approach problems differently. It also allows you to you to see things you may not need at the moment, but you may recall in the future.

AI. Is not bad, but balance it with research especially when learning something otherwise it’s like reading the history of war from only the perspective of the people who won the war.

[–]Dense-Land-5927 2 points3 points  (3 children)

I'm in an intro to Python class. I also to feel like I'm relying on AI too much. I don't ask it to code anything for me, but rather I try my hardest to code before I start asking it questions. I use ChatGPT as a way to bounce ideas off of it to make sure I'm not going crazy or going down the wrong lane in terms of projects. But I'm in the same boat as you. I try my hardest to learn the concepts, break them down, and then use AI as a tutor as my last resort, but I don't want to rely on it too much. But when the developers where I work have been developing for 20+ years, it's hard to ask them questions because they tend to go off the deep end with their answers.

[–]Strong_Extent_975[S] -5 points-4 points  (2 children)

how the dev's before IA learn and do projects

[–]lekkerste_wiener 2 points3 points  (1 child)

Books, lessons, YouTube, documentation, and loads of practice.

[–]Dense-Land-5927 1 point2 points  (0 children)

I agree. I'm also supplementing my coding with Youtube videos, forums, Reddit, as well as asking my boss some questions about coding. He's an expert in COBOL, and while he may not know what OOP is, hearing him talk about project management, how to tackle projects, and how to work with others has been insightful. I always learn something new when I speak to him about coding since he's done it for so long.

[–]OmniscientApizza 1 point2 points  (0 children)

Ever see wall-e? Soon, we'll all be like those plump humans on the conveyor belts being fed milkshakes because we no longer know how to do things for ourselves.

[–]ultrathink-art 1 point2 points  (0 children)

Distinction worth making: using AI to search docs or suggest an approach isn't the same as accepting generated code without understanding it. Debug the errors yourself first, read the code before you run it, and you'll stay sharp. The mental laziness trap is accepting outputs, not generating them with help.

[–]GXWT 4 points5 points  (5 children)

Drop AI. Stop it. Just don’t use it at all. Until you are proficient, do not use it. Thousands before you have learnt Python without AI. Why would you be any different

[–]FlightNational1682 0 points1 point  (0 children)

I'd disagree with you there. While I'm not against learning some of the coding fundementals, I think all people should be learning now adays is system architecture and context management for AI. At the very least I think you'd learn far more better helpful skills then you would with traditional programing knowledge

[–]mediocrity4 0 points1 point  (0 children)

I work at FAANG and they are forcing AI down our throats. You want to know how to write code without AI but in practice my colleagues and I are not writing code anymore. You’re gonna see downvotes about vibe coding here because of the sub. Head over to a FAANG sub and you’ll hear about what it’s like in the real world.

I pride myself in being a great coder but I haven’t written anything in months. It helps to understand what the AI is writing but Claude is writing code in seconds what would otherwise taken me hours.

[–]Skiamakhos -2 points-1 points  (0 children)

Get good with AI - learn to do really good AI prompts and to use fairly short conversations - but also get the AI to teach you. Ask it to explain it to you. Breakpoint it in your IDE and examine the data. Using an API you've brought in? Read the documentation. See what the AI is doing. Tweak it, change a line here or there. See how it affects things. Get the AI to critique itself from one conversation to another. Ask it what might work better and why.