Backend development is an essential part of creating a
dynamic, interactive website or application. The backend, also known as the
server-side, is the part of the website or application that manages the data
and logic behind the scenes. It works in conjunction with the frontend, or the
client-side, which is what users see and interact with.

There are several components that make up a backend,
including a server, an application, a database, and an API. The server is the
physical location where the website or application is stored and accessed. The
server is responsible for hosting the website or application and delivering it
to users when they access it. The application is the actual software that runs
on the server and provides the functionality of the website or application. It
is typically built using a programming language, such as Java or Python. The
database is where the data for the website or application is stored. The
database is used by the application to store and retrieve data, such as user
accounts, information about products or services, and other data needed by the
website or application. The API, or application programming interface, is a set
of protocols and tools that allow different software applications to
communicate with each other. In the context of backend development, the API is
what allows the frontend and the backend to communicate and exchange data. For
example, when a user interacts with the frontend of a website or application,
the API allows the frontend to send requests to the backend and receive
responses with the relevant data.

I selected this post
because I am interested in learning more about backend development and how it
plays a role in creating interactive websites and applications. Furthermore, a
lot of work for this class went into writing code for and experimenting with,
the backend code for Thea’s Food Pantry. Working on something actively in use, even
without making any changes, was a very interesting experience and will be
immensely useful for the capstone class next semester. Understanding the
importance of the backend and how it works with the frontend will allow me to
better plan and implement the overall architecture of a website or application.
Additionally, learning about the various backend components and their functions
will allow me to make informed decisions when choosing technologies and
frameworks to use in my projects.

Source:

https://www.codecademy.com/article/back-end-architecture

From the blog Zed's Blog by Lord Zed and used with permission of the author. All other rights reserved by the author.

Backend development is an essential part of creating a
dynamic, interactive website or application. The backend, also known as the
server-side, is the part of the website or application that manages the data
and logic behind the scenes. It works in conjunction with the frontend, or the
client-side, which is what users see and interact with.

There are several components that make up a backend,
including a server, an application, a database, and an API. The server is the
physical location where the website or application is stored and accessed. The
server is responsible for hosting the website or application and delivering it
to users when they access it. The application is the actual software that runs
on the server and provides the functionality of the website or application. It
is typically built using a programming language, such as Java or Python. The
database is where the data for the website or application is stored. The
database is used by the application to store and retrieve data, such as user
accounts, information about products or services, and other data needed by the
website or application. The API, or application programming interface, is a set
of protocols and tools that allow different software applications to
communicate with each other. In the context of backend development, the API is
what allows the frontend and the backend to communicate and exchange data. For
example, when a user interacts with the frontend of a website or application,
the API allows the frontend to send requests to the backend and receive
responses with the relevant data.

I selected this post
because I am interested in learning more about backend development and how it
plays a role in creating interactive websites and applications. Furthermore, a
lot of work for this class went into writing code for and experimenting with,
the backend code for Thea’s Food Pantry. Working on something actively in use, even
without making any changes, was a very interesting experience and will be
immensely useful for the capstone class next semester. Understanding the
importance of the backend and how it works with the frontend will allow me to
better plan and implement the overall architecture of a website or application.
Additionally, learning about the various backend components and their functions
will allow me to make informed decisions when choosing technologies and
frameworks to use in my projects.

Source:

https://www.codecademy.com/article/back-end-architecture

From the blog Zed's Blog by Lord Zed and used with permission of the author. All other rights reserved by the author.

Backend development is an essential part of creating a
dynamic, interactive website or application. The backend, also known as the
server-side, is the part of the website or application that manages the data
and logic behind the scenes. It works in conjunction with the frontend, or the
client-side, which is what users see and interact with.

