Do programmers need block diagrams?

Question

C++ / C#

I study at the university, in the direction of information security. In computer science, we go through flowcharts. And such questions are generally needed by programmers.

Answer 1

Need documentation. And in this documentation, it is very often useful to present some information graphically: the relationship between the components and the general principle of operation, the general principle of the algorithm., etc.
It is desirable to present this in some standardized form in order to make the diagram understandable to everyone to eliminate reading errors. Therefore, they come to all these UML, GOST 19.701-90, etc.

Answer 2

If you ever write systems with uptime of millions of hours, you will understand that not only flowcharts are needed, but a large part of the university program. But before that, few survive.

Answer 3

Paradoxically, in my opinion, yes. Sooner or later, a diagram of a user case will pop up. Or a sequence of key business logic actions. You will not be drawn a diagram for each step. But these schemes are used in "broad" strokes. They are drawn on the boards, for example, at rallies.

Answer 4

needed

Answer 5

Flowcharts are needed in order to visually show the logic of the program / algorithm / function / process.
They are easier to work with than code.

Answer 6

such questions are generally needed by programmers.

Flowcharts in their pure form (not to be confused with UML, etc.) are a relic of FORTRAN times in 1958...
And they (in this form) are categorically unnecessary, harmful - they constrain thinking when comprehending the algorithm with a poor set of block pictures schemes.
Try to draw in a flowchart the simplest recursive algorithm... factorial calculation, say. And you won't ask that question again.