Skip to main content

CST 499 - Week 2

This week, our group continued working on the current iteration of our capstone project. Sebastian has done a fantastic job so far setting up the baseline code/master branches for both the client and server, and we have a good starting point to expand on. Progress is going well and development continues.

For our group meeting this week, there were several items/tips/good practices from the "Effective Meetings" week that we followed:

 1. The purpose of the meeting was clear: similar to a Scrum meeting, we discussed current work in progress and what was finished last week, along with any technical issues in development.

2. Agenda was clear and on topic.

3. Action items were discussed and assigned.


Since I've been back to work in the office and lab and attending daily scrum meetings for software test over the phone, I've been making note of what I think is effective regarding teleconferences and trying to implement them into our own group meetings. 


Resume Reviews


I reviewed several peer resumes and LinkedIn profiles this week, and I saw a couple of great resumes with interesting, yet professional design language that I admired. If I ever decide to reformat my own resume in the future, I've got some good inspiration now. Also, I noticed the resumes that I did review followed most good resume practices, although I always find it to label a resume "good" or "bad" because it's so specific to the position you're applying for. I'll have to get some more insight on what a "good" resume has from my manager once I get the chance. 



Comments

Popular posts from this blog

The Final Journal

It's the end of a long, four year journey, and what a journey it has been. I never thought I could pull off finishing my second bachelor's degree four years ago when I first went to that introduction to programming class at my community college. I would like to thank all the friends I've made along the way and the people who have helped me through the last two years. Although it was difficult at times taking class while working 40+ hours a week, I'm proud of myself for making it through. I don't think I'll be a student enrolled in classes anytime soon, but I'll always be a lifelong student. See you all around.

CST 300 - Week 4

Educational Goals My current educational goals are to finish my bachelor's degree in computer science while also gaining a deep understanding of the fundamentals along the way. I have always believed that a solid understanding of the fundamentals goes a long way in any skill since you always refer back to them. When I have gotten stuck on a problem or some skill in the past, I have always taken a step back, broken down things into smaller pieces and remembered my fundamentals, and doing so has helped me through a lot of academic and professional work so far. Although I already know basic programming and data structures, I want to learn more about them and discover new ways of thinking in order to solve complex problems.  Career Goals I started a career as a full-time software test analyst about two months ago. Even though my job doesn't involve a lot of programming, getting a degree in computer science would be really helpful in all aspects of my career, such as identif...

CST 499 - Week 5

This week, our group completed a major milestone in our project by finishing the front end of our application, marking it as a "feature complete". We also conducted our initial round of user acceptance tests and received plenty of useful feedback, comments, and suggestions for the final stages of development and eventual deployment.  As a test engineer, I also interact with end customers doing software system test, so I understand quite well the process of conducting tests and then signing off said tests if they meet all requirements as specified. Since my company must comply with Department of Defense standards, the "rules of engagement" for testing and product acceptance are much stricter than our standards for capstone, but I can imagine similar rules would be applied to other students doing industry projects. Also, I got my first experience writing a test procedure from scratch by myself, as even at my job I am not responsible for writing procedures but I am acc...