Our Clarusway curriculum takes a cumulative path through the Python ecosystem, as we were discussing yesterday as we entered recap and review mode. We are still in that mode today.
This sessions continues our recap started in a previous session and draws upon everything we have learned so far.
We started in DAwPy (Data Analysis with Python) by introducing numpy and rolling forward through pandas to where we were rubbing up against:
In DVwPy (Data Visualization with Python) we explored:
The transition from Seaborn to plotly, introduced yesterday, was not intended to impart all of plotly in a single day, after taking three days sailing in the Seaborn sea.
Plotly Express is as high level as Seaborn, but then plotly is able to work at a lower more detailed level, akin to how we use matplotlib.
However, we saw the leverage we now have as data analysts familiar with Seaborn, to apply the same concepts, such as the visualization types (violin, boxplot, swarm), across platforms. Our ability to ascend this new learning curve may indeed have increased, thanks to the transferrability of the ideas.
Here's a screenshot of an exhibit we arrived at yesterday, plotting Power Plants around the world on an orthographic projection, with embedded tools such as zoom and pan.
The skillsets we have been most developing in the foreground encompass:
Secondarily, we have been reviewing the relevance of:
Github and Your Online Portfolio
You're free to clone the content of public repos, perhaps after installing Git for Windows. We went through demonstrations of cloning:
You're also free to create your own free public repos and start populating them with your own public content.
What blend of skills would you like to showcase?
In what formats would you like to demonstrate your expertise. May we suggest the Jupyter Notebook (ipynb files).
Background:
Since the open source revolution, many enterprises have gravitated to a base layer of communally shared products and projects, such as Python and SQL Alchemy, on top of which a proprietary non-public layer is added.
Sometimes the non-public value added is not only source code, but also data. Even with a communally shared ecosystem, there's still plenty of room for private enterprising.
PayPal calls it "InnerSource": using open source tools and workflows in a proprietary environment. This is how many and probably most internet enterprises are constituted: using a combination of open and closed tools.
As a result of these developments, those of us wishing to join these enterprises have an opportunity to learn some of their tools (the open source ones) without investing in expensive license agreements or taking on the overhead of private ownership.
Finally, we have been learning about: