Many programming guides recommend to begin scripts with the #! /usr/bin/env shebang in order to to automatically locate the necessary interpreter. For example, for a Python script you would use #! /usr/bin/env python, and then the saying goes, the script would “just work” on any machine with Python installed. The reason for this recommendation is that /usr/bin/env python will search the PATH for a program called python and execute the first one found… and that usually works fine on one’s own machine.
If you're having some old desktop or laptop, there are many lightweight Linux distros that you can install and enjoy a lag-free computing experience. These operating systems for 2018 have been optimized by their developers to reduce overall RAM and resource usage. The top-rated distros on our list are Bodhi Linux, Puppy Linux, Linux Lite, Ubuntu MATE, etc.
Learn my 10-step process of how to start a business while keeping a full-time day job, from someone who's successfully done it. What's your side business?
There's an adage which goes, "The tool does not make the artist." While this statement maybe true, it matters whether the artist has access to any free
This is a short collection of lessons learned using Colab as my main coding learning environment for the past few months. Some tricks are Colab specific, others as general Jupyter tips, and still more are filesystem related, but all have proven useful for me.
To see live versions of the charts included in this article, and the code used to create them, see my GitHub project repository here. When working with text datasets, getting a handle on the “who…