There are several components that make up a backend,
including a server, an application, a database, and an API. The server is the
physical location where the website or application is stored and accessed. The
server is responsible for hosting the website or application and delivering it
to users when they access it. The application is the actual software that runs
on the server and provides the functionality of the website or application. It
is typically built using a programming language, such as Java or Python. The
database is where the data for the website or application is stored. The
database is used by the application to store and retrieve data, such as user
accounts, information about products or services, and other data needed by the
website or application. The API, or application programming interface, is a set
of protocols and tools that allow different software applications to
communicate with each other. In the context of backend development, the API is
what allows the frontend and the backend to communicate and exchange data. For
example, when a user interacts with the frontend of a website or application,
the API allows the frontend to send requests to the backend and receive
responses with the relevant data.

I selected this post
because I am interested in learning more about backend development and how it
plays a role in creating interactive websites and applications. Furthermore, a
lot of work for this class went into writing code for and experimenting with,
the backend code for Thea’s Food Pantry. Working on something actively in use, even
without making any changes, was a very interesting experience and will be
immensely useful for the capstone class next semester. Understanding the
importance of the backend and how it works with the frontend will allow me to
better plan and implement the overall architecture of a website or application.
Additionally, learning about the various backend components and their functions
will allow me to make informed decisions when choosing technologies and
frameworks to use in my projects.

Source:

https://www.codecademy.com/article/back-end-architecture

From the blog Zed's Blog by Lord Zed and used with permission of the author. All other rights reserved by the author.

Backend development is an essential part of creating a dynamic, interactive website or application. The backend, also known as the server-side, is the part of the website or application that manages the data and logic behind the scenes. It works in conjunction with the frontend, or the client-side, which is what users see and interact with.

There are several components that make up a backend, including a server, an application, a database, and an API. The server is the physical location where the website or application is stored and accessed. The server is responsible for hosting the website or application and delivering it to users when they access it. The application is the actual software that runs on the server and provides the functionality of the website or application. It is typically built using a programming language, such as Java or Python. The database is where the data for the website or application is stored. The database is used by the application to store and retrieve data, such as user accounts, information about products or services, and other data needed by the website or application. The API, or application programming interface, is a set of protocols and tools that allow different software applications to communicate with each other. In the context of backend development, the API is what allows the frontend and the backend to communicate and exchange data. For example, when a user interacts with the frontend of a website or application, the API allows the frontend to send requests to the backend and receive responses with the relevant data.

I selected this post because I am interested in learning more about backend development and how it plays a role in creating interactive websites and applications. Furthermore, a lot of work for this class went into writing code for and experimenting with, the backend code for Thea’s Food Pantry. Working on something actively in use, even without making any changes, was a very interesting experience and will be immensely useful for the capstone class next semester. Understanding the importance of the backend and how it works with the frontend will allow me to better plan and implement the overall architecture of a website or application. Additionally, learning about the various backend components and their functions will allow me to make informed decisions when choosing technologies and frameworks to use in my projects.

Source:

https://www.codecademy.com/article/back-end-architecture

From the blog Zed's Blog by Lord Zed and used with permission of the author. All other rights reserved by the author.

The blog I reviewed this week delves deeper on the topic of design smells and the classifications of some of them in different situations, some of which we had discussed in previous classes and some new ones that prove to be important to know in the long run. this article focus on design smells in the UI/UX side of programming and more specific to this side but still very much important.

The first discussed is “Documentation for Power users” which is the separate documentation used on portals to different sights when users click hyperlinks, or the different section on a Website or application. the issue comes from the formating and the flow of said website many look very cluttered and the flow of information is jumbled up. One specific example that is used for this smell is the Use of Microsoft Excel, the main focus being that it is a universally used application and thus has universal tools that the users disposal, the issue with such a great tool as without distinct tools being separated from the ones a user might not use in order to optimize the users experience it overwhelms them. this goes for all users as there is no case by case optimization, one solution brought up would be to dissect the application into separate products in order to better organize the UI for consumers in different situations, such as one made for educational use and one for corporate.

