Why C++ A to Z?

  • Be pragmatic: Write useful tools that you and friends want to use
  • Adopt holistic thinking
  • Go deep, avoid surface-scratching
  • Every chapter features a tool or a service that is built from A-Z:
    • Design a tool or a service
    • Write code
    • Architecture
    • Tests (unit, integration, mock, fuzzing, hypothesis)
    • Logging
    • Documentation
    • Profiling
    • Debugging
    • Linting
    • Formatting
    • Code coverage
    • CI/CD
    • Package
    • Distribute
    • Experience on user side