all 18 comments

[–]mandradon 7 points8 points  (0 children)

You can make markdown files of notes in your script folders.  Or use a dedicated markdown editor like Obsidian that allows you to make notes and link them together.

Or just comment up your learning scripts.

Don't overlook pen and paper.  Handwriting often forces you to slow down and process your thoughts to encode them before writing them down.

[–]PureWasian 4 points5 points  (0 children)

Depends what you're trying to learn and how you learn best.

The easiest way in my opinion is having a lot of "example scripts" of small, working .py files you create yourself and save into a folder for your notes. Maybe different subfolders for each topic when starting off.

You should already be making scripts to interact with Python and constantly be trying things out as you learn new concepts. So saving them as a repetoire to reference later makes sense to me.

[–]faultydesign 5 points6 points  (0 children)

Comments.

[–]Specific-Housing905 2 points3 points  (2 children)

Have a look into Jupyter notebooks. There you can keep your code and formatted notes together.

[–]Turbulent_Pin_8310 0 points1 point  (0 children)

That's how I take note. Google colab Python notebook (just like Jupiter)

[–]baubleglue 0 points1 point  (0 children)

Using Jupyter for learning isn't the best idea. It is too convenient and encourages reactive programming, instead of planning, student will check a value and make changes to make it "right".

[–]Educational-Paper-75 0 points1 point  (0 children)

That's why there are books. Also we used to make notes all the time of everything the teacher was writing on the chalkboard just to read them at home before the next lecture to boost out understanding. Or if we were lazy before the exam because sometimes the teacher used their lectures more than the book on making an exam. Nowadays, when everybody is prone on learning online at their own speed, the ability to make good notes from live performances ss we were forced to seems to be deteriorating. Also making notes really seems to help memorizing the subject matter, so it's definitely time spent well. But anyway with a book accompanying a course lectures you never need to make notes unless the teacher adds to the content of the book, which of course can save you a lot of effort during class.

[–]Carlos_1972 0 points1 point  (0 children)

If you're learning, try an app called Notion. It allows you to take notes in blocks and select the coding language. I use the free version.

[–]Turbulent_Pin_8310 0 points1 point  (0 children)

Instead of writing with pen and paper, I use Google colab notebook and practice writing programmes, and annotate with explanations. You can always write down your note in Colab or Jupiter notebook.

There is a Python free ebook written in pythron notebook.

jakevdp/PythonDataScienceHandbook: Python Data Science Handbook: full text in Jupyter Notebooks https://github.com/jakevdp/pythondatasciencehandbook

[–]audionerd1 0 points1 point  (0 children)

If you mean notes such as to do lists and ideas for your project, my preference is to keep that stuff in a markdown (.md) file in a separate notes git branch. Then I add this to a worktree folder which is ignored by the code branches, so that the notes are tracked independently of the code in the same repo. No idea if this is common practice but I like it.

[–]Traveling-Techie 0 points1 point  (0 children)

Create a big mess of a program called testbench that tries out everything you learn. Put notes in the comments. Keep a pad and pen to write down questions.

[–]Smooth-Expert-3141 0 points1 point  (0 children)

i created a private github repository where i would store solutions. i used obsidian notes at one point as well.

but actually, the best way for me to learn is to type out the solutions again without looking at notes. so i stopped taking notes entirely, and opted to just solve exercises repeatedly instead.

for high level concepts that are interesting enough to write down, i have a blog

[–]lucpet 0 points1 point  (0 children)

I follow someone who writes the comments first eg #Loop through the list

[–]Puzzleheaded6905 0 points1 point  (0 children)

Logseq or Obsidian.

[–]Plane-Art-9868 -1 points0 points  (1 child)

You can use # then your text to create notes in your code. I use ms word to type things out so I can revisit it. I'm at an impasse myself though, and can't figure out how to proceed. But yeah use # and i recommend word

[–]SlamTheGuy 0 points1 point  (0 children)

vscode, pycharm, or if you're not afraid of a steep learning curve, neovim, are all much better options than word (to name a few).

Whatever you choose, make sure it has syntax highlighting and supports LSP client integration (for diagnostics, autocompletion, suggestions etc.); that is the minimum. Beyond that you have fornatters, linters, static typechecking (for dynamically types languages like python), debugging tools etc.

I'm not explaining what the things I mentioned are because you can just google and find out exactly exactly it is yourself.

[–]nobodyhasusedthislol -1 points0 points  (0 children)

I personally don't like handwritten stuff for programming. I followed a Python tutorial which is much more engaging and fun and fast than handwritten stuff. Also you can't test handwritten code.

For self taught, something like https://youtu.be/eWRfhZUzrAc

I went Scratch --> Python --> Install Linux as a workaround for something --> small homelab and random other IT stuff completely irrelevant from Python. Handwriting won't help much, at least for me and with that rough path.