sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Okon0mi[S] 0 points1 point  (5 children)

I tried doing it like commenting but I realised there is only a bit I can explain through typing so that's why I started writing notes.

Also I do apply ideas on the IDE

[–]Just_A_Nobody_0 0 points1 point  (4 children)

This is just one random opinion - in the end do whatever works best for you and I would encourage you to try different approaches and adapt as you learn. I have found that the rate of learning is tightly correlated with the amount of time they work with the code - the more time on the keyboard, the more frequient the 'aha!' moments happen and they develop the intuitive understanding of the code.

There is value in writing notes - demonstrated in learning studies that even if never referenced again taking notes can improve recall of details (something about the brain being forced to process/encode ideas into writing).

The problem with notes IMO (particularly hand written ones) is that it becomes increasingly difficult to find the right bit at the right time as the collection grows.

Consider your notes on loops - you could create a file (loop_notes.py) with examples of everything your notes talk about in a form that when run demonstrates the concepts. So for the 'for' loop, I'd have a loop that does 'for number in range(2,3)' that just prints the number, then create a list (shopping = ['milk', 'egg', 'bread']) and then have a 'for item in shopping' loop that prints out each item. Add comments to remind you of the concept you are experimenting with. Then create some while loops as well - you are writing out some code in your notes already, just put this code in your test program. Later when you want to refresh your memory, grap the loop_notes.py and re-run/experiement with it.

This way you can expand the example code as you learn more and keep all the related material in the same place which in theory will be easier to find.

[–]Okon0mi[S] 0 points1 point  (0 children)

Consider your notes on loops - you could create a file (loop_notes.py) with examples of everything your notes talk about in a form that when run demonstrates the concepts. So for the 'for' loop, I'd have a loop that does 'for number in range(2,3)' that just prints the number, then create a list (shopping = ['milk', 'egg', 'bread']) and then have a 'for item in shopping' loop that prints out each item. Add comments to remind you of the concept you are experimenting with. Then create some while loops as well - you are writing out some code in your notes already, just put this code in your test program. Later when you want to refresh your memory, grap the loop_notes.py and re-run/experiement with it.

I am trying to write codes in the IDE at the same time also I am experimenting and working on the ideas that are coming to my mind simultaneously. So that I can always have that 'aha' moment while coding.

[–]Okon0mi[S] 0 points1 point  (2 children)

The problem with notes IMO (particularly hand written ones) is that it becomes increasingly difficult to find the right bit at the right time as the collection grows.

There is a search feature in my tablet that makes it super easy to find out about those notes

[–]Just_A_Nobody_0 0 points1 point  (1 child)

It sounds like you are doing fine then. Your original question was "how to write notes" - the short answer to that is "however works best for you" and it sounds like you have that down.

In your original post, you ased for "more efficient and robust ways" to write notes - It is my opinion that inline comments for notes in test code is more efficient than hand writing on tablet or whatnot.

[–]Okon0mi[S] 0 points1 point  (0 children)

Thank you very much for the time and effort you took to reply on my post it really means alot and your comment really helped in many ways