After some significant revising in Part 1, the map at the start of the book is no longer accurate. It needs to be updated.

• Remove "More Math"
• Rename cities to match new level names.

Revise Level 24 so that it can be included in future Early Access releases.

People who have purchased the 3rd Edition in the past need to be told about the 4th Edition being in Early Access, and given a discount code for it. Send an email out to them.

Two errors in this one sentence. Should be "The compiler can often infer what types are in use..." but I wonder if it couldn't also be made clearer a different way. Maybe "The compiler can often infer the type of a variable from how it is used. Listing var as a variable's type tells the compiler to use the inferred type, instead of writing it out yourself. (But the variable still has a specific type.)"

The website needs to be updated with a post about Early Access now being available.

I've had two reports of XP being wrong, when comparing the chart at the beginning of the book against what the book actually says. I need to systematically go through them all and make sure they are right, and consider if making references to the numbers is worth the overhead to be able to know that XP will either be right or broken links.

Revise level 31 so that it can be included in the next early access revision.

This is a comment in the early part of the book before learning about comments. I don't think it adds any real value, and should be removed.

This is a test of the emergency issue system. in the event of an actual issue life would of collapsed in on itself and time would end. thank you.

Revise Level 26 so that it can be included in future Early Access releases.

Revise Level 30 so that it can be included in the next early access revision.

This should be "In other cases, you may spend a while..."

Eventually, I need to create and post solutions to all challenges in the book. I have not been doing that as Early Access progresses, but the challenges in Level 24 are substantial enough that they deserve the solutions now rather than later.

The scope of this story is to create solutions for each of the nine challenges contained in Level 24 (The Catacombs of the Class) and put them on GitHub. A ZIP file of that repository will be placed in the artifacts for the EA3 download. The solutions do not need to be on the website yet.

• The Point
• The Color
• The Card
• The Locked Door
• The Password Validator
• Rock-Paper-Scissors (Design)
• 15-Puzzle (Design)
• Hangman (Design)
• Tic-Tac-Toe (Full game)

Typo. Should be "describing".

"By knowing a variable's type, we know how much actual space in memory we must reserve for the memory location, among other important benefits."

For starters, this should be:

"...how much actual space in memory we must reserve for the variable, among other important benefits."

But it could also maybe be shortened to "By knowing a variable's type, we know how many bytes in memory to reserve for the variable. Knowing a variable's type is also key in getting the compiler to make sure we are using our variables correctly."

The "among other important benefits" is not a very helpful phrase. If I don't elaborate on what those benefits are, then I should just delete the phrase.

"Modern day programming is complex and challenging, but a programmer does not have to go it alone."

The "go it alone" phrasing was reported as being confusing/wrong. I'll look into seeing if there's a way to phrase this differently.

Revise Level 19 so that it can be included in future Early Access releases.

This one is grammatically correct, but not as clear as I had hoped. Figure out a different way to phrase it, or consider just removing the sentence. I'm not sure it adds much to the challenge.

issue

Revise Level 23 so that it can be included in future Early Access releases.

Revise Level 18 so that it can be included in future Early Access releases.

The book is going to leave out some details about configuring nullability checking and leave that to an article on the book's website. This story requires writing and posting that article so that it is available when the Null References level is published.

"String interpolation and verbatim strings can be combined by using $ and @ together."

The order doesn't matter, and saying so would be good.

The table at the start of the book uses 150XP, but the book itself uses 200. 200 is the right number, and the table at the start needs to be updated.

Should be more like "You cannot change a variable's type on the fly, nor is it a catch-all for any type of data."

For digital downloads, I want a single page map in addition to the two-page map at the start of the book. For a digital download, it is okay for this map to be larger than a sheet of paper.

This is a typo. Should be "how to not show it".

Revise Level 17 so that it can be included in future Early Access releases.

Revise Level 25 so that it can be included in future Early Access releases.

Revise level 29 to allow it to be included in the next early access release.

This needs to happen sooner or later, but there was a request to do it sooner rather than later for school bookstores.

This won't get the book available for purchase any time sooner, but may make the stores feel like things are ready to go for when that time arrives.

Revise Level 21 so that it can be included in future Early Access releases.

The introduction currently uses Arabic numerals (0-9), even though it is currently considered front matter. That means there are two pages labeled Page 22 in the book, which is bad.

There are two potential solutions:

1. The Intro was originally supposed to use Roman numerals instead. Make this work like it used to.
2. Make the Intro and possibly the Acknowledgements use Arabic numerals, but start page numbering over when that starts and do not reset it afterwards.

• The Fountain of Objects
• Small, Medium, or Large
• Pits
• Maelstroms
• Amaroks
• The Flooded Cavern
• The Map

This should be "This is a strategy that programmers often use, giving it the name divide and conquer."

This should read "and has its place"

"...you will the contents of memory as well..."

should be

"... you will lose the contents of memory as well..."

"Remember that names are meant for humans to use, not the computer. So pick names that help human programmers make sense of what is going on, not things that you think will make life easier for the computer."

This was reported as being unclear, and I agree. A suggestion was made to make it "Remember that variable names..." and I think that's a good suggestion. The second part was also reported as being unclear. Perhaps the following is clearer?

"Remember that variable names are meant for humans to use, not the computer. Pick names that help human programmers understand what it is for."

In the XP bar, Part 1 is called Procedural Programming. In the rest of the book, it is called The Basics.

The two should be the same.

The Early Access version will be available on Gumroad. The download needs to be created and placed there.

"Bit" is defined, and both the terms "bit" and "byte" are used a lot, but "byte" is never defined. Maybe it should be.

Revise Level 15 so that it can be included in future Early Access releases.

Revise Level 27 so that it can be included in early access releases.

Apparently the XP on this is wrong too.

"Of the IDEs we discuss in this level, this is the most feature rich and capable, though it was one important drawback:..."

Should be:

"Of the IDEs we discuss in this level, this is the most feature rich and capable, though it has one important drawback:..."

Revise the level on structs to allow it to be included in the next early access release.

Revise Level 16 so that it can be included in future Early Access releases.

Revise Level 22 so that it can be included in future Early Access releases.

Revise Level 20 so that it can be included in future Early Access releases.

This was reported as incorrect (should be "foundations" not "foundation") though I think it could be okay. But that bullet point isn't all that great in the first place. Perhaps something more like, "These types are the building blocks of a much larger type system."