Tag: tc3045

Postmortem No. 12

--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.

Final Blog

--Originally published at A project being made

The project is done, as well as the demo video and I can conclude now this reports. The team worked well, with some communication difficulties at a times. We learned at the same time to use new tools and put them together to carry out the idea of a client. A good decision we made was not to try to customize the entire user interface, because this could take too long and move away from the objective of the course.

In general, the way the course was developed was good. If I have to blame myself for something, I would say that I always arrive 15 or 20 minutes late for the class. This semester I experience many things, but put aside the habit of punctuality. Without a doubt it is something that I will work in the future.

I feel now, with better tools to speak with a client, be honest in calculating the production times of a job, know my strengths and my opportunities to improve. I am more aware of the need for an ecomerce and be able to discern between points that are worth being better detailed to those that do not. And above all the advantages of developing with the aim always to have a functional prototype that has passed the relevant tests.

Summary of the Whole Semester…

--Originally published at TC3045 – Israel's Blog

I want to start off by apologizing, I’m really sorry about not posting on the supposed dates, which were meant to be Fridays and Sundays, this semester has been awfully stressful and busy. Luckily, I took many notes in a sketch book that I always carry around on what we were going to do on the week and what we accomplished. So, I think the way on how I’m going to write this is in form of a list, describing each task to be accomplished and then what tasks needed more time or were more difficult.

So, let’s get started…

  • Expectations for week 3
    • Study the framework and get familiar with it.
    • Get familiar with the project and the code that is already there.
  • What we did for week 3
    • Due to exams coming and partial project in need to be finished we only got to know the framework but there is still much to learn.
  • Expectations for week 4
    • We kept studying the framework, but I think that for the next two weeks we are going to put this project in standby.
  • What we did for week 4
    • We didn’t do much, we just created a Trello to keep track of what we are doing
  • Expectations for week 5
    • We are in exams week and at least from my part, I stopped, just for this week my studies from the framework.
  • What we did for week 5
    • So everybody stopped learning the framework but we plan to get together to see what we’ve learned.
  • Expectations for week 6
    • This week I hope we finally get to sign the confidentiality contracts.
  • What we did for week 6
    • We did sign the confidentiality format, and we are going to get started next week.
  • Expectations for week 7