RainerGrimmSmall

Why my Blog in English?

For half a year I have a blog about modern C++: Modernes C++. Although 80% of the readers are used to English, the blog is written in German. So I decided to translate the articles successively into English. Because my English is not as good as my German I asked a few people for help. They will proofread the syntax of my articles. Now I have a few volunteers and I’m ready to start. I will still write my articles in the first place in English, but my hope is, that the German and English articles are in lockstep in half a year.
Because the roots of my blogs are in German, I will continue to call them Modernes C++. That is not by mistake.

Now my original words in English.

Key ideas

My blogs will focus on key ideas and cover that topic exhaustively. The topics will be challenging. My goal is to write one article about one issue. So in case of any doubt, I will split a large article into smaller ones. If it makes sense, I will add news.

A couple of very exciting topics that I want to address.

  • Multithreading, including the memory model
  • Embedded programming
  • Moving from C to C++
  • Functional programming
  • Generic programming (Templates)
  • Programming at compile time (metaprogramming)

Modernes C ++

Of course, one question remains open. What is modern C++? Modern C++ is for me C++, that uses C++11 and C++14 in a useful way. C++14 includes only minor extensions to the last large C++11 standard.

I am open to any criticism. May it be positive, negative, or will it just a typo and I’m already looking forward to the discussions. If you want to be a proofreader, please register yourself on the front page.

 RainerGrimmSmall

 

 

Rainer D 6 P2 500x500Modernes C++ Mentoring

  • "Fundamentals for C++ Professionals" (open)
  • "Design Patterns and Architectural Patterns with C++" (open)
  • "C++20: Get the Details" (open)
  • "Concurrency with Modern C++" (open)
  • "Generic Programming (Templates) with C++": October 2024
  • "Embedded Programming with Modern C++": October 2024
  • "Clean Code: Best Practices for Modern C++": March 2025
  • Do you want to stay informed: Subscribe.

     

     

     

     

     

    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)

    Do you want to stay informed about my mentoring programs? Subscribe Here

    Rainer Grimm
    Yalovastraße 20
    72108 Rottenburg

    Mobil: +49 176 5506 5086
    Mail: schulung@ModernesCpp.de
    Mentoring: www.ModernesCpp.org

    Modernes C++ Mentoring,

     

     

    0 replies

    Leave a Reply

    Want to join the discussion?
    Feel free to contribute!

    Leave a Reply

    Your email address will not be published. Required fields are marked *