Hey mfort, good question. I've got a single running text file of notes, but it's pretty sparce. I mark the day and time in the notes so I can find the full explanation again. But if I code something during the video then I tend to put notes in the code itself rather than the master text file, which is kind of a hole in my method actually. (This code gets copied every session, so to find something I'd have to go back through all my old versions of the files.)
My goal would be to have very terse "overview" notes, kind of like Iker's nice summaries
.. basically enough for me to remember the structure of things at a glance. The idea is I want to be able to recreate the code from scratch with just a few guiding notes (after all, Casey can!).
My main strategy is similar to yours: basically take notes during the lesson and then try to recreate the code on my own afterwards. However, I'm quite a bit behind on the "recreate on my own" portion :silly: so I can't really report on the effectiveness of this yet.
Also now that we're on game code, my strategy may shift a bit since I don't feel as completely out of my depth here. But also because some of the coding here is exploratory, I don't feel I have to follow Casey so tightly. Just sort of being along for the ride feels like enough. Not sure how I'll end of proceeding here. Right now I'm just taking notes on anything I think I won't remember. (Or hilarious quotes, like Casey's near perfect deadpan delivery of "it's a game about animal safety" in the day 33 pre-stream.)
Do you find it's useful to take notes? I'm not looking for the perfect solution, but I'd like to know what people think about that.
Yes, I definitely find it useful. Although to be honest I'm not sure how often I actually use my notes... sometimes I think just the act of making them helps me remember. I don't get too detailed though... Right now probably the most common thing in my notes are various Windows calls... but here's kind of like what it looks like:
is basically a mask, any F byte will remain
translation lookaside buffer
like a cache for virtual memory addresses
good for us since we're using such a big chunk of contiguous memory
"where" is a Windows cmdline tool that will list the position(s)
of that file in the filesystem IF any can be found (e.g. try "where xinput*.*").
It uses the same logic (as far as I can tell) that DLL loading etc.
use (current folder, PATH, ...).
could draw paths too like the bret victor thing
note: mostly this is so easy because of the way
we set things up, the memory etc...
TOPMOST | LAYERED
(layered doesn't work with owndc, so we'd have to get dc every time and release like normal)
"we could load the executable in the dll
load a handle to that and reverse call into it"
day 21 24m40s
Anyway, that's kind of like what my notes look like. In hindsight I def need to do a proper mind dump of things on my mind now, basically a summary of what we've done so far. As you can see I also put other related notes, like tips from the forums too.