Week 8

 Part 1: Review Other Teams' final video projects:

  • Sports Technology ((57) Sports Technology Long Video - YouTube)
    • Then topic is covered well, with the group's introduction to various areas where sports technology is being applied. The presentation is clear with visual aids to go along with each point. Research has been done as the links advancements in technology to the benefits that have been seen in sports as a result. The video production is clear and easy to follow with videos keeping me engaged while listening. The team worked together to present their topic, and the level of detail applied to each video is relevant to their intended audiences. 
  • Quantum Computing (Quantum Computing Presentation - OtterAI - YouTube)
    • OtterAI covers Quantum Computing well. The presentation is clear and goes over history to give some background, then follows it up with more technical information that is once again easy to follow. The team's research was excellent, explaining key contributors to Quantum Computing. technical details, and processes. The video production was simple, including visual aids that wouldn't distract from what the speaker was saying. I was engaged by the topic being discussed, and it was evident that the team worked together to explain their topic. Each of their videos kept their level of detail appropriate to their audience.
  • AI-Driven NPCs in game worlds (Comp CSUMB VIdeo - YouTube)
    • This topic was well covered. The team gave a history of NPCs in video games and explained where they are at now. Their research was good, including how NPCs are used to make experiences unique in different games. The video production was also good, using example videos throughout the presentation to keep the viewer engaged along with helping the viewer follow along. The team definitely worked together to produce their video, with different teammates explaining different parts of AI NPCs in emergence in game worlds. Their videos were appropriate however their shorter video could have included less detail in order to keep a younger audience engaged.

Part 2:


    I've learned a lot from CST 300. From ethics arguments, to improving my writing, to researching more about various technologies, and learning to be more effective when working with a team. With the OLI Post test, I found that my answers had shifted a bit from the pretest, however they mostly stayed the same. Through previous work with a team, I had an understanding of ways to make teamwork effective, however the OLI modules were beneficial in providing additional insight. Our team collaborated well. We communicated with each other, set meeting times, and completed our work on time. Next time I could try to be more proactive about upcoming assignments and meeting times.

Comments

Post a Comment

Popular posts from this blog

Software Engineering Week 4

    The most interesting thing I have learned about in my reading of "Software Engineering at Google" are how each of the various processes are executed. While I am familiar with most of the processes I've read about so far, including code reviews, unit testing and system testing, the manners in which these are executed at Google are different from how they have been executed in my professional experience. For code reviews in particular, Google engineers ensure they invite various other software engineers to fill the roles of correctness and comprehension checking, language readability checking, and code owner. However, in my experiences this is not explicitly required. While a single engineer on the team often fills a couple of these roles, there wasn't an engineer specifically dedicated to carry out each of these tasks. Another interesting thing I learned was a recommendation about the use of the "sleep()" function in testing. While sometimes waiting is re...
Read more

Capstone Project Week 10

   What did you accomplish this week? This week I looked into integrating the stac-browser container within the docker compose YAML file provided in the stac-fastapi-pgstac project. In addition I cleaned up some unnecessary data included in STAC items written by our parser as well as read further documentation from the National Hurricane Center on how I can do additional parsing on dropsonde remark messages. I also published a build and tested docker image including our team's parsing tools to docker hub to allow it to be pulled from our AWS instance. What is your plan for next week? Next week I will work with my team to get our STAC Server running and hosted within an AWS server for demonstration and testing with our stakeholders.  What challenges, if any, are you currently facing in project development? Do you need instructor assistance?  So far local development has been smooth on a Windows 11 operating system. Containers are able to be built and ran using docker...
Read more

Capstone Project Week 11

What did you accomplish this week? This week I pushed updates to our parser development branch which included additional parsing for remarks and removal of certain metadata properties that were unnecessary for describing the who, what, when, and where of a dropsonde message. In addition I was able to get our parser, STAC API, and STAC browser containers running and hosted AWS, load our STAC database with STAC items using our custom API endpoint integrated with our parser, and test our application's availability on the internet. After confirming our application's accessibility, I scheduled a demonstration with our mentor to show our progress and attain feedback. What is your plan for next week? Next week I will demonstrate our STAC parsing and catalog browsing capabilities within our container hosted on AWS to our project mentor.   What challenges, if any, are you currently facing in project development? Do you need instructor assistance?  I'm not facing any challenges at...
Read more