When looking
around the internet, I found that there was waterfall 2.0 version of the
waterfall software development methodology that we learned at start of class. After
I saw the article, I found out that even the most established practices can
transform to meet the demands of new era. Therefore, I chose this article as it
provides basic summarization of waterfall 2.0 and the difference between
traditional waterfall model. As we talked about why waterfall method was being
replaced by agile and scrum, I thought there will be some people who will try
to improve and use the old working method so using this article showed me how
waterfall transformed to adopt need of current workflow. Therefore, I decided
to look into it as a background for finding out about the improved version as
it revives the dying method into a new form.

             This
article uses baking as an example to illustrate the principles of waterfall 2.0.
It describes the steps on planning, mixing, baking, decorating and enjoying trying
to explain how they work. For example, for planning, allowing adjustments to the
cake showing adaptability, mixing; showing collaboration with others, baking;
showing continuous monitoring, making sure the cake does not burn or become too
dry etc. This shows how the 2.0 fixed many problems of waterfall. In the end,
these changes try to solve the problem of traditional waterfall model that was
not able to adopt to constantly changing environment and unexpected changes to
the requirements and need of the program.

             Reading
this article reminded me why the waterfall model is being replaced by agile or
scrum, not able to meet the industry’s demand in changing environment. Using
cake to explain the new waterfall made the concept more understandable and memorable.
The example clearly showed what the 2.0 version tries to do in order to survive.
The concept of Waterfall 2.0 was particularly impactful because it demonstrated
that no methodology is entirely outdated. If they have the right adjustments,
even traditional approaches can remain relevant in the changing world. In the
future, I thought I might use waterfall methodology in a short and brief project
that what I had to do was very clear. However, finding out waterfall 2.0 I can
try to use it for future project. For example, it could be useful in projects
with fixed deadlines and regulatory requirements, where a hybrid approach
ensures adaptability and flexibility.

Link https://de.celoxis.com/article/waterfall-is-dead-long-live-waterfall-2-0

From the blog Sung Jin's CS Devlopemnt Blog by Unknown and used with permission of the author. All other rights reserved by the author.

When looking
around the internet, I found that there was waterfall 2.0 version of the
waterfall software development methodology that we learned at start of class. After
I saw the article, I found out that even the most established practices can
transform to meet the demands of new era. Therefore, I chose this article as it
provides basic summarization of waterfall 2.0 and the difference between
traditional waterfall model. As we talked about why waterfall method was being
replaced by agile and scrum, I thought there will be some people who will try
to improve and use the old working method so using this article showed me how
waterfall transformed to adopt need of current workflow. Therefore, I decided
to look into it as a background for finding out about the improved version as
it revives the dying method into a new form.

             This
article uses baking as an example to illustrate the principles of waterfall 2.0.
It describes the steps on planning, mixing, baking, decorating and enjoying trying
to explain how they work. For example, for planning, allowing adjustments to the
cake showing adaptability, mixing; showing collaboration with others, baking;
showing continuous monitoring, making sure the cake does not burn or become too
dry etc. This shows how the 2.0 fixed many problems of waterfall. In the end,
these changes try to solve the problem of traditional waterfall model that was
not able to adopt to constantly changing environment and unexpected changes to
the requirements and need of the program.

             Reading
this article reminded me why the waterfall model is being replaced by agile or
scrum, not able to meet the industry’s demand in changing environment. Using
cake to explain the new waterfall made the concept more understandable and memorable.
The example clearly showed what the 2.0 version tries to do in order to survive.
The concept of Waterfall 2.0 was particularly impactful because it demonstrated
that no methodology is entirely outdated. If they have the right adjustments,
even traditional approaches can remain relevant in the changing world. In the
future, I thought I might use waterfall methodology in a short and brief project
that what I had to do was very clear. However, finding out waterfall 2.0 I can
try to use it for future project. For example, it could be useful in projects
with fixed deadlines and regulatory requirements, where a hybrid approach
ensures adaptability and flexibility.

Link https://de.celoxis.com/article/waterfall-is-dead-long-live-waterfall-2-0

From the blog Sung Jin's CS Devlopemnt Blog by Unknown and used with permission of the author. All other rights reserved by the author.

When looking
around the internet, I found that there was waterfall 2.0 version of the
waterfall software development methodology that we learned at start of class. After
I saw the article, I found out that even the most established practices can
transform to meet the demands of new era. Therefore, I chose this article as it
provides basic summarization of waterfall 2.0 and the difference between
traditional waterfall model. As we talked about why waterfall method was being
replaced by agile and scrum, I thought there will be some people who will try
to improve and use the old working method so using this article showed me how
waterfall transformed to adopt need of current workflow. Therefore, I decided
to look into it as a background for finding out about the improved version as
it revives the dying method into a new form.

             This
