Three quick answers:

• flowcharts are useful to communicate and document the logic of a process. Not knowing how they work may well be a problem in some kinds of work.

• goto has value in many situations where some programmers (not all) will work. Not everything is done in high level languages. At a low level there are no loops, only conditional and unconditional gotos (branches).

• goto also has considerable importance in security/vulnerability. That's because hacking and vulnerability work (and therefore security) can involve understanding stack manipulation techniques and disassembly (machine code to assembler) which are completely based on jumps not loops. If you look at an infosec analysis of malware you'll see the need to comprehend code that doesn't have high level classes and objects.

Three quick answers:

• flowcharts are useful to communicate and document the logic of a process. Not knowing how they work may well be a problem in some kinds of work.

• goto has value in many situations where some programmers (not all) will work. Not everything is done in high level or modern languages. At a low level on most processors there are no loops, only conditional and unconditional gotos (branches). Older non structured languages also remain in use.

• goto also has considerable importance in security/vulnerability. That's because hacking and vulnerability work (and therefore security) can involve understanding stack manipulation techniques and disassembly (machine code to assembler) which are completely based on jumps not loops. If you look at an infosec analysis of malware you'll see the need to comprehend code that doesn't have high level classes and objects.