How to start learning flowcharts of algorithms from scratch?

Question

Algorithms

There was a problem in learning algorithms.
What is the point: ten years ago I studied coding, things were going well, I understood the algorithms, I could write everything down.
Then he went to study in a completely different steppe, and a couple of years ago he returned to the IT field already as a tester, but not a virgin. Everything would be fine, but the ability to code is now more and more necessary every day (in autotests, etc.), and I forgot the process itself. Deciding to remember the forgotten, I went to look for books. Decided to start with Knut, and broke down already in the search for a bubble.
As it turns out: I can write the code that draws up this search, I can describe it in words, but I just can’t put it into a flowchart. I just sit down at a piece of paper, start writing, and fall into a stupor.
What can be read specifically from flowcharts in order to better understand this issue (except for Knuth, of course)?

Answer 1

Answer 2

Why do you need flow charts? At the level of algorithms, this form of notation is not used; it is much worse readable than pseudocode.
Flowcharts are useful at a higher level. And they are called Activity Diagram.

Answer 3

Why even start repeating coding according to Knuth, I, of course, understand outstanding books, but for repeating the PL and for auto tests it is a little off topic, maybe you should choose which is easier in relation to your PL? There you look and block diagrams are not needed.
And since you are already doing auto tests, maybe you should just dig deeper into auto tests, rather than go into the wilds of algorithms? At one time, this resource
helped me in auto tests , yes, it’s on rails, but it gives the big picture

Answer 4

To see and be horrified (or admire)
Visual algorithmic programming language DRAKON
Description of the visual syntax of the DRAKON language