What can we learn from your latest paradigm shift in cataclysm?

Question

Very often we come across software experience that turns our assumptions upside down, and we view software development from a completely new perspective. The most obvious, which I suspect, for most of us who have been around, has been a transition to hard OOP. What other earthquakes did you experience, and how would you suggest we use your experience to question our assumptions?

EDIT: Maybe some suggestions about what you learned and how it changed your programming?

Answer 1

, . , , , . , 2- , . , , , , , , 10- .

, . , , : .

, , DLL, , GAC, , , , , . , . , , , , , , , .

, 6 , , . , , , , : , 5 , , , . , , , Java. , , : , , , .

, , , , , , GoF : .

6 , . , , MVC MVP, . , , , . Python, #, Perl , . , , . , , , . funsies ( OCaml Haskell Lisp), , .

:

, - ? ? , Java, 1000 , , , .. .. OCaml, 20: 1. Java- OCaml, . .

: , , . " , ", .

Answer 2

Test-Driven Development?

Answer 3

, , ...

, , .

Answer 4

, - , , .

Answer 5

-...

Answer 6

.

Answer 7

Answer 8

3GL 4GL;)

Answer 9

Enter the output. Being incredibly frustrated by the explicit cumbersome, bureaucratic specification of type specifications, discovering SML and seeing that static typing can be almost easy, became a real discovery (and made me even more frustrated with Java ...). Keep in mind, I did not use the type inference language, because (as a rule, either I do not choose the language, or I choose Python), but the vision of what can be done strongly influenced my attitude to what was done ...