article uses baking as an example to illustrate the principles of waterfall 2.0.
It describes the steps on planning, mixing, baking, decorating and enjoying trying
to explain how they work. For example, for planning, allowing adjustments to the
cake showing adaptability, mixing; showing collaboration with others, baking;
showing continuous monitoring, making sure the cake does not burn or become too
dry etc. This shows how the 2.0 fixed many problems of waterfall. In the end,
these changes try to solve the problem of traditional waterfall model that was
not able to adopt to constantly changing environment and unexpected changes to
the requirements and need of the program.

             Reading
this article reminded me why the waterfall model is being replaced by agile or
scrum, not able to meet the industry’s demand in changing environment. Using
cake to explain the new waterfall made the concept more understandable and memorable.
The example clearly showed what the 2.0 version tries to do in order to survive.
The concept of Waterfall 2.0 was particularly impactful because it demonstrated
that no methodology is entirely outdated. If they have the right adjustments,
even traditional approaches can remain relevant in the changing world. In the
future, I thought I might use waterfall methodology in a short and brief project
that what I had to do was very clear. However, finding out waterfall 2.0 I can
try to use it for future project. For example, it could be useful in projects
with fixed deadlines and regulatory requirements, where a hybrid approach
ensures adaptability and flexibility.

Link https://de.celoxis.com/article/waterfall-is-dead-long-live-waterfall-2-0

From the blog Sung Jin's CS Devlopemnt Blog by Unknown and used with permission of the author. All other rights reserved by the author.

When looking
around the internet, I found that there was waterfall 2.0 version of the
waterfall software development methodology that we learned at start of class. After
I saw the article, I found out that even the most established practices can
transform to meet the demands of new era. Therefore, I chose this article as it
provides basic summarization of waterfall 2.0 and the difference between
traditional waterfall model. As we talked about why waterfall method was being
replaced by agile and scrum, I thought there will be some people who will try
to improve and use the old working method so using this article showed me how
waterfall transformed to adopt need of current workflow. Therefore, I decided
to look into it as a background for finding out about the improved version as
it revives the dying method into a new form.

             This
article uses baking as an example to illustrate the principles of waterfall 2.0.
It describes the steps on planning, mixing, baking, decorating and enjoying trying
to explain how they work. For example, for planning, allowing adjustments to the
cake showing adaptability, mixing; showing collaboration with others, baking;
showing continuous monitoring, making sure the cake does not burn or become too
dry etc. This shows how the 2.0 fixed many problems of waterfall. In the end,
these changes try to solve the problem of traditional waterfall model that was
not able to adopt to constantly changing environment and unexpected changes to
the requirements and need of the program.

             Reading
this article reminded me why the waterfall model is being replaced by agile or
scrum, not able to meet the industry’s demand in changing environment. Using
cake to explain the new waterfall made the concept more understandable and memorable.
The example clearly showed what the 2.0 version tries to do in order to survive.
The concept of Waterfall 2.0 was particularly impactful because it demonstrated
that no methodology is entirely outdated. If they have the right adjustments,
even traditional approaches can remain relevant in the changing world. In the
future, I thought I might use waterfall methodology in a short and brief project
that what I had to do was very clear. However, finding out waterfall 2.0 I can
try to use it for future project. For example, it could be useful in projects
with fixed deadlines and regulatory requirements, where a hybrid approach
ensures adaptability and flexibility.

Link https://de.celoxis.com/article/waterfall-is-dead-long-live-waterfall-2-0

From the blog Sung Jin's CS Devlopemnt Blog by Unknown and used with permission of the author. All other rights reserved by the author.

If you’re studying or working with Rest APIs, the chances of you running into endpoints are extremely high. I struggled a bit to wrap my head around them, so here’s a casual breakdown. It’s not as scary as it sounds.

What Are API Endpoints?

Let’s start with the basics. An API (Application Programming Interface) is like a menu at a restaurant(HOW MANY TIMES MUST I SAY THIS?). It tells you what’s available (services or data) and how to ask for it (requests). Endpoints are specific URLs on that menu where you go to get what you need.

Imagine you’re at a pizza place. You want to order a pizza with extra cheese and pepperoni. The endpoint is like the part of the menu that says, “Build Your Own Pizza.” It’s where your request (extra cheese, pepperoni) is processed and sent to the kitchen (server), and then your pizza (data) comes back to you.

