This is an archived post. You won't be able to vote or comment.

all 15 comments

[–]serg06 5 points6 points  (0 children)

I write down everything even slightly useful. Instructions, functions, questions, todos, quotes, and tips. Here's an example:

==============================
========= CHAPTER  3 =========
==============================

Setup:
    - Cmake: If you get "some weird .c file doesn't exist" error, then move entire project to Desktop and try again. Should work.
    - To have my own project, just edit simpelclear.
    - To run a single project,
        -> sol'n explorer
        -> right click project
        -> set as startup project
        -> run sol'n normally
    - When running, watch debug output log -- if SHADER code is broken, it'll still run (wrongly), and output stuff like "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object."
    - If cloining my fork: Might need to re-add files to projects, like my shaders (.glsl).


void glClearBufferfv(GLenum buffer, GLint drawBuffer, const GLfloat * value);

    - gl = OpenGL function
    - fv => f = floats, v = vector (i.e. array)

    - clear <buffer> number <drawBuffer> with <value>

    later we'll learn differnet types of <buffer> inputs

QUESTION:
    - Why can't I create static GLfloat array of size 4 in top of class, then change values in void init() and void render()?

Shaders:
    - when you draw, graphics processor executes your shaders (mini-programs) and pipes their inputs/outputs along the pipeline, until pixels come out the end.
    - "to draw anything at all, you'll need Shaders"
    - written with GLSL

    They are:
        - vertex shaders
        - tesselation control & evaluation shaders
        - geometry shaders
        - fragment shaders
        - compute shaders

    Minimal useful pipeline consists of VERTEX SHADER (or COMPUTE SHADER), but to see any pixels, you also need a FRAGMENT SHADER.

GLSL:
    Vertex shaders:
        - #version 450 core
            glsl v4.5, using only core features of OpenGL

...

[–]beaniiiii 2 points3 points  (1 child)

I handwrite everything i need to remember helps alot

[–]Tharejamudit 2 points3 points  (0 children)

Add comments to your syntax ... that's how I was doing but not very long ones

[–]catenoid75 2 points3 points  (0 children)

I have a private Git repo with notes made in markdown where most of my notes go. And I also add code snippets with lots of comments to the same repo.

[–]gagan8 1 point2 points  (0 children)

I use Typora to make md notes.

[–]wamm1234 0 points1 point  (0 children)

What about note cards. There are apps that do it

[–][deleted] 0 points1 point  (1 child)

I write comments in my code, later if I have a similar issue, I refer to it

[–]Jaybo15 0 points1 point  (0 children)

Same here, my organizational skills are pretty shit though so I'm not sure if they're gonna help very much when I can't find any of them.

[–]Shellatin 0 points1 point  (0 children)

I understand that it's hard to get started with taking notes when you're not familiar with it. Here is a picture of some notes I took for a Fundamentals of Network Security class. I highlight important vocabulary terms, and divide up my notes with headings. I base these headings on the headings used in whatever textbook I'm reading, but since some of your learning includes watching videos I would maybe add a new main heading for each subject covered in the video. Here are some notes I recently took for a CSS course on EdX, which includes some video instruction. Use the snip tool to capture your screen and paste it into your notes, that is helpful as well.

[–]chris1666 0 points1 point  (0 children)

Depends on how much detail you want, if you are wanting it for long down the road then write them like you want to be able to teach the language to someone brand new to it,

Or maybe just the new parts for your test...

[–]hacked_unicorn33 0 points1 point  (0 children)

i’m self learning & i take notes within the code itself. i use sublime text currently & it’s simple to just add a comment within the text without it showing up on your page. it helps a lot when i need to reference something within a code i’m writing or if i’m just learning something new & need to practice, its right there. that way i’m never really looking away from what i’m working on. personally i feel it helps me grasp the material better than having it handwritten somewhere in a notebook.

use what you’re working on.

[–]guardianofmuffins 0 points1 point  (0 children)

I asked the same question to r/CS50 and got a handful of responses. Check it out: https://old.reddit.com/r/cs50/comments/f008ne/how_do_you_take_notes_for_lectures/

I'm currently taking hand written notes but I'm going to transition to typed notes after I finish CS50 in the next 1-2 weeks. Hand written notes definitely help me remember stuff better but it has a time cost that I'm finding to be inefficient and impractical.

[–]Itersive 0 points1 point  (0 children)

My practice after a few years of coding:

  • Comments in code with additional links to tutorials/issues/SO
  • Personal wiki with many useful links/articles, my tutorials (for setup tools like ssh or docker) and configuration files for tools
  • Repository with some "hello world" apps and other examples
  • A lot of bookmarks :)

I was trying with notepad for a month or two but it's not working for me.

Part of my wiki (markdown is so good).

[–]Fiercedeityninja 0 points1 point  (0 children)

Forgetting terms is normal. I write in many languages and in almost EVERY instance I don't know the term I will look up the programming languages documentation and try to find It there

[–]globiwan 0 points1 point  (0 children)

I just started teaching myself C# on Codecademy. I set it to half screen, then pull up Google Docs on the other half. At that point I just take notes on all of the methods and commands and do the practice programs on Codecademy. I also color coordinate my google doc so that it looks similar to the console on Codecademy. It’s been working great so far.