Course Evaluation

Software Quality & Testing.

Course Evaluation.

This course is quite different to a lot of courses in which I have been in my entire degree., there is no doubt about that. Of course as a student I love the flexibility and the lack of stress that comes from a trust based grading system. It is true that I have done a lot of the stuff that the course asks me to do, but at some point, but I also wish I would just have taken advantage of what the course offers me and done the things I didn't really do. And at some point of the course I come to the conclusion that I am not going to do them at all. Personally, I think it is all about the deadlines. I am the kind of student for which deadlines were created for. I just think I have all the time in the world to do an assignment but the present. On the other hand, when I do an assignment I really dislike doing things just for the sake of getting a grade, it feels wrong to me, I just do that when the deadlines are over me and the grade of such assignment or project will have a great impact on my overall performance. In this course I was quite amused that I went through putting effort to things that are not really demanding upon grades.  I believe that setting some sort of way to motivate (or push) slackers to get things started. would be very good for the course.

I think the course content was good, I'm currently refactoring my own code at work to make it testable and it is pure pain. At this point of the semester I begin to understand how important so many of the good practices and concepts are in the real world development. I would suggest to make some sort of hands on classes in which we follow more of the "dev-ops" kind of tasks along with the instructor. They are super useful out there. 

I really enjoy blogging, it is like some kind of rubber-ducky technique , but after you get things done. You can express your frustration and showoff your achievements, tech related work comes with a lot of emotions and feels nice to be able to release them in my blog. I don't really mind spending time doing this.

I don't like reading. Maybe its personal but I think I learn much more from short descriptions on theory and then intermediately doing something to apply it. While some readings were quite interesting, there were a lot of readings in which my eyes were merely following the lines rather than paying attention before reaching the half of it.

Finally, I'd like to suggest to have some sessions or tasks in which we do unit testing to some code given by the instructor. I think it would be kind of fun and very valuable for the course.

DevOps part 3

For this task we were asked to work on the configurations of SSH for GitHub. The very first task of course was to ask Git to generate an SSH key. Everything ran pretty smoothly when following the instructions given by GitHub on how to do this. I was pretty happy to see myself doing this on my Ubuntu VM rather than having to deal with a bash for Windows or anything. The only point in which I had any problems was to copy the public key off the directory in which I created it. While I was aware of the place in which I left the SSH files, I didn't quite understand the command for creating them. While messing with it for 10 minutes or so adding and removing points and dashes I ended up opening a file open on gedit, but it turned out to be the private key. After another 10 minutes of doing the same thing I got the public key and managed to successfully added the key at the GitHub website.

Now I just had to test it quickly. I created a

file quickly directly on the GitHub website and pushed it. I just had to make a pull from my virtual machine, and yeah I had this problem in which I wasn't able to login. After some research I found out that it had nothing to do with the SSH configuration, it actually came from setting the two factor authentication. I asked for a token at the website and tried again with it and it worked. Good thing on my way doing so is that I learned that I can also use a SSH key specific to a repository for additional security. In the end the important thing was that the file was where it was supposed to be.

On Ana's blogpost...

Back at middle school I love writing those lame freestyle essays back at literature classes,.Writing is a really comfortable way to express yourself without having to deal with the anxiety of speaking in person, since you can just think over what you are going to write. I have never been a great speaker and there are a lot of things I wish I could share with people around me just as fluently as a text can do.

Reading Ana's article I think I can relate a lot to her. While I was no cyberpunk in my childhood, I didn't surf through a koalas fanpages nor was a an active visitor on experimental art websites, I can see the beauty that was in it and the nostalgia that might come from it. I believe that back them people did not visit the web for instant entertainment or interesting content, there was some "surfing" that had to be done and more interestingly there was some space for people to produce this interest upon each other, and as a consequence it created a certain kind of feeling of connection and community which was one of Ana's central points in her post. Even though I agree with her on this one, there are so many places in the web that people visit for this purpose. As mainstream as it is, I love visiting the smaller communities on Reddit that focus merely on reading and posting about their own bizarre interests such as bonsais, a specific music group, or  weird videogames such as Stellaris. And I have noticed how the purpose of some subreddits change as its popularity increases. For instance r/stellaris used to be full of discussions about builds, strategies and fanart and turned into memes, bug screenshots and shitposting. 

Well, while I would never write a technical blogpost because of the reasons expressed in this tweet, I believe it might be just a matter of time until I get the confidence to do so.In the meanwhile I must say I enjoy doing some technical blogposts for this course because I can just throw away some of the frustrations that I catch while doing the technical part.