Programmers nowadays have to...
… write 100%-covering unit tests;
… set up continuous integration, linters, hinters, style checkers, …;
… follow style guides for every language;
… meet impossible deadlines;
… meet impossible management/customer/end user expectations;
… read through terrible code others made;
… read through terrible documentation others made;
… make terrible documentation themselves;
… fight with the IDE;
… fight with the build tools;
… deal with unreproducible crash reports coming in from everywhere;
… debug code written at 2am (by themselves AND others);


  • 2
    Thankfully, someone came up with Doxygen to save our poor souls from bad documentation
    It's just that few use it.
  • 3
    Geniuses at the mercy of fools.
  • 0
    @AKCr you get my up vote for using sochen.amazing tool
  • 2
    @anekix All my root-folder CMakeLists.txt automatically search for doxygen. If it's found, they look for Dot from Graphviz. Then it configures a pre-made doxygen.in.conf into doxygen.conf in the build directory and adds a docs target to launch doxygen with the specified config. Also, if CMAKE_BUILD_TYPE equals DEVEL then they turn on the INTERNAL_DOCS option so one can view all the implementation docs too.
  • 0
    @DLMousey ☺
  • 1
    That sounds easy, can you do it in 2 hours?

Add Comment