Introduction

Hello everyone, well, going fast: my full name is Natanael Pérez Bucio and I'm currently studying the Computer Science major at Monterrey Institute of Technology, the Mexico's State Campus. I've been studying at this campus for 6 and a half years. Even when I've decided to study an TI focused major I had several options based in my interests, having as options a Film Major, a Mathematics Major and even a Philosophy Major. Finally I decided to study Computer Science because I felt more secure in my programming and understanding skills, also is one of the topics that few people understand and it may be a really important advantage for my professional life; it's really polymorphic and give enough options for professional growth on any matter.

About my hobbies and my topics of interest I can tell you that I love movies, specially the cult, the independent, the social criticism, the mockumentary and the superhero movies; but I enjoy looking at any movie. Recently I've seen many interesting movies, like "Goodfellas", "Pefectos Deconocidos", "Los Cronocrímenes" and "The Usual Suspects". I also love music, to sing is one of my secret passions, even when I don't consider myself as a good singer, and the music genre that I listen to the most is ska and trova, this two are strongly represented into the latin community and simply makes me feel inspired.

For this course I expect to get to practice more than the last course of Programming Languages that I programmed a lot but not focused on something that practical, but more into theoretical knowledge.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Understanding the SOLID principles

The first interesting topic I find here is focused for the object-oriented programming, but even with that this in mind, we find it useful for other purposes. This might appear a little out of place, but the distinction here is necessary, because I've felt that some concepts are strongly related to the OOP. Anyways, we have here five solid principles for design and getting the code more intuitive and to avoid the most dependencies that we can. The first principle is the "Single responsibility" one and the name is very explicit, it's for getting each class doing one and just one thing, this I see that applies for the methods too, getting in the example some problems for a method that does more than one task. I would ad to this that the name would explicitly say what does each method do, because this is also a problem clearly presented. The second principle is called "Open/Closed principle" and refers to get the classes/functions to be open to the extensio...
Leer más

Is Design Dead?

For this article there is several topics that appeared very interesting to me. For the initial themes treated, one was the difference between the traditional structured design, and the evolutionary design, and it's a matter that I've even seen as a difficult topic because of the different perspectives presented even by my own teachers, some of them teaching me that the planned design is extremely important and even forcing this practices into our projects, but in the other perspective, some professors taught me to be evolutionary, and to make incremental design based on prototypes making really confusing the decision for the design every project I've made. Also, one of the things that I've found curious into the article is the association that the author makes between the refactoring and the YAGNI's simplicity to the evolutionary design. It's not that usual to understand the "best practices" of programming as supporting any bigger concept than the co...
Leer más

Software Craftsmanship with Bob Martin

I liked this podcast, it has some strong opinions from Bob Martin that even considering that the podcast is from 10 years ago, are really applicable for the industry of the software. I think that programming is very satisfying just for some of the reasons that are described as the craftsmanship, like the art that involves maintaining the readability and the refactoring always clear into the code, and not getting totally disconnected from the design even when into the Bob's preferences around the agile methodologies. One of the points that got my attention is the way he expresses himself about the design and architecture documents (and other documents as well) letting us know that the agile methodologies can produce outputs of any kind, that this mentality as programmers of not producing any kind of documents while working agile it's just wrong, and we shall just be used to get great practices into our own process of making software. Other topic that it's touch is this i...
Leer más