[rethab]

This is great advice. Unfortunately, all these AI tools make it far too easy for beginners to not follow it. I'm not sure if all this advice will become irrelevant or if those programmers trained in the 2020ies will not become those "best"..

[Cthulhu_]

Everything comes in cycles I think. There will be a wave of AI generated stuff, but then people / companies will be hit hard by bugs and problems and will reinvent the wheel of quality assurance.

I wonder if AI generated stuff would pass our existing checks, e.g. linters, test coverage, sonar, etc.

[bluetomcat]

> I'm not sure if all this advice will become irrelevant or if those programmers trained in the 2020ies will not become those "best"..

It's how they use the AI. If they see it as a glorified StackOverflow where you paste a big chunk of code and ask "why does it not work", they'll be in trouble. If they are able to narrow-down their problems to a specific context, express them well and take the output of the AI with a grain of salt, they'll be 10x programmers compared to what we were in the 2000s, for example.

[dehrmann]

You could argue that a "feature" of Stack Overflow is the culture. They're building a reference, not a help desk, so they expect questions to be original and researched. Once you're in a corporate environment, if you don't have experience in asking good questions, you'll come off as incompetent.

[taneq]

I dunno, do they really make it that easy? From what I've seen they can give you some example code, and often it works, but when it doesn't, you actually need to know what you're doing to fix it up.

Fixing someone else's code is a great exercise, so maybe they're actually learning useful skills by accident? :)

[epolanski]

I'm kinda conflicted that you shouldn't use AI.

With a good combination of Cursor, NotebookLM, flashcards (I use RemNote) and practicing you can accelerate a lot your learning.

Nothing stops you from reading specs, docs and having AI assist you doing so.

[ancientrevolver]

Your workflow sounds interesting.

I understand the power of flash cards and SRS in general. But was wondering how you decide when to put something into an SRS when learning something new. Especially in a tech/programming context.

[epolanski]

I add stuff in general that I'm curious about, want to learn for long-term, or is important in that specific period of time.

It's a bit random, with time I then ignore some topics.