--Originally published at TC3045 – Software Quality – Building Software

This is not only the conclusion to this week but also to the semester. During this three months I learnt the following:

• Motivation is the key to success, but too much motivation is risky: it might end up in a total lack of interest.
• Estimating is hard.
• Individual works are faster, but when the person working on this task is not available, things can turn bad. Therefore, people redundancy on tasks is required.
• Unit tests are as important as integration tests.
• Versioning software is extremely helpful.
• Demos may go wrong: always have a local (and even mock) version.
• Saying “no” is ok.

--Originally published at TC3045 – Software Quality – Building Software

On this week I fixed the HTTPS bug: apparently, there was a problem with our deployment script. This was my main work during the whole week. By the looks of things, we’ll only do one more week of work.

--Originally published at TC3045 – Software Quality – Building Software

A couple of days before our demo, we had a small problem with the HTTPS in the broker: something really weird happened with the certificates. Since we had no time to fix it before the demo, we had to do a rollback on the server. Fortunately, the Docker image was versioned correctly and the change required was only a modification in the Kubernetes YAML file. Other than this, our demo was good.

--Originally published at TC3045 – Software Quality – Building Software

During this week our main objective was to prepare for our demo. Also, I worked with Lucía with our deployment script.

--Originally published at TC3045 – Software Quality – Building Software

In this week we had our delivery: we had a couple of bugs on the demo (which I tested and worked, IDK what happened). But we managed to success in the demo.

As for our second session, I didn’t really work on the project. But I’ll keep on on vacations.

--Originally published at TC3045 – Software Quality – Building Software

In this week I worked mainly on fixing our previous mistakes. I admit I had to work on a non-class day. But, taking into account that one of our classes was entirely wasted, it sounds fair.

I added more functionality to the HTTP broker and I helped Lucía with the Kubernetes YAML file generating script. As for our test platform, I deployed both the new broker and client (in this one I didn’t add any functionality).

We were supposed to present on Friday, but due to unforseen circumstances we weren’t able. But we’re ready for Tuesday.

--Originally published at TC3045 – Software Quality – Building Software

In the first part of the week we focused on delivering our technical debt. We ended up with a good deployment. Unfortunately, this helped us discover a couple of bugs in the client code. So, now its important to do fix this.

As for the second class, to be honest we didn’t do anything. It was more a relaxing session rather than productive. But, to repair this, I intend to make some advance to the project maybe next Saturday.

The next week we’ll have Taller Vertical, which is an entire week of hard work focused on a fast deliverable. So, I won’t focus on this project at all (from Monday to Friday).

--Originally published at TC3045 – Software Quality – Building Software

In the previous week I worked mainly on fixing our problems, Such problems include:

• Having fully isolated tasks (now at least two people must work in each of these).
• Only me having access to things (now Alejandro has access to Docker Hub).

As for technical work, I started working with Lucía in a Python script for building Kubernetes Secret files (for distributing sensitive data in the cluster, which should vary on each build).

--Originally published at TC3045 – Software Quality – Building Software

During this week we finished our second deliverable. We had some big issues, mainly because Alejandro wasn’t present for the whole week. And, although he finished his part and it was working by itself, the integration was very hard and we didn’t manage to make it. This made us realize that work cannot be isolated any longer: at least two people must work on each issue.

Regardless of the situation, I worked mainly on Kubernetes things. I deployed both a MySQL database and the HTTP broker, both in Google Cloud Platform in a Kubernetes cluster. I had some trouble with a routing ingress and I deployed a single service with a particular IP. This is not the best way to do it, but it’s a temporal fix that works.

--Originally published at TC3045 – Software Quality – Building Software

During this week I worked on the HTTP broker. We finished a basic version, with a microservices approach. It now is ready to be deployed. The tweaks we added (Lucía and me) include logging to a file, using flags for configuring variables without modifying the code and it even includes a test mode, which runs with dummy data.