Mark Zuckerberg

This documentary gives us a global idea of what seems to be the real origin of Facebook and its founder personality.
One of the main purposes of this I think is to take into account that the sole fact of knowing how to do something (the technical skills) are not enough if you really want to leave a trace in this world.
In the case of Mark, besides knowing how to do such massive site, he knew how to make it have a very strong impact. Maybe he stole the idea, maybe not. But he knew how to drive the business to make it billions worth.

Something that I loved about the movie and they mention it in the video, is the passion Mark has. I think that one of the things that made Mark be the man he is, is his passion he has for programming. As said in the video, he spent days and night building the site; but not in a normal way, he turned it into almost an obsession. And you realise that things are well done when someone puts an effort of that magnitude in something. That's when you know when something has a great quality, when it is done with love.

I know it is almost a pattern, that almost all the successful people that make a difference in computing, started from children, learning by themselves. I don't think that it may be a gift, I think it is more that they found what they loved at a very small age. And that pattern repeats in all fields of science and arts.

Software Architecture - Code Craft

Flying Spaghetti Monster

Some people may think that a good or a bad architecture doesn't affect the behavior of the program the user sees, but that is wrong. Although a good architecture helps the developers, it also reflects the quality of the final program, a good design. And as Steve Jobs said "Some people think design means how it looks. But of course, if you dig deeper, it's really how it works". and this can perfectly fit in this reading.

The author relates various types of software architecture with types of pasta. I like the relation, because code is pretty much like pasta, it can be a mess if you don't care about anything, or it can be something with an interesting shape, but at the end is pasta.

"A good architecture leaves space for maneuverability, extension, and modification". That is one key concept and in my short coding experience I can say that phrase holds the truth. Sometimes I've written code in the rush, just worrying about delivering it without paying attention to possible changes in the future; and that mistake has cost me a lot of time.
For example:
I recently programmed an Android app in which I spent a lot of time replicating code over and over, getting errors where they shouldn't be and driving me very mad. Then, after struggling I realised that what I needed was to implement a Java interface for my problem. Finally, when I did that, everything was more clear and without errors, because that was the correct approach. And what is best, the next time I face a problem like that, I know how to quickly solve it, because now I know the perfect tool for it.
But obviously not everything solves with interfaces, we need to find the correct tool for our problem. That's why these readings are so important, because show you various ways to find the correct tool for your Flying Spaghetti Monster.

Welcome entry

Hi. I'm Moisés Olmedo Piña.

What I expect to learn in this course are the various software designs that currently exist. I hope I can learn ruby as complete as professor Ariel Ortiz teaches. And apply all the knowledges in my web developments.

My hobbies are very wide. I like movies and tv series a lot, I like the night life of the city, I usually go to the gym and I'm currently an employee as a developer creating mobile applications in iOS and Android.

I am currently watching a TV series called Nip/Tuck. The last movie I enjoyed was Pacific Rim and The Great Gatsby, I liked it a lot. I'm a big fan of Matrix, a lot of music, and Steve Jobs