You should be forced to write efficient code and know how to do it in situations where it matters. You should also be able to recognize when it’s more important to optimize for readability, maintainability and clarity.
If you haven’t figured out how to get the most out of what you already have, don’t ask me for more RAM/disk/CPU or anything else. Buy a Pi Zero and use it’s limitations to force yourself to write tight code.
It’s possible to simplify the “normal” things for normal users while still providing source code and repositories that allow us strange creatures to continue experimenting, testing, and yes, struggling with inevitable incompatibilities all night long.
I’ve been curating my social media, as I do at the end of every year. By “curating” I mostly mean “deleting annoying rants” but also a whole lot of stuff that was timely when posted but irrelevant a week later. As I re-read things, some of them stand out, and are worth calling attention to.
I was asked to join the team running the National Transportation Data Challenge, not as a data scientist, but as a project manager to help keep all the big data people on track and moving forward. It’s an interesting use of my skillset and after a slow start I’ve been devoting more and more of my time to it. After lots of work behind the scenes, we showcased the Challenge to a more general public last week at JupyterCon in New York.