Welcome back to my blog. If you didn’t know, my name is Kyler and this is where I’ll be occasionally making blog posts about topics that relate to software, computers, programming, and the like.
From the blog CS@Worcester – Kyler's Blog by kylerlai and used with permission of the author. All other rights reserved by the author.
Welcome back to my blog for this semester! My name is Josh, and I will be discussing Software Development topics related to the construction, design, and other elements of software. Hope you enjoy!
From the blog CS@Worcester – Josh's Coding Journey by joshuafife and used with permission of the author. All other rights reserved by the author.
Hey. I am a student at WSU taking CS 343. This is a test post to introduce the blog and make sure it appears on the CS@Worcester blog.
From the blog CS@Worcester – Mr. Lancer 987's Blog by Mr. Lancer 987 and used with permission of the author. All other rights reserved by the author.
Hello, my name is Giovanni Casiano and am a senior at Worcester State University majoring in Computer Science. I am looking forward to learning as much as I can during this course.
From the blog CS@Worcester – Giovanni Casiano – Software Development by Giovanni Casiano and used with permission of the author. All other rights reserved by the author.
Hello again,
My name is Anthony Cao, and I will continue to use this blog to document my education in software development and what it has to offer. I am taking another software class that will correct the way I write code, making it more efficient.
From the blog CS@Worcester – Cao's Thoughts by antcao and used with permission of the author. All other rights reserved by the author.
This is my CS 343 Blog
From the blog CS@Worcester – WSU CS Blog: Ben Gelineau by Ben Gelineau and used with permission of the author. All other rights reserved by the author.
To begin, my name is Oanh Nguyen. At this point and time, a student at the university of Worcester State. I major in computer science and minor in business administration. Another thing to add is that I’m currently taking ‘Software Constr, Des & Archit’ and many further blog will be related to this class. Which will be tagged accordingly.
While I’m not particularly great at programming, I enjoy problem solving and those moments where I succeed in getting a project done. The reason I choose to major is because there was a ‘Discrete Structure’ class I took in the past and I enjoyed it great. I wished to take a further step in that direction, although I do not know where it will take me.
It’s nice to meet you, who is reading this. Thank you.
From the blog SoftwareDiary by Oanh Nguyen and used with permission of the author. All other rights reserved by the author.
This blog page will be used to discuss my findings and research throughout my courses. This will be a gateway to look back on and view how much improvement I have made or even the different technologies I used previously.
From the blog CS@Worcester – Cinnamon Codes by CinnamonCodes and used with permission of the author. All other rights reserved by the author.
Hi everyone, my name is Abdullah Farouk, for those who don’t know me by now, and this is going to be my first sprint retrospective of the semester. First, I will start out by saying, considering this whole thing is brand new to us, we did a great job working with this new style and adapted quickly to all the changes. Don’t get me wrong, there is still a lot of room for improvement from everyone in the team, but we successfully passed through this semester. This sprint consisted of us getting more familiar with libre food pantry more and to see how this scrum framework actually go and went more in depth into the actual system. The first thing we did in the beginning of the semester was weighing the different issues and breaking some epics into smaller issues and assigning it to our team. We then organized the issues on which one we wanted to do first and so on. I worked on most of the issues during class time, which worked out nicely because I had my team member there to help me with things just in case, I got stuck, which I did sometimes. I liked meeting in person instead of virtual meetings, as I think we do more work when we see each other instead of behind a computer screen.
One thing that I would say the we massively on was how we weighed the issues in the beginning. Compared to the first sprint, Some of the issues took less than what we had anticipated, and some took way longer, but this sprint we got it spot on and managed to finish all the issues on the board just in time. Another thing that we improved on was communicating outside of class time. I started privately messaging class mates for updates if they haven’t said anything in days. One thing we still didn’t do well was Some of the issues we had made, we didn’t add a description to it, so it was a little harder for me to figure out what they want me to do just from the title, so I had to ask classmate to double check.
Other than that one issues, I think me, and the team did a great job going through these issues and completing them on a timely basis. I worked on multiple issues for this sprint that I will list at the ends, but mostly I was trying to clean up code and made sure anything that I had left unfinished, was either finished or deleted so the next class is not having a headache trying to figure out why it’s there. I also checked a couple of my classmate’s issues that needed to be reviewed in order to merge to main. I also worked on. I also learned a lot about nodemon function and have a basic understanding of how it works and how to properly integrate it.
From the blog CS@Worcester – Farouk's blog by afarouk1 and used with permission of the author. All other rights reserved by the author.
In Chapter 3 of “Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman,” entitled “Walking the Long Road,” the focus lies on recognizing that achieving mastery in fields like software development is a gradual process demanding persistence, endurance, and ongoing education.
The chapter opens by stressing the importance for aspiring craftsmen to accept that attaining mastery is not an immediate goal but rather a journey that unfolds over time. It underscores the comparison to a lengthy road trip, where the adventure itself holds equal importance to reaching the final destination. This change in mindset is essential for newcomers to the realm of software development, aiding them in valuing the journey of honing their skills and achieving expertise.
Following this, the chapter presents the “Long Road” pattern, advocating for prioritizing long-range growth over pursuing immediate rewards or quick fixes. It stresses the significance of establishing realistic objectives, fostering a mindset of continuous improvement, and dedicating oneself to regular practice and enhancement of skills throughout the journey.
An interesting element of this chapter lies in its focus on the importance of persistence and fortitude when confronted with difficulties and setbacks. It underscores the certainty of facing obstacles during the pursuit of mastery and urges readers to perceive these challenges as chances for personal development rather than excuses to surrender.
Additionally, the chapter offers actionable guidance on effectively traversing the lengthy journey. It recommends approaches like seeking mentorship, engaging with communities of practitioners, and embracing intentional practice to expedite the process of learning and skill refinement.
In summary, Chapter 3 of “Apprenticeship Patterns” underscores the essential components of achieving mastery in software development, emphasizing the need for commitment, endurance, and an appreciation for the process. By embracing the philosophy of “walking the long road” and heeding the chapter’s advice, aspiring software craftsmen can embark on a journey toward ongoing advancement and eventual expertise in their field of choice.
Ultimately, this pattern can inspire a more sustainable and fulfilling approach to your intended profession, one that emphasizes continuous learning, resilience, and a commitment to long-term improvement.
From the blog CS@Worcester – THE SOLID by isaacstephencs and used with permission of the author. All other rights reserved by the author.