Week 7

 Part One

This week is the last week for CST300, we collaborated well as a team. We broke down the Final Research Video Project to sections, each team member will be responsible for a section. We agreed on getting a daft ready for our team meeting this Thursday and discussing anything that needs to be edited or improved. I had not used PowerPoint for a long time, it was fun getting to relearn PowerPoint and it was my first time using the record button. I found it easy to work with my team. In the future I think as a team it would be helpful to make an outline with what will be presented in the PowerPoint before we start the audio recording. 



Part Two

We watched ted.com videos this week, I watched With AI, anyone can be a coder now, it was a very interesting video. The video explained how it program was very difficult to understand as it evolved it became more familiar to understand. In a short span of time AI has made it possible for anyone start coding with the help of copilot. It speeds up writing code. With AI we can ask question regarding what a few lines of code does. It makes it so simple even a child can now understand programing. The newest development of tools that help software developers is called Copilot Workspace. Where you can ask it what you want and it gives poses some code writes all the code for you.  

I also watched Your right to repair AI systems. How farmers have "smart" tractor equipment that only manufacturers can repair equipment. These "smart" tractors use software that the manufactures make it illegal if anyone else works on it and fixes. They control the right but this right should extend to AI.  

We learned about presentation skills such as how to use PowerPoint. Some key take aways I learn was to not use too many charts, pictures and not to use too many bullet points. PowerPoint slides should be kept with minimal animations, color scheme should be Appling and easy to read. 

Comments

Post a Comment

Popular posts from this blog

CST438 Software Engineering: Week 8 (Final week)

 One of the most important things I learned is that software engineering is about much more than just writing code. While coding is a big part, there's a strong emphasis on documentation, understanding client needs, and getting continuous feedback. It’s about designing systems so others can easily improve them and applying principles like "low coupling and high cohesion" to keep things modular and maintainable.      Another key lesson was understanding the entire development process from end to end. This was the first time I worked with both the front end and back end together, fully grasping the HTTP protocol (including how methods like POST work), how JSON is used, and how the front end communicates with the back end. Seeing how everything fits from database interactions to deploying the app online—gave me a fascinating glimpse into the full workflow and a lot of practical experience.      Another important lesson was learning how to work as part of ...
Read more

CST438 Software Engineering: Week 1

What did you expect a course in Software Engineering would cover? I expected it to cover how to build applications from the ground up and the design behind application development. I thought we would look at other things we’ve been learning in this program, like database management, front end development, and back end work, and then put it all together into one complete project. After completing week 1, how has your opinion changed? Well, I never really thought much about keeping an application’s design maintainable for future improvements or changes. There is a lot more that goes into software engineering than just simple programming. It is  about planning ahead, documenting your work, checking for errors, and testing properly to avoid issues later. I’ve also realized software engineering looks at the big picture it is not just about coding and design but about how software impacts people and how teams work together to build it. Developers need to stay motivated, think critical...
Read more

CST370 Week 5

Hello everyone,  This week we studied binary‑tree traversals preorder, inorder, and postorder but I kept mixing them up. I finally got it when I attended TA office hours, and it clicked. Walking through Quick Sort step by step helped me see how the Decrease and Conquer approach works by breaking problems into smaller chunks. Then we looked at Kahn’s algorithm, and watching it remove nodes with no incoming edges reminded me of picking a pivot in Quick Sort. Seeing these patterns repeat helped me realize that many algorithms work by simplifying things piece by piece. 
Read more