Chapter 1 - Aside - Consider adding teardown / cleanup instructions

[alexfdrover]

If the reader were to follow the instructions in Chapter 1 and then decide to no longer follow the book, what actions (if any) would be required by the reader to restore their system to the pre-book state?

If actions were required, consider listing them or adding a teardown script.

If no actions are required, consider highlighting that point and explaining why no further actions would be required.

[superggn]

actually this whole project runs on linux, in the video jonhoo mentioned that he's not sure whether this can run on win, macos or other unix-like system
I think you can consider buy an ecs / run a virtual machine to run it, if anything goes wrong, re-install the system image or just delete it then buy a new one.

I'm not reading this book but following the video, I've finished the first 2 parts and not planning to go through the 3rd part immediately, cause as jonhoo said, his videos are so-damn-long...

what I recommend (my learning process):

• check the repo(https://github.com/jonhoo/rust-tcp) first, search the timeline to find the commit where jonhoo accomplished at the end of each video, read the code
• try figure out the main idea of the code at current commit
• you can write down what each variable means in comments, you know the project's var naming is so difficult to read... at least for me it's hard to tell that a connections actually means quad_to_connection hashmap
• watch the video, I recommend you mainly follow the design idea demonstrating part, you can 10x speed go through the debugging part (follow the debugging part and try copy every movement is such a stupid thing, and miserable... just denote what test you can make)
• "if you find yourself tired, you can get away and go back whenever you've restored power and feel interested again" --- jonhoo in "why my vids are so damn long"