Hello, My name is Aksh Patel, and this is my introduction blog. I am a senior year Worcester State University student. My major is Computer Science and i am more interested Design Technique.
I will take CS-343 class to learn about more in my interesting stuff.
From the blog CS@Worcester – Pre-Learner —> A Blog Introduction by Aksh Patel 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.
Welcome to Dev Patterns. This blog will serve as a platform for looking at software development methods, design choices and architectural frameworks. The purpose of this is to document my learning journey as I advance n the computer science realm. Writing in this space will assist me monitor the progress, structure and share my ideas and also share various insights that might be beneficial to everyone with the same interest as me.
You can anticipate some interesting articles and information covering a range of subjects from coding practices to system design concepts, always keeping the overarching goal in focus: how we can create software that is dependable, maintainable, and efficient.
I am eager and excited to embark on this journey so sit back and enjoy with me. Welcome to my mind!
From the blog CS@Worcester – MY_BLOG_ by Serah Matovu 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.
This is an introduction to my blog. I am taking software construction, design, and architecture, and I will be recording my blogs here. I am excited for what this class has to offer, and I hope I learn and grow!
From the blog CS@Worcester – Aaron Nanos Software Blog by Aaron Nano and used with permission of the author. All other rights reserved by the author.
hello
xin chào
你好
こんにちは
This is my first blog post for CS-343! My name is Gia Vuong and I’d prefer to be called Kiet. I’ve been doing WordPress blog for a year now since my last year with CS-348 – Software Process Management. This year marked the year that I am now using Linux for the first time, so I’d be happy to help if anyone is getting started, or currently using Linux as if you have any questions.
I’d love to know more about everyone, and get connected with anyone in our CS community here in Worcester State!
From the blog CS@Worcester – Hello from Kiet by Kiet Vuong and used with permission of the author. All other rights reserved by the author.
Hello! My name is William Cordor and this is my blog.
From the blog CS@Worcester – Blog del William by William Cordor and used with permission of the author. All other rights reserved by the author.
Hey this is my introduction post to CS Notes Blog
This blog will be for me to post about the different things I’ll be learning about in CS-348.
The current use of this space is to fulfill the course objectives, if I find it helpful I may continue to use it. We’ll see.
From the blog CS@Worcester – CS Notes Blog by bluu1 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.