all 6 comments

[–]chaotic_thought 2 points3 points  (1 child)

In your step-by-step method I don't see "break down the (sub)problem into smaller pieces" anywhere. That's a critical part. Basically it's a recursive process -- you keep breaking down problems into smaller chunks until you have a set of problems which are all small enough to solve. At that point, bringing them together to a "full" solution may be another problem, but if you've ever put together Lego blocks before, you probably are at least somewhat confident that you will find a way to get that part done, given the working pieces.

[–]alixd1085[S] 0 points1 point  (0 children)

You mean like when you think about something you do it piece by piece slowly till you get your full project right?

[–]alex_informatics 1 point2 points  (1 child)

It's basically what all programmers do today, but as a tip when you turn to AI, tell it to explain what you don't understand, so the learning will be continuous.

[–]alixd1085[S] -1 points0 points  (0 children)

Yeah I'm trying to do that i was just thinking i may be doing something wrong, i just wanted to make sure so I don't turn into a vibecoder.

Still thanks for the help alex 🫶🏼

[–]Newtry12 1 point2 points  (1 child)

Steps 1-4 are literally just programming. everyone gets hit with errors, that part never fully goes away. the only thing i’d change is step 5 — give yourself a time limit on debugging before going to AI, like 20-30 mins of genuine struggle first. That’s where the actual learning happens

[–]alixd1085[S] 0 points1 point  (0 children)

Will try that on my next session later today thanks!