Another Smell that is discussed and closely relates to the previous is “Excessive Iconography”, this smell focuses on the use of unclear icons to display information in large loads, if we look at the example used in the blog of Xcode on Mac with many of the icons and labels out all on the same display to overwhelm the developer, making the tasks more difficult. the issue isn’t that the Labels or the Icons are not clear, but there are to many options and features present on the same screen. one way to combat this is to structure the application into smaller instances including all features that are connected together, allowing for clearer labeling and better overall experience for users. one personal example of this kind of structure I found was on Jira which structured its features according to what the user needed, allowing for a seemless UI and better experience. it did this but hiding features entirely that were not necessary and clearly labeling its tools.

Yodaiken, Aaron. “Ux Smells.” Medium, UX Collective, 7 Feb. 2017, https://medium.com/user-experience-design-1/ux-smells-fa971feef820.

From the blog cs@worcester – Marels Blog by mbeqo and used with permission of the author. All other rights reserved by the author.

The Principle of Least knowledge also called the law of Demeter, as explained in Eric Feminella’s blog “Principle of Least Knowledge”, is a design principle that provides guidelines for designing a system with minimal dependencies.  It is summarized in short as “Only talk to your immediate friends.”

A client should have knowledge of an object’s member, and not have access to properties and methods of other objects via the members.

The example shown in the blog has three classes: ClassA, ClassB, and ClassC. ClassA has an instance member of type ClassB and ClassB has an instance member of type ClassC. This shows that all the classes are connected one by one, and this can be extended further ClassC if need be. Now believe it or not this example violates The Principle of Least Knowledge because it creates multiple dependencies, thus reducing the maintainability because if ClassA needs some work so would all the instances of ClassA. This creates like a domino effect and keeping up with the client could pose some trouble.

Now, like the blog explains, in software development there might be some trade-offs. If the program runs better optimally with the above method, then maintenance might need to be pushed aside for just that. But it’s an important goal for the software developer to minimize dependencies, and by following guidelines provided by The Principle of Least Knowledge this becomes much easier to accomplish.

The Principle of Least knowledge is very important when it comes to coding because when it comes to programming a client itself, it becomes very easy to callback other dependencies to make things easier. But this creates more classes that, in a before blog would be referred to as “master classes” and more redundant code is created, and other dependencies are brought into the mix.

In code it seems like it’s better off if some classes don’t know the inner working of their other class, I’ve seen many programs break entirely because of one class. These classes are dependent of other classes. When one class falls all the other classes fall with it. So, It’s important to implement these dependencies so that they can be changed easily. And it’s also remembered to implement in such a way that they don’t require these chains of dependencies involved. All in all, it’s best to create a program that easy to modify and refactor so that the code is easy to work with in future development.

Link to Blog: http://www.ericfeminella.com/blog/2008/02/02/principle-of-least-knowledge/

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

Refactoring is an important concept in software development
that refers to the process of modifying and improving the internal structure of
existing code without changing its external behavior. This can be a useful
technique for improving the readability, maintainability, and performance of a
codebase, and it is often an essential part of the software development
process.

There are many reasons why a developer might choose to
refactor their code. One common reason is to improve the readability and
understandability of the code. Over time, as a codebase grows and evolves, it
can become difficult to understand and maintain. Refactoring can help to clean
up the code and make it more organized and easier to read. Another reason to
refactor code is to improve its maintainability. As a codebase grows and
changes, it can become more difficult to make updates and modifications without
introducing bugs or breaking existing functionality. Refactoring can help to
make the code more modular and flexible, which can make it easier to make
changes and updates without breaking the code. Refactoring can also be used to
improve the performance of a codebase. As code is written and optimized, it can
sometimes become inefficient or slow. Refactoring can help to identify and
remove bottlenecks, and to optimize the code for better performance.

I chose this blog post on refactoring because it is a
crucial concept in the field of computer science. As I read through the post, I
found it to be very informative and well-written. The post clearly explained
what refactoring is and described the various benefits it offers, such as
improving readability, maintainability, and performance. I found the discussion
of different techniques for refactoring code particularly interesting.
Techniques like extracting methods or functions, renaming variables and
functions, and restructuring code can all be effective ways to make code more
modular, readable, and maintainable. I also appreciated the emphasis on maintaining
the external behavior of the code during refactoring. This is something I will
keep in mind as I continue to learn software development. Although refactoring
wasn’t required in this class, I plan to use what I learned on future projects
and when working with others on a team. I will refer to this resource as I
continue to improve my skills and knowledge in the field.

