Skip to main content

Ethical Reflection on Ready Player One


Todays blog is the last one!!!!!! It has been quite a journey, but as everything, its time to end this. On today’s blog we are going to talk about a book, Ready Player One, written by Ernest Cline, this is the book that everyone in my class has been reading during the semester, and it was really, really good, I actually enjoyed it a lot. The plot is quite simple, it talks about a kid called Wade Watts, in a world were the actual real world is kind of a huge disaster for not saying other words, but in the book exist another world, a virtual one called the Oasis, were technically everyone plays it, because it was a whole new world, not only a videogame, in there people can have jobs, meet people, study in schools. The creator of the Oasis was James Halliday, and I say was because in the book he is dead, and after his dead he created 3 easter eggs that, when a player has the three, that player will own the oasis, and be the richest person in the world, and that is the goal of our dear Wade Watts.

At the beginning, I didn’t wanted to read the book because I have already watched the movie (yes, there is a movie), but when I started reading it I was trapped for those details that aren’t shown in the movie and for instance, the author showed the problems of the real world quite well in the book but not in the movie, the problems are kind of the problems in Black Mirror ( a Netflix series).

After I read the book I started to think that those problems, aren’t that far away as I thought, with the recent boom of technology advancements, we will need to improve the politics and laws, because is not only a matter of copyright and license terms anymore, is more of moral rights now, the interaction by the web is becoming stronger in the past years, so the possibility of creating a virtual world or anything will have to be attached to a restructure of the moral and ethical rights for anyone.

Comments

Post a Comment

Popular posts from this blog

Microservices

On today’s blog entry we are going to talk about the Microservices architecture. This architecture has an approach where when we are developing a single app, we develop it as lots of small services, each of them running on its own process and communicating with each other with something that can bind them together. Now I have already used microservices without knowing I was actually using them, perhaps this architecture is quite intuitive for best practices or something like that, but anyway the author of the article gives some characteristics about this which are the following: ·          Componentization via Services: The components of the microservice need to be gather into libraries that will be used later on by the microservice to communicate with remote parts of the whole program. ·          Organized around Business Capabilities: This characteristic refers that we need to create divisions, e...
Post a Comment
Read more

Understanding the SOLID principles

On today’s blog we are going to talk about the SOLID principles, which were discovered by Robert Martin, the famous Uncle Bob from the podcast of the previous entry. This principles are recommended to be used whenever someone wants to create an object oriented program. There are 5 principles where the acronym SOLID comes from which are the following S ingle Responsibility Principle (SRP) -> it says that any class should only have one responsibility. Yet, the author ends up saying that there might be some classes that have two responsibilities (the invoicing class that has some logging routines). In the end, I didn’t understand this principle well because I found the explanation confusing (as the author said, practice is much more difficult than theory).  O pen/Closed Principle (OPC) -> open extension but closed modification Although the author says that if you change a parent class method it might kill another part of the ...
Post a Comment
Read more