3 ms·
Key part of the study is that it gets the logical steps wrong. Worse, it's convincing, so be careful. LLMs are great for finding key words in a domain you don'
by godelski 2y ago
Key part of the study is that it gets the logical steps wrong. Worse, it's convincing, so be careful.
LLMs are great for finding key words in a domain you don't know which you can then use to search.
As a mostly self taught programmer the advice I'll give it to read docs and learn to read code. This is when my skills really increased. It's easy to get caught up in trying to just find the answer and doing these things definitely takes longer. But it has a multiplicative effect. You'll not only learn to be able to do it faster but you'll need to do it less often. So never pass up the opportunity to learn. There are times you need to rush but they're far less often than you think.
The other big advice I have is two strategies when coding. First write it quick and fast. Sloppy is okay, you're learning to solve the problem (move fast and break things). Then while you're cleaning up the mess you made, document. While you're doing that it'll stress the lessons into your memory and you'll almost always discovery things you missed. It is literally the rubber ducky method. Plus, you get the benefit of docs (others will read your code. And months or years later you'll come back, asking what idiot wrote this garbage to only find it's you. But also, that's a good sign, because you improved!). The second point is that the best code is flexible code. Remember that you suck at code (the secret is we all do) and you're going to have to come back, edit, and debug. So by writing flexible code you're making life easier for future you. It's really easy to forget these lessons because we think in the moment and our egos don't want us to admit we're bumbling idiots, but like in a video game, when it gets harder it means you're progressing. Don't misinterpret that signal.
- alabhyajindal 2y agoThanks for the advice! > As a mostly self taught programmer the advice I'll give it to read docs and learn to read code. This is when my skills really increased. How did you improve your ability to read code? It's currently hard for me to understand a largish codebase written by others without much documentation. eg. I thought of contributing to htmx [1], cloned the repo but couldn't make heads or tails of the codebase - even though it's a single file, albeit a long one. 1. https://htmx.org https://htmx.org
- godelski 2y ago> How did you improve your ability to read code? You're going to hate me for this, but it's by reading lots of code and being very very confused. When tackling a large code base I still pull out pen and paper and create flow charts. And don't fret that you suck at it now. These are really hard things but they take time