One thing I found interesting from the reading was the Agile values and principles, and the Twelve Principles of Agile Software. I found this interesting because it puts people and teams before the product, encouraging communication and teamwork over raw productivity. I found this interesting because I would have thought that everything would be based around getting the most productivity, but instead it emphasizes the process and making interaction within the team as smooth as possible. I really like the policy of responding to change rather than following a plan, because even though having a plan is great, sticking with a failing plan is most often a bad idea. I chose to write about this because this stuck out to me as good, common-sense practices that it seems often aren’t used.

From the blog CS@Worcester – Alex's Blog by anelson42 and used with permission of the author. All other rights reserved by the author.

When looking through the Thea’s Pantry GitLab Group, I saw something that interested me with the release process where we have to use semantic-release when we make new working builds and new merge requests are accepted. There we can see that this helps makes the release process automatic without human interaction; leaving it “unromantic and unsentimental”. It didn’t occur to me before but when reading the link that phrase led to how people think differently about changing the version number. It looks as though when reading that website, that we don’t care about the creative values and expressions they talk about and just keep things standardized and clean.

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

Despite being intrigued by the many interconnected systems, it gives me a sort of confidence that people can overcome their current level of understanding which we’re comfortable with, and can confidently connect these differing types of information to make a solution that seems to be a logical conclusion. I have to admit that such data is something that may be inconclusive to my biases that hold me to my biased endings, but I always try my best to side with the morally better decision, no matter how difficult. I certainly acknowledge the difference of opinion, and the potential radicalization I may bring, but in the light of our current civilization, I only want the best for the people of my nation.   

From the blog CS@worcester – Dummies that Code by howbrash and used with permission of the author. All other rights reserved by the author.

For my capstone project in CS-448, we are working on the libre food pantry which I have taken a look into the mission, values, code of conduct, etc. I have read about the FOSSisms which provided good information about the opened sourced culture into sixteen parts. Such as, respecting the community and to get in-depth with the community purpose and guideline and whatever to dig up into the project you are interested in. The steps give me more insight on how to go about the open source world. And how to go about it. In step 3, to give community back intrigued me because when we are in a field working on a project we make as much positive contribution as possible to gather answers from others or give answers to others, where it is a positive two communication to continually improve your community.

From the blog cs@worcester – Dahwal Dev by Dahwal Charles and used with permission of the author. All other rights reserved by the author.

I looked through the documentation for Thea’s Pantry to get an idea of what the project is about and how the project works. Of the sections, the User Stories section stood out to me the most because I felt like that t gives an idea of how the project should work, what features it should have, who it is serving, and what the software architecture should look like. I think this guide is very helpful for future reference when working on the project myself. I think that it is something that I will revisit frequently to make sure that I am on the right track.

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

As I’ve been engaged with the internet for most of my life, I’m not entirely surprised, but I’m little unsettled by the Code of Conduct/Our Standards of the site. I didn’t realize with such a helpful type of engagement that standards such as these are as important as they seem to be. I suppose I wish this this type of medium was not as aggressive, as it would encourage a better attitude towards the people involved, but I’m familiar with the type of rhetoric people use on the web, and I am disappointed as it is needed to specify a certain type of behavior. I hope it is a failsafe rather than a direct shutdown of awful things that people say, but I understand the logic in case some awful people feel the need to post on the thread.

From the blog CS@worcester – Dummies that Code by howbrash and used with permission of the author. All other rights reserved by the author.

It is exciting to learn about the software being used in building an entire working system from bottom to top. I will research but briefly talk about Kubernetes, RabbitMQ and Keycloak since these are the software I personally have not used before.

Keycloak is an open-source Identity and Access Management solution for modern applications and services. It offers features such as Single-Sign-On (SSO), Identity Brokering and Social Login, User Federation, Client Adapters, an Admin Console, and an Account Management Console.

RabbitMQ is a message broker that implements Advanced Message Queuing Protocol (AMQP). Basically, it is a messaging system used for decoupling software components. It also Performs background operations and asynchronous operations.

As complexity increases in containers, features like; automated deployment, the orchestration of containers, scheduling apps, granting high availability, managing a cluster of several app instances, etc. are needed. Kubernetes is a tool that provides all these features.

From the blog CS@worcester – Towards Tech by murtazan and used with permission of the author. All other rights reserved by the author.

The mission statement by Libre food pantry is very similar to my personal life goals. I as well hope to use my computer science knowledge and skills I have obtained towards the betterment of not just humans, but also human society, our standard of living, environment, and planet earth in general.

There is also a false belief among the common masses that people in computer science just have to write their part of code and move on. Therefore, they do not work well with other people or just don’t have to work with other people. Mission statement of Libre food pantry states right from the start that they are a “vibrant, welcoming community of clients, users, and developers” working together as an unit and team to achieve their goals.

From the blog CS@worcester – Towards Tech by murtazan and used with permission of the author. All other rights reserved by the author.