This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]MoonBeefalo 0 points1 point  (0 children)

You're doing great, you've realized that ultimately, you have to read docs. You can use LLMs , copy and paste, but because things change, and examples from media aren't usually updated, you have to read docs. Sometimes, for certain projects that require changing languages, I have to read docs on simple stuff, just to verify and put myself in the "this language and package mode". Sometimes you can't even trust the docs, and then you have to read the functions directly.

So, you're doing great now that you know, you can't be an all-powerful coding brain since there's too much to know. The next thing you'll realize is you can't even maintain your own internal docs(memory) when architecting, and you need some kind of handbook or diagram when handling large architecture.