Loading...
  OR  Zero-K Name:    Password:   

Post edit history

learning to code

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
2/20/2024 9:23:08 PMUSrankchaplol before revert after revert
2/20/2024 9:15:38 PMUSrankchaplol before revert after revert
2/20/2024 9:13:12 PMUSrankchaplol before revert after revert
Before After
1 When I took a high school programming class, the way the class worked was that we would literally transcribe code from a textbook into a compiler. More often than not, the verbatim code never worked. Regardless, the goal was to make a program that could run, so were effectively forced to understand what the code was doing so that we could correct the typos and logic bugs. Weirdly, my classmates and I would pick were successful at picking up the language despite just transcribing. Not sure if that was the goal, but it was nonetheless a very, very useful learning method whose effectiveness surprises me to this day. 1 When I took a high school programming class, the way the class worked was that we would literally transcribe code from a textbook into a compiler. More often than not, the verbatim code never worked. Regardless, the goal was to make a program that could run, so were effectively forced to understand what the code was doing so that we could correct the typos and logic bugs. Weirdly, my classmates and I would were successful at picking up the language despite just transcribing. Not sure if that was the goal, but it was nonetheless a very, very useful learning method whose effectiveness surprises me to this day.
2 \n 2 \n
3 In other words: Griping about their code will get you nowhere. But fixing their code gives you an important opportunity to learn. Take the opportunity. 3 In other words: Griping about their code will get you nowhere. But fixing their code gives you an important opportunity to learn. Take the opportunity.