Looking for Proofreaders for my new Book: C++ Core Guidelines
I’m looking for proofreaders for my new book “C++ Core Guidelines”. The crucial idea of the book is to put the precious ideas of the C++ Core Guidelines into a readable book for the big audience. This book includes more than a hundred examples to study the theory in praxis.
Let me write a few words about the book.
My Motivation
Here are the essential lines of my E-Mail discussion in May 2019 with Bjarne Stroustrup and Herb Sutter telling them that I want to write a book about the C++ Core Guidelines: “I’m an absolute fan of the value which is inside the C++ Core Guidelines because my strong belief is that we need guidelines for the correct/safe usage of modern C++. I often use examples or ideas from the C++ Core Guidelines in my C++ classes. The format reminds me of the MISRA C++ or AUTOSAR C++14 rules which is presumably intentional, but this is not the ideal format for a big audience. I think, more people would read and reason about the guidelines if we would have a second document which describes the general ideas of the guidelines.“
About the book
C++ Core Guidelines is a journey through best practices for writing modern C++. The best practices are based on the rules presented in the community-driven GitHub project C++ Core Guidelines. The book contains the following chapters:
- Philosophy
- Interfaces
- Functions
- Classes and class hierarchies
- Enumerations
- Resource management
- Expressions and statements
- Performance
- Concurrency
- Error handling
- Constants and immutability
- Templates and generic programming
- C-style programming
- The standard library
For a better idea of my book, I attached the chapter to functions to this post. At least you get a concrete idea of the content.
You can download it here:C++CoreGuidelines.pdf.
Here are the missing facts about proofreading my book.
State of the book
I finished the first draft of the books. The book has roughly 300 pages. This first draft is cooked well enough for proofreading. I will replace the images which are at the beginning of each chapter with illustrations.
Modernes C++ Mentoring
Do you want to stay informed: Subscribe.
Who publishes the book?
- The book will be published by O’Reilly. I assume it will be available in the digital and printed version.
When will it be published?
- The book will be published in November/December this year.
What’s your job?
- Proofreading the entire book. You don’t have to read the chapters in sequence. I send you the book as pdf. If you are done with a chapter, send me the pdf back with your comments inside the pdf. I will update the book weekly; therefore, your comments are based on the newest version. This process worked quite well with my last two books for Leanpub (see footer) and is most comfortable for you and me.
- Look for all kinds of errors in the book. These errors may include
- typos
- syntax error in my American English or C++ programming language
- inconsistency
- …. (four dots, not three)
- Make further suggestions about the content and the structure of the book.
- Just write to me about what you think could be improved.
What are the requirements for proofreading?
- To be honest, you have not to be a C++ expert. If you don’t understand some explanation, it’s probably my fault.
- It’s very helpful but not necessary if English is your mother tongue. The book is written in American English.
What do you get?
- A printed version of the book.
- Learn, how you should write in modern C+.
- I will mention you in the book.
How to contact me?
- Use the contact button in the left column of this web page.
- The call for proofreaders is open for two weeks. Therefore, it will end on the 12th of April
- I’m looking for 5-8 proofreaders. So if more than 8 people want to proofread the book, I have to choose the right ones. Therefore, it helps me a lot if you say a few words about yourself. The few words are only necessary if I don’t know you.
Modernes C++,
Thanks a lot to my Patreon Supporters: Matt Braun, Roman Postanciuc, Tobias Zindl, G Prvulovic, Reinhold Dröge, Abernitzke, Frank Grimm, Sakib, Broeserl, António Pina, Sergey Agafyin, Андрей Бурмистров, Jake, GS, Lawton Shoemake, Jozo Leko, John Breland, Venkat Nandam, Jose Francisco, Douglas Tinkham, Kuchlong Kuchlong, Robert Blanch, Truels Wissneth, Mario Luoni, Friedrich Huber, lennonli, Pramod Tikare Muralidhara, Peter Ware, Daniel Hufschläger, Alessandro Pezzato, Bob Perry, Satish Vangipuram, Andi Ireland, Richard Ohnemus, Michael Dunsky, Leo Goodstadt, John Wiederhirn, Yacob Cohen-Arazi, Florian Tischler, Robin Furness, Michael Young, Holger Detering, Bernd Mühlhaus, Stephen Kelley, Kyle Dean, Tusar Palauri, Juan Dent, George Liao, Daniel Ceperley, Jon T Hess, Stephen Totten, Wolfgang Fütterer, Matthias Grün, Phillip Diekmann, Ben Atakora, Ann Shatoff, Rob North, Bhavith C Achar, Marco Parri Empoli, Philipp Lenk, Charles-Jianye Chen, Keith Jeffery,and Matt Godbolt.
Thanks, in particular, to Jon Hess, Lakshman, Christian Wittenhorst, Sherhy Pyton, Dendi Suhubdy, Sudhakar Belagurusamy, Richard Sargeant, Rusty Fleming, John Nebel, Mipko, Alicja Kaminska, Slavko Radman, and David Poole.
My special thanks to Embarcadero | |
My special thanks to PVS-Studio | |
My special thanks to Tipi.build | |
My special thanks to Take Up Code | |
My special thanks to SHAVEDYAKS |
Modernes C++ GmbH
Modernes C++ Mentoring (English)
Rainer Grimm
Yalovastraße 20
72108 Rottenburg
Mail: schulung@ModernesCpp.de
Mentoring: www.ModernesCpp.org
Modernes C++ Mentoring,
Leave a Reply
Want to join the discussion?Feel free to contribute!