Ethical Reflection on Ready Player One
In this blog I will be discussing some especif point that involves an ethical point of view to the book named Ready Player One.
I do see some virtues in the OASIS system, of course we can agreed that OASIS is just and exagereted analogy to our todays internet, social media, games, and many other hobbies in general, and this analogy tries to criticize the concept of having a space when you can forget about the real world and all of the issues that involve real life.
Said that I can compare OASIS to just a simple hobby like reading a book, which is an actual way to "leave this world" and explore a whole new world, and we can agreed that reading a book has some virtues, despite this we need to take mesaure and not leave behind completele the real world, such as a person that get himselft into OASIS or just a person that the only thing he does is read books, neither of this are healthy.
We can find this type of social criticism in many novels such as the ones mentioned by Ariel Ortiz in the task of this blog. I could agreed that there exists some similartities, because they all explotes and exagerates a concept that you can see in "real life" in order to try to explained and maked out how bad things could turn if we take it to the extreme, this is beacuse it is easy to explain something if you use a bigger concept in compare.
Do i think that we can build a software architecture that can accomplish one to the be similar to oasis, i think we could, speaking in therms of architecture, becuase we are talking about a conceptual and logical design of this world, but I don think that techonoly nowdays.
Software Architecture
domingo, 1 de abril de 2018
miércoles, 31 de enero de 2018
Is Design Dead
Is Design Dead
In this article I will be discussing about an article called "Is design dead" written by Martin Folwer.
I dont thinks software design is dead, said this what I was really try to say is that I hope software design is not dead, because on every quality software develop there is a prettey well planned and thought design and architecture behind.
As we can read in the article the author considers that there is to ways of writing code nowadays, this two are: the traditional way and the extreme programming way. I can be sure that the author is not trying to go for just one way and has no intention of convincing us to decide for either of both. I think he is just analysing and give advantages and disadvantages of these two way of software develop.
But of course every programmer has its own thought and maybe if you are getting good result of what you are doing and the way you are doing maybe you should change the path you chose to work with.
I particullary have the thought that each of these two are usable in different circunstances, but wait we all should be agreed on is that either of these two type of coding, they both have to be pre-planned and have to have a nice design that garantees the programmer he is doing it right, and that there will be the less complications in the future of the software life time.
So to finish this blog I would like to anwser the question the author intends with the name of the article, Is Design Dead?, and my answer to this, is that It is not dead, and whoever thinks the opposite way will never be developing a quality product or service.
In this article I will be discussing about an article called "Is design dead" written by Martin Folwer.
I dont thinks software design is dead, said this what I was really try to say is that I hope software design is not dead, because on every quality software develop there is a prettey well planned and thought design and architecture behind.
As we can read in the article the author considers that there is to ways of writing code nowadays, this two are: the traditional way and the extreme programming way. I can be sure that the author is not trying to go for just one way and has no intention of convincing us to decide for either of both. I think he is just analysing and give advantages and disadvantages of these two way of software develop.
But of course every programmer has its own thought and maybe if you are getting good result of what you are doing and the way you are doing maybe you should change the path you chose to work with.
I particullary have the thought that each of these two are usable in different circunstances, but wait we all should be agreed on is that either of these two type of coding, they both have to be pre-planned and have to have a nice design that garantees the programmer he is doing it right, and that there will be the less complications in the future of the software life time.
So to finish this blog I would like to anwser the question the author intends with the name of the article, Is Design Dead?, and my answer to this, is that It is not dead, and whoever thinks the opposite way will never be developing a quality product or service.
miércoles, 24 de enero de 2018
Who Needs an Architect?
Who Needs an Architect?
I personally consider that every programe or software needs to be design by a good architectura, because it does not matter if a module is well written or coded if that module does not communicate or interact properly whith the other elements of the whole system.
As the author mentioned, in the process of developing a system, there has to be a character which has the role of understanding the whole system in a wide point of view, this will help if some of the programmers have a doudt about the module they need to code, or maybe whith this person it will be easier to detect an error when system crashes.
I think software achitecture is pretty much underestimated, nowadays programmer just start coding modules as they are needing them, I mean, whithout any prevous design or architecture, and this must have to ocurre errors in the future, so it is very important in modern sofwtware development, to have an achitecture behind a software project.
In order to be a good architecure I consider that his/her should understant in a hundered percent of knownledge of the next elements: requieremnets, technology used, hardware used, user cases and system scope.
As mentioned in the article the architecture of computer system should be able to change the way that the system is being develop, because sometimes as programmers we dont usually make the right design of a code, and we get marry with the idea that our solutions was the best solution ever, but we need to consider that in this world there are many different way of solving the exact same problems, so the author recommends to be open minded and try to explore new design and solutions.
References
"Who Needs an Architect?" by Martin Folwer, href: https://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf
I personally consider that every programe or software needs to be design by a good architectura, because it does not matter if a module is well written or coded if that module does not communicate or interact properly whith the other elements of the whole system.
As the author mentioned, in the process of developing a system, there has to be a character which has the role of understanding the whole system in a wide point of view, this will help if some of the programmers have a doudt about the module they need to code, or maybe whith this person it will be easier to detect an error when system crashes.
I think software achitecture is pretty much underestimated, nowadays programmer just start coding modules as they are needing them, I mean, whithout any prevous design or architecture, and this must have to ocurre errors in the future, so it is very important in modern sofwtware development, to have an achitecture behind a software project.
In order to be a good architecure I consider that his/her should understant in a hundered percent of knownledge of the next elements: requieremnets, technology used, hardware used, user cases and system scope.
As mentioned in the article the architecture of computer system should be able to change the way that the system is being develop, because sometimes as programmers we dont usually make the right design of a code, and we get marry with the idea that our solutions was the best solution ever, but we need to consider that in this world there are many different way of solving the exact same problems, so the author recommends to be open minded and try to explore new design and solutions.
References
"Who Needs an Architect?" by Martin Folwer, href: https://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf
jueves, 18 de enero de 2018
The foundations of Software Architecture
The foundations of Software Architecture
The author of Software Architecture: Laying the Foundations of Software Design makes a good analogy about life and software achitecture, by explaning that in order accomplish an achivemnt first we hace to make a plan which we are going to follow to get to that goal, and is the same for software, in order to build a system please we have to make a model in order to make the system works correctly and this is when Software Architecture gets in.
Nowadays is very common and easy for people to make software, there are a lot of tools and practices that teach almost anyone how to code, but I think that this do not make them real programmers.
For me is crucial for all programmers to have a lot of experiences and information about software architecture, this is the line that defines a well done system.
Techonoly as we know is getting newer every day so it is important for us to be able of uodating the system that we made so they do not get out of day. And if a software is not develop in the best way, this task become very difficult to accomplish.
In order to make a good software architacture we have to be able of watching the system as a big module made by little blocks and how all they are realated and how the conecctions are made. This will help the Architect to detect errors, fix bugs and update the system.
Documentation is an important part for this proccess, as the architecture desing a system it is vital for him to write a consistent and updated documentation to each of the blocks of the system. This will help all developers and future architectures to keep coding and updating blocks of the system.
As future architectures it is our duty to mantain this standards and to keep making good practices in our developments.
The author of Software Architecture: Laying the Foundations of Software Design makes a good analogy about life and software achitecture, by explaning that in order accomplish an achivemnt first we hace to make a plan which we are going to follow to get to that goal, and is the same for software, in order to build a system please we have to make a model in order to make the system works correctly and this is when Software Architecture gets in.
Nowadays is very common and easy for people to make software, there are a lot of tools and practices that teach almost anyone how to code, but I think that this do not make them real programmers.
For me is crucial for all programmers to have a lot of experiences and information about software architecture, this is the line that defines a well done system.
Techonoly as we know is getting newer every day so it is important for us to be able of uodating the system that we made so they do not get out of day. And if a software is not develop in the best way, this task become very difficult to accomplish.
In order to make a good software architacture we have to be able of watching the system as a big module made by little blocks and how all they are realated and how the conecctions are made. This will help the Architect to detect errors, fix bugs and update the system.
Documentation is an important part for this proccess, as the architecture desing a system it is vital for him to write a consistent and updated documentation to each of the blocks of the system. This will help all developers and future architectures to keep coding and updating blocks of the system.
As future architectures it is our duty to mantain this standards and to keep making good practices in our developments.
viernes, 12 de enero de 2018
Moon Machines
Moon Machines
The documentary was about all the way through of how USA reached to the moon. For this mission it was requeried the most advanced technoly and mathematicians that existed in this decade, computer science was an important part of this mission of course.
The most interesting thing for me was that computers in that time were not enabled of changing the computer calculation once the spaceship was launched, so the maths that allowed to machine to work were all programmed before the lanching and it was not posible to change it when the spaceship was out in space.
It is very amazing how many pieces had to intervine in this proccess and how everithing could go wrong if only just one of the pieces, as small as it could be, did not make its job as it supose to do it.
I completely recognize de achivement of making all these work with the techonolgy of that decade.
Because the code had to be made by hand on perforated cards and the testing was really slow and sometimes calculations were not able to demostrate if they were right. And one coding error could lead the mission to a complete chaos or disaster.
I consider that engiennres nowadays have a much more easy testing process, if we could code in the same way they did it, because now an bug is detected very easily and it doesnt generates caotic consecuences, systems now would have much less errors that they usually have.
This mission made posible a big step on the computer history and thanks to all the research and innovation of these process many of our new computer programming technologies are how we know it today.
I consider that sometimes computer advanced not always are created for computer achivments, sometimes the goal to accomplish has nothing to do with the solutions, but it makes the engieniring to improve and innovate technology in order to make a solutions to the main goal.
The documentary was about all the way through of how USA reached to the moon. For this mission it was requeried the most advanced technoly and mathematicians that existed in this decade, computer science was an important part of this mission of course.
The most interesting thing for me was that computers in that time were not enabled of changing the computer calculation once the spaceship was launched, so the maths that allowed to machine to work were all programmed before the lanching and it was not posible to change it when the spaceship was out in space.
It is very amazing how many pieces had to intervine in this proccess and how everithing could go wrong if only just one of the pieces, as small as it could be, did not make its job as it supose to do it.
I completely recognize de achivement of making all these work with the techonolgy of that decade.
Because the code had to be made by hand on perforated cards and the testing was really slow and sometimes calculations were not able to demostrate if they were right. And one coding error could lead the mission to a complete chaos or disaster.
I consider that engiennres nowadays have a much more easy testing process, if we could code in the same way they did it, because now an bug is detected very easily and it doesnt generates caotic consecuences, systems now would have much less errors that they usually have.
This mission made posible a big step on the computer history and thanks to all the research and innovation of these process many of our new computer programming technologies are how we know it today.
I consider that sometimes computer advanced not always are created for computer achivments, sometimes the goal to accomplish has nothing to do with the solutions, but it makes the engieniring to improve and innovate technology in order to make a solutions to the main goal.
jueves, 11 de enero de 2018
About me
My name is Josep Romagosa I'm on the 8th Semester of the System Engineering career. For this course I hope to have a closer idea of compiler language, I do have a theorical idea of how this works, but as many things in engineering, you can not fully understand a topic until you get down to work and start practicing.
I have always considered the theater as a hobby, both to see it and to be part of it. I also enjoy cinematographic films. I would never earn my life doing this but I like to keep it as a hobby.
One of the movies I have recently enjoyed was Mother from director Daron Aronofsky, I loved how he could tell a story we all know by memory as a complete new story and without even tell which story he is trying to share.
My favorite kind of music is modern and acoustic version of classic rock and roll songs, one of my favorite is \"Sweet child of mine\" but the \"Captain Fantastic\" movie version, I consider that all song with a classic rock and roll base really have a whole armory between the lyrics and the music.
I also like to spend my holidays in countries I have never been, i like to just grab my backpack, find the cheapest flight and then go visit and travel as many places as I can, I make this every holiday school and work allowed me to do.
Im actually working in a digital marketing company, my main function there is to develop web pages, sometimes they are very simple such as landing pages or register form, but every semester im in charge of one or two big web app such ash ecommerces, CRM or ERP.
And that was a little bit of me lately.
Suscribirse a:
Entradas (Atom)
Ethical Reflection on Ready Player One
Ethical Reflection on Ready Player One In this blog I will be discussing some especif point that involves an ethical point of view to the ...
-
Ethical Reflection on Ready Player One In this blog I will be discussing some especif point that involves an ethical point of view to the ...
-
Who Needs an Architect? I personally consider that every programe or software needs to be design by a good architectura, because it does n...
-
Moon Machines The documentary was about all the way through of how USA reached to the moon. For this mission it was requeried the most adv...