Brought to you by Linode - Build your next big idea @ linode.com

Episode #201: Choosing JupyterHub and Python over MATLAB

Published Wed, Feb 27, 2019, recorded Wed, Jan 23, 2019.


The Nobel prize in economics recently went to Paul Romer, a convert from proprietary software like Matlab over to Python and the SciPy stack. Paul said, “The more I learn about proprietary software, the more I worry that objective truth might perish from the earth.”

That's quite the statement. But what if your organization is deeply committed to proprietary software such as Matlab? Don't despair because Peter Kazarinoff, a professor at Portland Community College is here to share his experience converting his courses over to Python and JupyterHub.

Links from the show

Peter on Twitter: @pkazarinoff
Portland Community College: pcc.edu
JupyterHub: jupyterhub.readthedocs.io

Peter’s Book: Problem Solving with Python: problemsolvingwithpython.com
Problem Solving with Python [Amazon]: amazon.com
Peter’s Blog: pythonforundergradengineers.com
Peter’s MkDocs site showing JupyterHub deployment for a college class: professorkazarinoff.github.io
GitHub repo for Portland Community College’s engineering programming course: github.com

nb git puller: github.com

This year’s Nobel Prize in economics was awarded to a Python convert: qz.com

Peter Kazarinoff
Peter Kazarinoff
Peter teaches Engineering at Portland Community College in Portland, OR. Teaching at a community college is his dream job. He is the author of the book Problem Solving with Python. Peter wants to reduce textbook costs for students with open education resources. He is working towards reducing software costs for students by incorporating open source software into Engineering courses. Peter lives with his wife and two young daughters in Portland.
Click to show comments


Individuals: Support this podcast via Patreon or one-time via Square Cash or . Corporate sponsorship opportunities available here.
X
Become a friend of the show
Stay in the know and get a chance to win our contests.
See our privacy statement about email communications.