In tech terms, an endpoint is a specific location on a server where an app interacts with the API to get or send information. For example:

https://api.pizzaplace.com/orders

Here, /orders is the endpoint where you place or check your pizza order.

How Do They Work?

Endpoints use URLs and HTTP methods to define what action you’re taking. These methods are the “verbs” of APIs:

• GET: Asking, “What’s on the menu?” You’re retrieving information.
• POST: Placing your pizza order. You’re creating something new.
• PUT or PATCH: Updating your order, like adding mushrooms.
• DELETE: Canceling your order. Sad day.

When your request hits the endpoint, the server processes it and sends back a response, often in JSON (an easy-to-read data format).

Why Do They Matter?

Endpoints make modern apps and websites possible. For instance, when you check Instagram, there’s an API endpoint fetching your posts. When you order on Amazon, there’s an endpoint processing your purchase. They’re everywhere!

Endpoints keep things organized. Instead of exposing a server’s entire functionality, APIs provide specific endpoints for specific actions. It’s like keeping the kitchen off-limits in a restaurant—you just see the front counter.

Real-World Example

Let’s say you’re building a library app. You might have API endpoints like these:

• GET /books: Retrieve a list of all books.
• GET /books/42: Get details about book #42.
• POST /books: Add a new book.
• DELETE /books/42: Remove book #42.

Each endpoint serves a purpose, and together they make the app functional.

Wrapping It Up

API endpoints are the way apps and servers talk to each other. They’re like doorways leading to the data and services you need. Understanding endpoints is crucial because they’re the foundation of so much of what we build. Whether you’re connecting a frontend to a backend or building your own API, endpoints are the unsung heroes of the digital world.

Next time someone mentions an “endpoint,” you’ll know it’s just a fancy name for a digital doorway.

From the blog CS@Worcester – Anairdo's WSU Computer Science Blog by anairdoduri and used with permission of the author. All other rights reserved by the author.

I chose to write about this Podcast episode in a blog because it’s a topic that resonates with me personally. This episode speaks specifically about the effect COVID had, and how burnout relates to that, which is something that affected me heavily during the COVID year. This isn’t really a topic we discussed directly in class, but Arjun Subramanian is discussing this with Mario Gerard within a technical project management context, which I feel relates to the general theme of what we’ve been discussing thus far in class.

Something Gerard and Subramanian talk about is establishing a boundary between work life and home life. This comes naturally when you’re clocking in to work from 9-5, and forgetting all about work as you come home, but when working from home it becomes harder to mentally separate the two. Working from home in the tech industry has its undeniable benefits, and there’s a reason so many people in the field prefer it, but with increased productivity also goes hand in hand with increased effort, or at least prolonged effort. It becomes harder to create a boundary between work and life when there’s no physical separation between the two. This is something that impacted me heavily, because prior to this I always kept strict separation of my school life and family life. I never invited school friends over, I only did schoolwork in my room privately, or I would set aside time at school to do it, I never talked about school at home or talked about family at school. And while I was at UMass in 2019, I had a taste of freedom for the first time. School life and social life was blending together in a way that I had never allowed it to back home. Coming home from UMass due to COVID was a huge detriment to that, and having to manage my online courses with my tense familial struggles was something that wore me thin.

The podcast also discusses how toxic environments can contribute to burnout, and the necessity of having the agency to manage and create your boundaries. You can speak up, and you work as hard as you can within your specific timeframe, and you put your heart into it, and once that time is up you come back to earth and you don’t allow work to cross that boundary into personal life.

As far as toxic situations go, that doesn’t necessarily mean a difficult one. As Subramanian talks about, you can have a difficult situation that’s right, and you need to show “grit and tenacity”. But a toxic situation is one you need to walk away from, for your own sake. There may not be a clear way to identify a toxic situation from just a difficult one, but there are signs, and while they talk about some of the signs on the podcast, the bottom line is that you need to have your own well-being in mind as you work.

The discussion about boundaries and toxic situations is one that I feel are a major contributor to the way I was affected by burnout over the COVID years, and something I’m aware I need to look out for, now and in the future.

Podcast Link: https://www.mariogerard.com/tpm-podcast-with-arjun-subramanian-project-manager-burnout/

From the blog CS@Worcester – Justin Lam’s Portfolio by CS@Worcester – Justin Lam’s Portfolio and used with permission of the author. All other rights reserved by the author.