If you’ve ever rubbed your eyes trying to decrypt C++ compilation errors from a terminal, traced those back to the line in the ROOT script you were just typing in your plain text editor, then googled CERN ROOT TTree to fix the signature of that function you just used incorrectly, or even have faced with your bare eye the intimidating logs of valgrind output for memory leak detection, or manually deployed gdb, you should definitely keep reading.
This is a companion discussion topic for the original entry at https://root.cern/blog/code-horsepower-f1/