#Takenote github how to
#Takenote github software
#Takenote github code

For example, we'd have a folder called Higher Order Functions or Object Orientated Programming, and within those folders we'd have all the markdown files about those topics. Typically I like to structure this repo with folders inside that are labelled for a specific topic. The next step is to create a GitHub repository.

#Takenote github code

If you're super new to coding syntax, you can always type the code out in VSCode to get intellisense to make sure there are no errors. This is huge, because it allows us to keep the flow when taking code as notes, as well notes about that code, all in one place. We can do the same for the vast majority of languages out there, and chances are, when you're learning to code, it's going to be Python, JavaScript, or some variant of C, all of which are supported. Note that it's labeled as Python in the second text example, this renders the text as Python code as seen in the first example. This allows us to combine typical note taking alongside code it's such a simple concept but it took me months to figure out. Because it is plain text it can be read by any text editor, and because it's so flexible and part of the standard README format, we can use this our base for writing plain text notes, as well as chunks of code. Markdown is a plain text format that is super flexible.

#Takenote github software

Git&GitHub is critical for every software developer to master, so we can do two things at once with the method I will outline below. People mainly push these services because they're cloud based and have a lot of mindshare.īut what else is cloud based that's more developer friendly? GitHub. It's very clunky and really it only supports the bare minimum. Many online sources cite Evernote and other similar services but they're not built for taking coding notes. With that said, I struggled for a long time on how best to take notes. And once that experience matures you'll find that it's surprisingly easy to make use of other languages. It's much more of a mindset and building up problem solving capability within a specific language.

#Takenote github how to

The primary thing I learned when I finally learnt how to code was that it's lot less about syntax and memorisation than you think. No one remembers these things with complete and total accuracy, and you need look no further than LinkedIn itself to see the vast majority of software engineers at big tech companies posting about imposter syndrome, or how they struggled with something that just wasn't quite worded in a way they were used to. It feels like if you don't grab hold of every possible detail you'll somehow miss something incredibly important - after all, every other software engineer has memorised all the syntax and every single possible design pattern. It's tempting, when learning to code, to just note *everything* down.

Hello there! Last time I wrote classes and object orientated programming, and this time I'll be covering how to take notes when learning to code! What to Take Note of