Source:

https://maddevs.io/blog/code-refactoring/

From the blog Zed's Blog by Lord Zed and used with permission of the author. All other rights reserved by the author.

Refactoring is an important concept in software development
that refers to the process of modifying and improving the internal structure of
existing code without changing its external behavior. This can be a useful
technique for improving the readability, maintainability, and performance of a
codebase, and it is often an essential part of the software development
process.

There are many reasons why a developer might choose to
refactor their code. One common reason is to improve the readability and
understandability of the code. Over time, as a codebase grows and evolves, it
can become difficult to understand and maintain. Refactoring can help to clean
up the code and make it more organized and easier to read. Another reason to
refactor code is to improve its maintainability. As a codebase grows and
changes, it can become more difficult to make updates and modifications without
introducing bugs or breaking existing functionality. Refactoring can help to
make the code more modular and flexible, which can make it easier to make
changes and updates without breaking the code. Refactoring can also be used to
improve the performance of a codebase. As code is written and optimized, it can
sometimes become inefficient or slow. Refactoring can help to identify and
remove bottlenecks, and to optimize the code for better performance.

I chose this blog post on refactoring because it is a
crucial concept in the field of computer science. As I read through the post, I
found it to be very informative and well-written. The post clearly explained
what refactoring is and described the various benefits it offers, such as
improving readability, maintainability, and performance. I found the discussion
of different techniques for refactoring code particularly interesting.
Techniques like extracting methods or functions, renaming variables and
functions, and restructuring code can all be effective ways to make code more
modular, readable, and maintainable. I also appreciated the emphasis on maintaining
the external behavior of the code during refactoring. This is something I will
keep in mind as I continue to learn software development. Although refactoring
wasn’t required in this class, I plan to use what I learned on future projects
and when working with others on a team. I will refer to this resource as I
continue to improve my skills and knowledge in the field.

Source:

https://maddevs.io/blog/code-refactoring/

From the blog Zed's Blog by Lord Zed and used with permission of the author. All other rights reserved by the author.

Refactoring is an important concept in software development
that refers to the process of modifying and improving the internal structure of
existing code without changing its external behavior. This can be a useful
technique for improving the readability, maintainability, and performance of a
codebase, and it is often an essential part of the software development
process.

There are many reasons why a developer might choose to
refactor their code. One common reason is to improve the readability and
understandability of the code. Over time, as a codebase grows and evolves, it
can become difficult to understand and maintain. Refactoring can help to clean
up the code and make it more organized and easier to read. Another reason to
refactor code is to improve its maintainability. As a codebase grows and
changes, it can become more difficult to make updates and modifications without
introducing bugs or breaking existing functionality. Refactoring can help to
make the code more modular and flexible, which can make it easier to make
changes and updates without breaking the code. Refactoring can also be used to
improve the performance of a codebase. As code is written and optimized, it can
sometimes become inefficient or slow. Refactoring can help to identify and
remove bottlenecks, and to optimize the code for better performance.

I chose this blog post on refactoring because it is a
crucial concept in the field of computer science. As I read through the post, I
found it to be very informative and well-written. The post clearly explained
what refactoring is and described the various benefits it offers, such as
improving readability, maintainability, and performance. I found the discussion
of different techniques for refactoring code particularly interesting.
Techniques like extracting methods or functions, renaming variables and
functions, and restructuring code can all be effective ways to make code more
modular, readable, and maintainable. I also appreciated the emphasis on maintaining
the external behavior of the code during refactoring. This is something I will
keep in mind as I continue to learn software development. Although refactoring
wasn’t required in this class, I plan to use what I learned on future projects
and when working with others on a team. I will refer to this resource as I
continue to improve my skills and knowledge in the field.

Source:

https://maddevs.io/blog/code-refactoring/

From the blog Zed's Blog by Lord Zed and used with permission of the author. All other rights reserved by the author.