My name is Seth Boudreau and I am a computer science student attending Worcester State University. I am going into my fourth year now as a student here and I am mainly making this blog to go along with my studies. Most of the information that I will type here will be for my two courses this semester: CS-343 and CS-348 and topics will vary based on information within the two courses.

From the blog CS@Worcester – Works for Me by Seth Boudreau and used with permission of the author. All other rights reserved by the author.

This is my CS-348 blog.

From the blog CS@Worcester – My Coding Blog by Jared Delaney and used with permission of the author. All other rights reserved by the author.

Hello, I’m William Do! This is for CS-348.

From the blog CS@Worcester – wdo by wdo and used with permission of the author. All other rights reserved by the author.

Hello! Welcome to my blog. My name is Elizabeth Baker, and this is my introduction post for two Computer Science courses at Worcester State University: Software Construction, Design, and Architecture and Software Process Management.

Later blogs will focus on taking course material and connecting them to various resources in class and on the world wide web, to build my understanding, confidence, and resourcefulness as a developing engineer. Here’s to endless knowledge and professional growth!

From the blog CS@Worcester – Vision Create Innovate by Elizabeth Baker and used with permission of the author. All other rights reserved by the author.

This blog will be my space to share ideas, reflections, and lessons I pick up as I continue growing in the fields of technology and business. I am especially interested in business analysis and data analytics, because I believe data has the power to tell stories, guide better decisions, and create solutions that have real impact. Whether it’s exploring new technologies, breaking down complex problems, or learning from others in the industry, I want to use this platform to capture that journey.

I see this blog as more than just a collection of posts. It’s a way to practice communicating ideas clearly, to connect with others who share similar interests, and to start building a professional portfolio that reflects both my technical background and my business mindset. Over time, I hope these posts will not only track my own progress but also serve as a resource for anyone interested in the intersection of tech and business.

I’m excited to begin this journey and look forward to sharing my growth, one connection at a time.

From the blog CS@Worcester – Circuit Star | Tech & Business Insights by Queenstar Kyere Gyamfi and used with permission of the author. All other rights reserved by the author.

My name is Brady Splaine and this is going to be my blog for my posts for my software process management class.

From the blog CS@Worcester – Splaine CS Blog by Brady Splaine and used with permission of the author. All other rights reserved by the author.

I am Dipesh Bhatta, born and raised in Nepal, and currently living in Worcester, Massachusetts. I will be graduating in May 2026 from Worcester State University with a major in Computer Science.

From the blog CS@Worcester – dipeshbhattaprofile by Dipesh Bhatta and used with permission of the author. All other rights reserved by the author.

I listened to the podcast episode “Comparing Git Workflows” from CodingBlocks, which relates git and workflow strategies. This podcast explores different ways that teams structure their Git workflows, what the trade offs are among them, and when one approach might be more suitable than another. They discuss many different workflows such as feature branching, Gitflow, centralized workflows, and many more. Taking into consideration on how these choices affect collaboration, history cleanliness, conflict resolution, etc. They compare simpler approaches that are easier for small teams with more structured models that are more strict for larger, distributed projects. They highlight how workflow decisions impact and affect team.

I chose to listen to this podcast because our course has just started to learn about git and how version control works in terms of commands like commit or branch. Learning about how workflows and team agreements integrate into real-world coding practices is likely going to be important and something we will work on in this course. “Comparing Git Workflows” gave me deeper insight into how different teams make those decisions and how those decisions can affect the teams workflow.

Listening to the episode taught me that no one plan is ideal for every situation. Before, I had assumed that there would be one best practice for all around coding, but hearing how workflow can change based on taken actions was eye opening. I also realized that simpler workflows might sacrifice structure or history clarity, but can offer agility, especially for smaller teams or solo developers. The discussion on this podcast helped clarify for me how preserving a linear history can help with finding bugs or reading logs, but also how tools can be misused if people rewrite shared history. Another takeaway was how important it is for teams to agree explicitly on their workflow, branching naming conventions, pull request practices, and many more key aspects. Hopefully I can apply what I learned in future team projects and potential jobs that are upcoming.

From the blog CS@Worcester – Coding with Tai by Tai Nguyen and used with permission of the author. All other rights reserved by the author.

“How to create issues and pull requests in record time on GitHub” by Jon Peck is a blog discussing the importance of issues and pull request as well as how to efficiently use them. This blog goes on to explain how GitHub has improved the process of creating issues and pull requests, particularly with the help of GitHub Copilot. Instead of manually drafting titles, descriptions, labels and then writing separate pull requests, developers can use Copilot to assist with both issue creation and the process of turning those issues into draft pull requests. To start this blog reminds readers why well structured issues and pull requests are important. They provide shared information, enable online coordination, and many more important matters. It then explores the concepts of a good issue, including clear titles, explanations of expected versus actual behavior, reproduction steps or visual evidence, definitions of done, scope, constraints and useful data. From there the article shows how you can use Copilot Chat to speed up drafting issues. A developer can describe what is needed, include screenshots, and let Copilot suggest labels. Finally it demonstrates how to turn issues into draft pull requests by assigning them to a Copilot coding agent which can clone the repository, work in a secured workspace and produce commits in a draft pull request that remains open to continuous integration.

I chose this article because in our first pogil activity I didn’t have much experience using git and it’s available tools. Having read up on how version control tools are used not just for storing code but also for managing collaboration, code quality and workflow efficiencies. I learned that Issues and pull requests are surprisingly important to that process. This post shows explains this, It connects directly to what we have worked on in lectures, more specifically about assignment 1 about github, pull request reviews, issue tracking and practices in version control.

After reading this blog, the idea of version control to me is more than committing code or branching, it is about clear communication, traceability and making sure issues and pull requests are useful. I realized how much poorly constructed issues and pull requests slow down not only human reviewers but also automation tools. The idea of assigning a coding agent to issues via Copilot is interesting because it includes both human oversight while utilizing automation. In my future projects, I plan to apply these ideas by using formatting every issue in a useful way, making sure pull request descriptions link back to the issue and clearly explain what was done, and paying attention to data early so that project tracking and team collaboration become easier.

https://github.blog/developer-skills/github/how-to-create-issues-and-pull-requests-in-record-time-

From the blog CS@Worcester – Coding with Tai by Tai Nguyen and used with permission of the author. All other rights reserved by the author.