CS@Worcester Alejandro Professional Blog

 I find the assertion that one is never done learning to be very true to life. One's skills as a software developer should be iterated upon just like the very programs we craft. The section on perpetual learning provided  many interesting examples of ways to tackle improving one's own knowledge base and skillset. I want to cover some of my favorite sections in this blog post and over the course of the next couple blog posts. Expand Your Bandwidth I constantly get the feeling that my knowledge in my career is always much shallower than it should be. The suggestions provided at the start with Google Reader and following software luminaries seemed interesting, but I was much more interested in looking at online courses and podcasts. I want to be able to constantly expand my knowledge base and explore new horizons.  This reminds me of when I was keeping up to date with a subreddit that was all about mesh networks and peer

  While looking for something that I could use for my 5th homework, I started looking into other software testing styles that we have not covered in class. There are tons of different styles that are implemented to introduce quality testing to software development. One such style I found this time is called regression testing, a testing style created to combat resurfacing bugs. Basically, regression testing is about implementing test cases every update, and maintaining them throughout future iterations. This is done to prevent old bugs from resurfacing and to check for any new bugs from being introduced in every update. Test cases should be created and implemented after every iteration to prevent bugs from piling up within your software. https://www.browserstack.com/guide/regression-testing  While this may sound a lot like retesting , the main difference is that regression testing looks for unknown bugs rather than known. H

 The recent explosion of AI has invaded almost every industry nowadays. It has become something of a buzzword, with many companies loudly proclaiming how they are making use of the emergent technology to benefit their customer bases. Chat gpt and other types of  AI have already started creating all sorts of problems within the academic setting, giving many students an easy out on writing essays. Not only that, but AI is also now being attributed as one of the main driving forces behind massive layoffs within the tech industry and beyond. All of that being said, how can AI be utilized to improve software testing. I know that immediately trying to think of ways for AI to replace even more jobs within the software industry can be a bit jarring after bringing up the problems it has already created, but I wanted to look into how the future may look if we were to utilize this technology to expedite the testing process. It is entirely

 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