Am I the only one that likes to see the code before the explanation when trying to learn something??

I don't wanna read the explanation I only wanna see the code

the words literally confuse me. this might just be a problem in rust though

@jestdotty well I'm staring at a wall of text that I am really fucking sure can be less wordy for some C networking code. I'm just frustrated cause half of it I know from other languages but some I don't that's C specific so I'm caught in this line of I feel like I have to read it but it ends up for the most part being shit I already know and they're taking forever just to show me what I'm there for.

Same, I skip the whole bunch of paragraphs and only focus on the code.

If I don't understand the code, then I search the explanation in the paragraphs.

I know this is not a good practice... ☹

I also don't know if it's because of my autism that I am bad at R/W texts but very good with symbol/number

So you end up with no knowledge of design choices at all. You won't catch dem "drift"

@retoor no one ever describes design choices

also I do sometimes read the code and if it confuses me read the text. that doesn't help more than half the time though. generally I need to hunt for other examples of the same code

incidentally, this is also how I learned math. never paid attention in class, just guessed what it was doing from looking at enough problems

I jump between code and explanation

Yes I wanna see a bit of code first, then I’ll check if the code matches the genral idea, then resume reading code, the might get confused by a code detail and find it is clarified in the explanation…etc

@cho-uc @jiraTicket code first then seek answers to questions is kinda how I've been making it work.