I'm happy to present the five winners in this post including their answers.
I was happy that Stephan chooses the best five answers because we got more than 30 answers. He made his decision mainly based on the criteria: participants with no or little experience with Clean C++. To remind you, here are the three questions we asked:
- Are you already familiar with the principles and practices of Clean Code Development, and do you apply them to your C++ code?
- Do you use unit tests and try to achieve the highest possible test coverage?
- Are you familiar with the software design method Test-Driven Development (TDD), and do you apply it in your daily work?
When I present the three answers of the five winners, I only write their first names. Apress already contact them.
- Because I’m a beginner at C++ programming, I am not familiar with principles of Clean Code Development. For that reason, I couldn’t apply them to my learning-purpose-projects.
- Since I do not have any professional background in software development, I do not have any experience using unit tests.
- However, I am not familiar with the design method you mentioned.
- I am not familiar with clean code but I am interested.
- I do not use unit tests but am trying to learn Google unit test tool.
- I am familiar with TDD but I do not apply in my daily work. Shame.
- I have heard of it and have a couple books on my to-read list about them. Seems an up-to-date book would be even better place to start.
- I use some unit tests, but definitely need to use more for full coverage.
- Yes, I'm familiar, but unfortunately do not apply it.
- Yes I have read Uncle Bob's Clean Code book. I do apply the principles. I observe significant improvement in my productivity as I understand and implement more of them.
- Yes, I follow the TDD method. I write a test and implement no more than it is enough to make that test pass. This leads to naturally high amounts of test coverage.
- Yes and yes, I believe that TDD is the best and most effective method of software development. It certainly accelerates the development speed and makes it much easier to maintain a code base.
- I try to write code as understandable as possible, use templates and concepts as much as I can. And test them I try to apply the best practice as I learn from experts like you, cpp.con, and many other awesome writers.
- I write and test my code but Unit test is in my list I signed up for a class on Udemy to learn the basic Also look other code to learn from.
- I have not learned TDD yet.
Thanks a lot to my Patreon Supporters: Matt Braun, Roman Postanciuc, Tobias Zindl, Marko, G Prvulovic, Reinhold Dröge, Abernitzke, Frank Grimm, Sakib, Broeserl, António Pina, Sergey Agafyin, Андрей Бурмистров, Jake, GS, Lawton Shoemake, Animus24, Jozo Leko, John Breland, Louis St-Amour, Venkat Nandam, Jose Francisco, Douglas Tinkham, Kuchlong Kuchlong, Robert Blanch, Truels Wissneth, Kris Kafka, Mario Luoni, Neil Wang, Friedrich Huber, lennonli, Pramod Tikare Muralidhara, Peter Ware, Daniel Hufschläger, Alessandro Pezzato, Evangelos Denaxas, 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, Matthieu Bolt, Stephen Kelley, Kyle Dean, Tusar Palauri, Dmitry Farberov, Ralf Holly, Juan Dent, George Liao, Daniel Ceperley, Jon T Hess, and Stephen Totten.
Thanks in particular to Jon Hess, Lakshman, Christian Wittenhorst, Sherhy Pyton, Dendi Suhubdy, Sudhakar Belagurusamy, Richard Sargeant, Rusty Fleming, Ralf Abramowitsch, John Nebel, and Mipko.
My special thanks to Embarcadero
My special thanks to PVS-Studio
Mentoring Program in English
I'm happy to give online seminars or face-to-face seminars worldwide. Please call me if you have any questions.
Standard Seminars (English/German)
Here is a compilation of my standard seminars. These seminars are only meant to give you a first orientation.