Now that was funny. I have bled in that wilderness - debugged assembly language with a digital oscilloscope because there plain was no user interface. I’ve worked inside OSes, device drivers, and written my own real-time executive. I’ve lived through projects where getting output to a terminal was considered a huge leap forward in debugging capability. Your IDE is a luxurious syntax highlighting editor and make.
Similar to the Necronomicon, a C++ source code file is a wicked, obscure document that’s filled with cryptic incantations and forbidden knowledge. When it’s 3 A.M., and you’ve been debugging for 12 hours, and you encounter a virtual static friend protected volatile templated function pointer, you want to go into hibernation and awake as a werewolf and then find the people who wrote the C++ standard and bring ruin to the things that they love. The C++ STL, with its dyslexia-inducing syntax blizzard of colons and angle brackets, guarantees that if you try to declare any reasonable data structure, your first seven attempts will result in compiler errors of Wagnerian fierceness:
Syntax error: unmatched thing in thing from std::nonstd::__ map<_Cyrillic, _$$$dollars>const basic_string< epic_ mystery,mongoose_traits < char<, __default_alloc_<casual_ Fridays = maybe>>One time I tried to create a list<map<int>>, and my syntax errors caused the dead to walk among the living.
Life is simple as a cook. You know how you did that day. When you walk away from the kitchen, you are done. And you never, ever have to disassemble and upgrade a meal cooked by someone else working for a company that no longer exists on equipment that can only be found in outer Mongolia. At a flea market.
/johnny