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

CST 499 - Week 7

This week, our group finished recording and editing our capstone project video and prepared our presentation for the capstone festival. Although I wish the capstone festival was held in person (and it could not due to current circumstances), I am excited to show off our project and hard work to other computer science students, friends, and family. I hope they'll enjoy it and learn something cool while doing so. 

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 499 - Week 3

This week, we finished our ILP portfolios and turned in the final versions of our resume and cover letter. My group also completed the first part of the capstone report. I'll admit that creating a portfolio showcasing my past work was not at the top of my priority list when I first started studying computer science, although at this point in my educational and professional career I've learned how important it is to have such a portfolio. Like other creative professions, having a solid body of work to show to a potential employer, or even for personal documentation is one of the best ways to display your talents as an engineer. Also, all the assignments I've completed during my academic career, both at CSUMB and elsewhere, have given me a good start to my portfolio. I tend to prefer classic, plain styling like  Brian Kernighan's  home page (he has a pretty nice portfolio too), although I've come to appreciate highly stylized portfolios that make use of WebKit ani...