Hey everyone, I just have a question about how programmers take notes / learn new skills. I'm currently learning how to make shaders in Unity but I was just wondering what kind of notes I should be making. I'm not good at some of these algorithms being used (ex creating a vertices for a mesh... etc) but I was wondering if I should take notes on these as well as notes on shaders. in my personal experience, I have trouble learning new things (Practice makes perfect!) but I was wondering if it would be more efficient to spend less time making detailed notes and more time creating content. As of now, I'm working on tutorials / making a game during my free time. 

1 hour ago, MintyLyton said:

Hey everyone, I just have a question about how programmers take notes / learn new skills. I'm currently learning how to make shaders in Unity but I was just wondering what kind of notes I should be making. I'm not good at some of these algorithms being used (ex creating a vertices for a mesh... etc) but I was wondering if I should take notes on these as well as notes on shaders. in my personal experience, I have trouble learning new things (Practice makes perfect!) but I was wondering if it would be more efficient to spend less time making detailed notes and more time creating content. As of now, I'm working on tutorials / making a game during my free time. 

When I was learning to code I just learned the concepts from books or other people and then went on my own to create a bunch of programs using my own ideas. I spent most of my time understanding what (x) does, then making many programs using (x), and adding more as I learned. It was the long hours coding that helped me retain everything, and again most importantly understanding the inner workings of why the code works, not just that it works. This will allow you to code more freely without needing to copy other people's code in future.

The fact is we all learn differently, and what works for one person may or may not work for another. If you need to take notes then do it because there is no reason to cut yourself short during your learning phase. We have to consider that some people learn faster than others. I've worked with people that never seen to catch on, and other people who just need to see it once and they're good to go.

Keep in mind as programmers we never stop learning, there is always something new, and ways to improve our current way in doing things.

I've had to learn new concepts in other fields recently, and the only way I'm able to catch on quickly is to understand why something works, not just that it does. I'm very hands on, and if I understand the 'why', and put in the time utilizing what I learned it will absorb very fast for me.

If you learn by creating content, then do it. If you learn by making notes then creating content, then do it. All the matters is that you're understanding what is going on, and that you're able to retain it.

23 hours ago, Rutin said:

The fact is we all learn differently, and what works for one person may or may not work for another. If you need to take notes then do it because there is no reason to cut yourself short during your learning phase. We have to consider that some people learn faster than others. I've worked with people that never seen to catch on, and other people who just need to see it once and they're good to go.

Thanks for the insight. Most of the time I spend making notes is with the intention of retaining information or looking back if I need them in the future. I just don't want to mistake that with spending too much time spending on note taking rather than learning. 

I think my new question might be now is where to prioritize learning as a programmer while still looking for a job. As it is now, I'm looking for hobby projects to work on since I like creating content to learn / practice skills. Also I'm bad at thinking of content to make to showcase in my portfolio

34 minutes ago, MintyLyton said:

Thanks for the insight. Most of the time I spend making notes is with the intention of retaining information or looking back if I need them in the future. I just don't want to mistake that with spending too much time spending on note taking rather than learning. 

I think my new question might be now is where to prioritize learning as a programmer while still looking for a job. As it is now, I'm looking for hobby projects to work on since I like creating content to learn / practice skills. Also I'm bad at thinking of content to make to showcase in my portfolio

In my 18+ years I don't recall taking many notes. I'm more about "doing", not reading and writing notes. I like to create projects as soon as I learn a new concept.  In all the fields I'm involved I rarely write notes, but I retain information like a sponge though...

Depending on how you learn, I would suggest that you find something you're passionate about and use that as a way to justify creating projects. For example, if I'm very interested in space, I would tie in my learning by creating space based programs and games, I wouldn't spend that time making boring bookkeeping examples like you see in many of the older programming books, ect... Unless you're into that sort of thing.  

If you're struggling to create content you have two options. Find a game or program you really like, and make a clone of it.  Your other option would be to check out the hobbyist section on GameDev and join a project.

When you're creating a portfolio as a "programmer" it's not meant to be a visual showcase. Your object is to show how you code, put projects together, and solve problems. Showing that you made a fire ball shoot out of a hand visually means nothing, but showing the code behind it does.

27 minutes ago, Rutin said:

When you're creating a portfolio as a "programmer" it's not meant to be a visual showcase. Your object is to show how you code, put projects together, and solve problems. Showing that you made a fire ball shoot out of a hand visually means nothing, but showing the code behind it does.

I was told to make my games visually appealing in my Game Programming College. That idea might have just stuck with me for awhile actually. What I wanted to do was create a list of youtube tutorials for content that might seem appealing to people. One of the ideas I initially had was a complex inventory system which could use custom items, filter through, organize and delete items based on identifier tags. 

23 minutes ago, MintyLyton said:

I was told to make my games visually appealing in my Game Programming College. That idea might have just stuck with me for awhile actually. What I wanted to do was create a list of youtube tutorials for content that might seem appealing to people. One of the ideas I initially had was a complex inventory system which could use custom items, filter through, organize and delete items based on identifier tags. 

There is nothing wrong with making flashy projects for your portfolio, but when you're applying for a programming job the person reviewing your resume and portfolio should be reviewing you for your code, not visuals because it's not important as a programmer; you're not applying as an artist.  

EDIT: I should also add, you're not a "game designer" either, so keep that in mind. What is important is your ability to code.