Blogging 101

In the episode  Rich Hickey on Clojure we get to know the Clojure's creator, Rich Hickey. As an introduction as well as a personal statement, I would like to highlight the basic idea in which Clojure was formed: Frustration.  The discussion starts with a brief explanation of the author's decision to create a Lisp-like language in 2009, same year where well-established technologies, such as Java, C++ or even Python, were becoming  mainstream tools throughout the industry. As Hickey mentions, although these programmable utensils were popular, all of them lacked the power of adding macros or different processes to run under compilation time. Furthermore, they all share a relatively chunky syntax, making them suitable for lazy in addition to unprepared programmers for unhanded data manipulation.  After 30 minutes, he roasted the entire tool-set I've been trying to completely master during the last 3 years... but he's right. As an entry-level programmer I have not met nor us

 In the previous entry, the podcast  Software Engineering Radio stated that Lisp ended the same way it started, with the community. Nonetheless, this program, in my personal opinion, marked this language as one whose repercussions never really skyrocketed in the intended way. In contrast to that affirmation, the article The roots of Lisp not only the principles behind the creation of Lisp were mentioned, but really presented to the reader the impact that this programmable approach could change and did impact computer science as a whole.  Throughout its numerous pages, the article by Graham, P provides a simple, yet technical enough to challenge the experienced programmer, explanation of the mathematical and syntactical principles behind Lisp. In a matter of minutes, the reader is introduced to Lisp's core functionality. The quick lesson started by reviewing important concepts such as  atoms and operators  as an introduction to the list power, and ended testing the ultimate capabili

The podcast Software Engineering Radio in their 84th episode narrated one of the most unknown moment, for at least my generation, of Artificial Intelligence, as well as of Computer Science history. At first, and as it should be in every technical discussion, Dick Gabriel introduces to the listeners not only the functionality behind the modus operandi of Lisp, but the context in which those solutions were being applied. During the first days of computational research  in the mid twentieth century, there wasn't a collection of paradigms as wider or as strict as it is it now, thus, the need for a language that treated and transformed data easily for a variety of domains was evident. It was at this time when John McCarthy, one of the first AI researchers in history, decided to write Lisp, a programmable solution based on the easy manipulation of data structures, such as Lists , that in the future would not only facilitate laboratories to apply mathematical notations easily in a comput

As you can tell from my previous entries, I really love when technology is approached from a social perspective. Not only these viewpoints expand our industry to solve wider problems, but also help us to see what's wrong and what has been wrong within the computer science field since its beginning.  Thompson, C, from the New York Times Magazine, exposes how, as most things within our global culture, women influenced and perfected the development of technology. Although discrimination is globally perceived as a race or ethnic centered problem, gender biases in societies prove otherwise. Since the creation of modern communities, and that is, when humankind decided to scientifically approach metaphysical phenomenon in addition to organize civilizations around a patriarchal god figure, women have been misplaced as well as disrespected in any social factor. As it is mentioned in the article  The Secret History of Women in Coding  (2019). 1  , modern industries had and have had preferenc