Lenguajes de programación

Hello everyone, sadly, this is the last blog for a while. To anyone readying this, thank you for keeping up with this badly written blogs.  Today, we are going to talk about pair programming, this working framework that is widely used in the software industry. Some benefits include: Knowledge sharing, reflection, code review "on-the-go", focus, collective code ownership, team flow and most important, quality.   So everything is good, right?  Pair programming should be used always to improve software quality. Well, yes, but actually, no. It has also some challenges that most times are left apart, and personally, I didn't bother to think of them.  I'm only going to talk about the ones that I found most relevant, you can check the whole reading here . Exhaustion, pairing can turn your own times upside down, maybe you like to take breaks every hour or so, but your partner prefers to finish the work first and then take a rest. So we have a problem. You and your partner nee

Welcome to this blog again; throughout the past blogs we have discussed a lot of topics focused on Lisp, Clojure and computer science in general, but today is the turn of one of the greatest commodities in the contemporaneous area, garbage collection, this feature literally changed and simplified the programming process. So, in this blog I'm going to summaries and give my humble opinion on the topics discussed in Alexander Yakushev talk, A new age of JVM garbage collectors . So, for anyone not related to programming or familiarize with garbage collection, let me start with an example: You have two strings, "Hello" and "World",  these strings are saved in an address in memory, meaning they are taking a space in RAM; now you want to concatenate this strings, so you end up with a string containing "Hello World". Now, you don't need the previews strings, but they are still taking space in the finite and precious memory, and if this space is not free, i