Start of our notebook (Pointers welcome)

[Foximusprime]

I’ve seen a couple of teams sharing their notebooks for pointers and I thought I would do the same. Any pointers are welcome.

3695B Notebook 24-25 sharable

[Micahy321]

Interesting approach.

I found your sketches very difficult to interpret. Consider using Google drawing or some simple cad to show different angles and maybe some interactions of your mechanisms.

Keep up the good work!

[coding_might_be_fun]

In the code I would use a different font, like this:

void hello(void){
  std::cout << "Hello!\n";
}

[coquettecoder]

I actually really like the concept of having week summaries before the entries! It seems to help understand and pinpoint the aims of that week. I think your notebook is a great start, keep it up!

[GearGrinders]

The text and code isn’t readable. Try using a different font and increase the size. Also maybe make the variable names better and add syntax highlighting

[Foximusprime]

@Micahy321 Thanks! I did those sketches in tinkercad but I will do some paper sketches with more detail and scan them in.

@coding_might_be_fun Will do, I’ll use the monospace version of the same font to avoid the spacing problems I was originally avoiding.

@GearGrinders Thanks! That came from us not really having formal “team meetings” to record but still wanting to record who’s doing what.

@coquettecoder It’s a digital slideshow so you can just zoom in if the text is too small. I’m using the template provided by vex and size 15 is perfectly readable when we print it out. I have fixed the variable names to be more descriptive.

[some.person]

I think it looks good so far, but I think that you’re going a bit too fast and straight to building, since brainstorming is only a single page in each cycle. Also, the big walls of text probably make it harder to read, since the judges will not have too much time to read.