1, 2, 3... Another 100m Sprint

So… last week. What happened? Our 3rd sprint review. And, everything turned out well. As we get close
to wrapping up our project, we continue having less and less things left to do, other than better
implementations, bugs and general improvements. But the main structure and purpose of it all is mostly
done at this point.
In this sprint retrospective, we talked about our latest updates on the web client, with graphs shown to
the user for each of the parameters measured through time. Also, the data sent from the Raspberry Pi
to our sensors platform can now be done through HTTPS, so security is looking a little better now. We
still have to make some adjustments, given that for now we are signing this SSL certificate ourselves.
And that’s mostly it. The waters are mostly calm now, and we’ll have to continue dialoguing about what
we still need to do from here on and and what’s really just a “nice to have”.
So yeah. Watch out for more posts. There aren’t that many left, I promise to stop the bad jokes soon
(maybe) (maybe not) (ok bye).

Comentarios

Publicar un comentario

Entradas populares de este blog

Time Flies

Imagen
Hey there, again. So, 4 weeks have gone by already… time does fly. Also, now partials are here, but let’s not talk about that now. Or just as Michael Altshuler says, “ The bad news is time flies. The good news is you’re the pilot. ” image obtained from https://akatandamouse.files.wordpress.com/2015/01/time-flies.jpg?w=354&h=266 And with that being said… looking back at week 4, it was a pretty calm week. It turns out I did some research into what has to be done so that the signals sent from the Raspberry reach out Broker with the HTTPS protocol, and I’m pretty sure I’ve found a way. But, this HTTPS protocol must also be enabled on our server, on a separate port. So, I’m going to have to hold on to that idea until actual support for it is added on our server. Other than that, I did some more research into incorporating more sensors to the platform, and it seems that we can use a “humiture” sensor, which measures both humidity and temperature. 2 sensors in on
Leer más

Year 2038 Problem

Imagen
Previous week was a bit slow, we lost a bit of the energy that had us so pumped up at the beginning of the semester, but we still want to see this project through. We still believe in it. Personally, I did some research into the “Epoch” time, an universal reference to know the current time… the amount of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), without counting leap seconds. And, interesting fact, many Unix systems store epoch dates as a signed 32-bit integer, which might cause problems on January 19, 2038 (known as the Year 2038 problem or Y2038). Beware, world. You can read more into this here https://www.epochconverter.com/ Anyways, we decided to use this system as a timestamp for every temperature reading in our project, so I found out how to obtain this value in Python. It’s actually pretty easy. We also decided to move forward with our initial idea of having the plant “tweet by itself” updates on its current condition. Next post coming
Leer más

Commitments > Promises

Imagen
Aaand what’s in our agenda for this week? Well, once again we all have to talk to one another about what’s left to merge from our individual tasks. This week we’ll have our third Sprint Review, and we have a few new things to showcase. We’ll see how it all goes. Until then, I guess that’s all. Bye. image obtained from https://www.codeproject.com/Articles/674450/Agile-software-development-steps-to-work-with-Requ
Leer más