Blogging 101

Before 2014, I doubt a normal person -understand this as a non-geek profile- really knew the impact of Alan Turing's work. I was 13 years old when the movie The imitation game came out and I can say that it was one the few directions that really marked a b efore and an after  in me when I first saw it. Since then, I have easily watched at least 20 times and not because of its wonderful plot but for the marvelous presentation of such a complex topic such as computation history.  Telecommunications, medicines and as many other inventions we enjoy today, its fundamentals and need took place due to the desperation and chaos that derived from World War II. Computers are not different. Like the movie presents, Nazi Germany stole a Polish cipher-based communication machine called Enigma and used it during the Blitzkrieg -the very first years of the war- to streamline the German war effort in addition to coordinate operations in various fronts without being caught in the process. This rea

Throughout the development of this course, and as I have expressed in previous entries, I've become aware that, in fact, Functional Programming is more convenient than OOP, and this entry will continue to expand this mentality. The video  Why Isn’t Functional Programming the Norm? introduced us to a very interesting context that was previously touched in the very first entry: humanity within programming. Feldman, R. hinted various times that the OOP paradigm is strong nowadays not because it provided a better understanding of what the programmer was doing, like it happened when C was created back in the day. But in fact, its popularity grew due to the fragile, but complex concept of power.  In the video it was mentioned what I would like to refer as: the principles behind OOP power, those being: platform exclusivity, killer apps and language familiarity. Yes, I must admit that the video explicitly did not mentioned those attributes but those that were mentioned can be perfectly tra

 I don't know if this is my last entry, at least with Clojure related topics. but, I think that if that's the case, this discussion will be as, if not more interesting than the last two publications. Everyone who has programmed in Clojure knows that this language uses the JVM. This means that it takes all the benefits of using the Virtualization of Java to compile and run code. But... have you ever questioned how does this virtualization, specially, the java garbage collector works? Yeah, me neither. Nonetheless, if you answered no, don't worry that we are not the only ones. In fact, this curiosity inspired Alexader Yakuushev to not only questioned himself how does the tool that almost every programmer uses works, but to explain to the rest of us.  In his video, A new age of JVM Garbage Collectors introduces us to a whole new variety of concepts and abstractions that, if you're not familiarized with data structures, you may find them hard to understand. In particular, A