Paradigms are powerful because they create the glasses or lenses through which we see the world.<\/p>\nStephen R. Covey<\/a><\/cite><\/blockquote>\n\n\n\n There are three main programming paradigms used today and in JavaScript they have always existed since its first version.<\/p>\n\n\n\n Now, if we stick to the phrase of Stephen R. Covey,<\/a> that paradigms create the lenses through which we see the world. Let's imagine that the three previous paradigms, each, are a pair of glasses that we put on when programming and that we can change those glasses according to our visual needs (for programming or problem solving).<\/p>\n\n\n\n In 1954 the FORTRAN programming language appeared, then in 1958 ALGOL and in 1959 COBOL. Time after Edsger Wybe Dijkstra<\/strong> in 1968<\/strong> discover the structured programming paradigm, we say \u201cdiscover\u201d because they didn't actually invent it. Although this programming paradigm was formalized some time after the appearance of these programming languages, it was possible to do structured programming in them.<\/p>\n\n\n\n Dijkstra<\/strong> He recognized that programming was difficult, and programmers don't do it very well, which I totally agree with. A program of any complexity has many details for the human brain. In fact, the Neuroscience tells us that the focused mind <\/a>It can only work with four pieces of data at a time, at most. For this reason, if one small detail is neglected, we create programs that seem to work well, but fail in ways you never imagine.<\/p>\n\n\n\n Dijkstra's solution was to use tests<\/strong>, only these tests used a lot of mathematics, which was quite difficult to implement. During his research he found that certain uses of GOTO made it difficult to decompose a large program into smaller pieces, it could not be applied \u201cdivide and conquer\u201d, necessary to create reasonable evidence.<\/a><\/p>\n\n\n\n B\u00f6hm and Jacopini<\/strong> They proved two years earlier that all programs can be built by just three structures: sequence, selection and iteration<\/strong>. Dijkstra already knew these three structures and discovered that these are the ones necessary to make any part of the program tested<\/strong>. This is where the structured programming paradigm is formalized.<\/strong><\/p>\n\n\n\n Edsger tells us that it is bad practice to use Nowadays most programming languages use structured programming, JavaScript uses this type of programming. The simplest example is if conditions.<\/p>\n\n\n\n\n
Structured programming paradigm<\/h2>\n\n\n\n
Origin<\/h3>\n\n\n\n
Evidence<\/h4>\n\n\n\n
Sequence, selection and iteration<\/h3>\n\n\n\n
![\"Patrones](\"https:\/\/pensemosweb.com\/wp-content\/uploads\/2020\/11\/patron-programacio\u0301n-estructurada.png\")
GOTO<\/code> and suggests better using the following control structures:<\/p>\n\n\n\n\n
Decomposition of small units easy to test<\/h4>\n\n\n\n