Skip to content

Week 7 Reflection #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AshKitturGitHub wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Week 7 Reflection #116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions week7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
https://towardsdatascience.com/full-stack-visualizations-for-complex-solutions-for-data-scientists-5afc488f60d

While my previous reflection focused on examining the principles of data visualization within the context of front-end development, this article delves into the
implications of a full-stack approach to software engineering. I think that it is interesting that the visualization capabilities for backend projects is much more
complex than front-end, allowing techniques such as GIS mapping, for example. They also show the vast library of visualization tools that Python is able to interface
with, such as Matplotlib, and compatibility with libraries in R, for example. Furthermore, the authors of the article show how using Flask within Python is primarily
utilized with an object-oriented programming approach. Overall, my general impression is that there are different implications on the output of data visualization
techniques depending on the scope of the project.