A labor of love that would benefit from reorganization and editing.
It could also use a round of fact checking. Some of the info appears to be based on third-hand speculation.
It could also use a round of fact checking. Some of the info appears to be based on third-hand speculation.
Statements denoting speculation are started with words like 'presumably' or 'it is assumed that'.
I've also took an extra month to send the draft to many experts (part of whom are still active in the Xbox 360 scene) to gather feedback and make all the appropriate corrections. See the 'Changelog' at the end of the article.
I'm afraid I can only do so much. Just like you said, this is all voluntary work. I also keep a repo with all the manuscripts to correct all the mistakes after publishing any content (https://github.com/flipacholas/Architecture-of-consoles).
I don't know how else I could improve this, but I'm always open to suggestions.
I don't know what you mean with reorganization and editing.
I issued a minor correction on the GameCube article and you were extremely quick to correct it.
Op: if you’ve found something, please post it. Everyone benefits :)
The overwhelming tone of the comments here is positive. You took a complex subject , researched it deeply , open sourced it . That’s so rare.
Ignore the haters, always.
You should ask yourself “why am I writing this document“, and then check to see if the document is achieving your goals. I am guessing your goal is “I want to serve as the definitive publicly available textbook for the Xbox 360.“. If that’s your goal, I would split the doc into chapters by topic, and then edit the heck out of each chapter. Look at a model textbook like Computer Architecture, a Quantitative Approach, and see if you can imitate their style.
I think a good technical editor could help you edit this down to about 25% of the words, and still cover the same information.
The job is too big for drive-by code review style comments. You’re going to have to put in the work yourself if you want to improve this.