From: jj4public@outlook.com   
      
   On 7 Feb 2023 19:53:17 GMT, Stefan Ram wrote:   
   >   In a current discussion about a topic from the field of physics,   
   >   there are some people who do not realize that I am right.   
   >   
   >   In computer programming, often, when someone says something   
   >   that is wrong, I can demonstrate his error relatively easily   
   >   to such an extend, that he must realize that he is wrong.   
   >   Of course, this applies especially to trivial matters, and   
   >   not to all programming topics.   
   >   
   >   For example, when someone says, "In C, one cannot print   
   >   an asterisk, as this is a so-called 'meta character' that   
   >   has a special meaning for the language.", I can go ahead and   
   >   write a C program that prints an asterisk. Even if my opponent   
   >   does not even understand the program, he can start it and   
   >   see that it prints an asterisk.   
   >   
   >   Of, course, he /could/ say: "Yes, as I said. This program   
   >   is not written in C, because it prints an asterisk! This must   
   >   be C++.". But often he will see his error. People who do not   
   >   like to admit their errors have a hard time in programming,   
   >   because the behavior of their program is only controlled by   
   >   the technical guidelines of the language specification and   
   >   not by their wishful thinking or overconfidence.   
      
   If you go to any programming sub in Reddit, or any programming channel in   
   Discord, you'll realize that some people aren't capable of realizing that   
   they are wrong.   
      
   >   When things get more complicated, it becomes more difficult,   
   >   to get your opponent to admit that you are right. For example,   
   >   you cannot write a program that shows the complexity of an   
   >   algorithm in a convincing manner.   
      
   It may actually be the opposite. The program which is needed to convince the   
   opponent, would need to be done at a lower level - which increases the   
   complexity to understand the code.   
      
   Short question or small problem usually need a long answer or complex   
   solution. While long question or complex problem, usually need a short   
   answer or simple solution.   
      
   >   Of course, it is also possible that I am the one who is wrong.   
      
   Nah... you're not wrong. Some people don't (yet) understand either the lower   
   level part of programming, or the concept of programming itself.   
      
   Many jump directly into learning how to code, and skip learning the concept   
   of programming. Including failing to understand the capabilities of a   
   computer, an OS, a compiler/interpreter, and a software library. Not aware   
   that they are actually crucial to programming. Because no matter how hard   
   they tried, if the underlying softwares and hardwares aren't capable of   
   doing it, it'll never happen. Care to download a RAM?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)