Understanding the harmfulness of goto statement referring to Edsger Dijkstra's Journal Paper of ACM-1968

I have received inspirations from the expert opinions/reponses of this thread to study the features of Structured Language, Teaching Methodology as well as to practice careful use (where it is really necessary) of goto statement.

Myself being a hardware oriented person engage less time in the study of programming language compare to what I engage for the designing/prototyping of hardware gadgets.