Sprint 2 Retrospective

 In this sprint I focused my efforts on the front end, Specifically, checkinventoryfrontend. I wanted to experiment with nodemon at the start, and I had it installed on a separate branch on guestinfofrontend.

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem/checkinventoryfrontend/-/commits/Research-functionality-of-Nodemon

 I experimented with it, but ultimately one of my team members, Raquel, figured it out and gave us instructions on how to implement it. For the next sprint, I will add implementing nodemon to checkinventoryfrontend to my issues list. 

 

For the majority of the previous sprint I was grappling with updating checkinventoryfrontend to align with the current guestinfofrontend. At first I was struggling on how to deploy the front end on Gitpod, since the original shell scripts would not work in the development enviroment. It wasn't until the changes to guestinfofrontend to make it work in Gitpod that I started to make headway.

At first I thought that simply copying the files over to the bin folder would be a good enough start to fixing the issues with Gitpod. This was not the case however as this led to me having a bunch shell scripts that don't work, now with the added bonus of me not understanding what a single one of the new additions were meant to do or how to implement them. It was big mistake on my part since I thought I could easily parse out their purpose while I was implementing them.

 https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem/checkinventoryfrontend/-/commits/alejandromoca/update-checkinventoryfrontend-29

 I was wrong however, and terribly confused as to how to proceed for a bit. I actually ended up asking for the advice of my father on the matter, on account of the fact that he does front end development for his job. After looking at my work he told me to start all over from a new fresh branch to learn how the original checkinventoryfrontend worked. He also brought up using the commit history of guestinfofrontend to see how it was changed and in what ways. Taking his advice, I began changing bit by bit the file structure of checkinventoryfrontend. First, I implemented all the changes made in the guestinfofrontend commit "refactor!: refactor the frontend to modern standard".

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/commit/b9983049ac0ae7314292f03664d00058277e587a

These changes include creating the server and frontend folders in src, separating the shell scripts into frontend and backend variants, and creating a backend folder in the testing folder to contain the docker compose file for the backend. Doing this gave me a better understanding of the way guestinfofrontend and how it worked. This gave me the insight to continue on and start implementing the recent changes from the commit “fix: get working with gitpod url”. 

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/commit/e1a2029ed15c0e14bb148f97a9d7a814352224fa

After creating the frontend-dev-up shell script, I changed the gitpod and gitlab .yaml files to include npm install, among a slew of other minor changes to naming conventions and such, I finally got the shell scripts working and the front end running. Well, I say running, but the frontend is only giving an error currently which tells me that I fix something in either the App.vue or the package.json file. But that will have to wait for the next sprint, in which I will also be implementing nodemon. 

I think I really improved my understanding of the frontend, and my personal methodologies for implementing changes to code. In the future, I will take the time to truly understand each facet of the programs I work with, before committing to anything. I also think my team worked well together, and we completed our tasks quite efficiently. For the next sprint, maybe we could use some more open communication, but beyond that I think we do fine together.

.



Comments

Post a Comment

Popular posts from this blog

Open Source Software in Education

     In recent times I have started a job as a computer teacher for a private school, and as such I have had to become familiar with a variety of educational software. As an educator, it is important for there to be a plethora of accessible software to teach children digital literacy , as computers have become increasingly incorpor ated into more facets of modern society .  Open-source software is one avenue that allows young students a ccess to important tools to learn and create, without incurring a hefty price tag for their school. This is especially true for those learning how to code since it is not exactly a subject that comes naturally to everyone. While there are certainly many free IDEs out there for any aspiring adult programmer to use, I am more concerned with young children who may not be able to understand all the complex operations of standard IDEs.  The best answer I have found is the  educational coding software Scratch, created by MIT. Licensed under the "
Read more

Sprint-1 Retrospective

 I didn't manage to achieve a whole lot in my 1st sprint, I mostly looked at the guest frontend and poked around Thea's pantry. I'm going to make sure next sprint I actively work on the issues my team has in the backlog.  The only change I made to the pantry was a branch in guestinfofrontend named add-linters that I was planning on adding the Alexjs linter to. Unfortunately I never got around to actually adding it, and it seems that the other teams have already handled the adding of linters to the project. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/tree/add-linters?ref_type=heads Next sprint I plan on focusing on the inventory frontend and actually making and commiting changes. I do not want to let my team members do all the work.
Read more

Git and Game Development

     A subject that has always been near and dear to my heart is video games. Throughout my life I have always been deeply enamored with games and the process of their creation, from the intricacies of 3d modeling to the various game engines in use. Despite that, I would not say I am an expert in modern game development by any means. As my classes have progressed however, I have begun to understand more about the inner workings of software development and how teams are managed. This led me to investigate how game developers use these tools to manage projects and keep everything orderly. After doing some research, I found that many game engines are compatible with git and have no issue being stored on GitHub. Not only that but prominent game engines like Unreal Engine even have their source code up on GitHub , available for anyone to fork and clone . This was done to allow developers to modify the game engine itself, for whatever purposes they need. Godot is a free open-sourc
Read more