Accelerate Your Creativity with Automation

If you want to have more brain cycles for fun, creative stuff, you can automate the boring stuff.
Though you can't really call it a "cognitive assistant", it will definitely help you think better.
Automating the boring stuff was the secret to the rise of powerhouse startups like GitHub, GitLab, Puppet, and even Google (in the early days).
Wildly efficient companies can generate millions in profit per employee.
Companies that don't get it find themselves stuggling to exceed 100k of revenue per employee.

If you automate the drudgery, you will free up brain cycles for fun, creative stuff... like finding more things to automate.

At Tangible AI, our simplest, most popular automation has been the workon command. John, Olesya, and I use it a lot nearly every day as we switch back and forth between projects.
And we share it with our interns as part of the onboarding process.

Teaser: I've added a mind hack at the end of the post. It works well with the workon command to rev up your creativity.


The virtualenvwrapper python package includes a command called workon.
And others have created a package called, appropriately Workon

But I use conda rather than virtualenv to organize my python environments.
So I wrote a hacky shell script to take care of this.

John and I are working on a python version of this.
But don't hold your breath...
If it ain't broke, we probably won't fix it.

Use case

Every time I open a new terminal, I find myself activating an environment and then switching to that directory.
Remembering the right environment name and directory path can be a problem.
I work on many different projects in a given day, and they change from day to day.

So I created a workon command that makes it easy for me to set up a project and come back to it later.
All workon does is find the paths to my conda environmnt and source code, for a particular project.
It offloads my brain from memorizing paths and names and spellings that aren't helping me be creative.
Plus it gets me started quickly.

Now all I do is say workon qary and I'm off and running.


Download the bash shell script.


I put mine in my personal ~/bin/ directory where I keep all my automation scripts.
Then make sure that script is sourced as part of your bash login in .bashrc or .bash_profile:

mv ~/bin/
chmod +x
echo "source ~/bin/" >> ~/.bashrc

You may want to edit the script on line 38 to add paths where you keep your source code.
You might also want to add a git status command (or anything else you do a lot) below line 55.

That should do it!

Now, when you type workon qary it will get you all set up for some creative, productive coding on a chatbot to save the world!

Mind hack

Sometimes when you workon qary you end up staring at a blank screen or IDE.
It's hard to know where to start.
But if you do git status right after workon this highlights in green any files you've modified but not commited.
Then, if you remember to leave an "easter egg" before you switch to another project or shutdown for the day, that'll pop up at the beginning of your next session.
Right before I switch to a new project I'll add a TODO comment to my code, or even start a new line of code within incomplete syntax as a note to self.
Make sure you don't commit this reminder until you're in the zone and coding up some new automation to save the world.

Smart authors like Grant Ingersol often use this trick to seed their brain with creative ideas and avoid writer's block.
A writer will finish the day with an unfinished sentence or the first line of a dialog.
It's like a note to your future self.
This can supercharge your creativity the next morning by reminding you where you left off.

So when I'm about to switch projects I'll add an unfinished line of code or TODO, but won't git commit it.
That way it shows up when I do git status.
If your past self forgot to do this, and git status is empty, you can just do a git log --stat to reorient yourself.
And if that still doesn't work, sometimes when you build your project, your linters will flag any broken lines of code from the previous session.


You lint don't you?!!!
If not, I'll set you straight in a follow-up post.
Linters are a crucial bit of automation that all the strong developers I know of lean on heavily.
Thank you Steven and Aleck for indoctrinating me with this habit all those years ago.
PEP8 linting is mandatory for all interns and contractors at Tangible AI, as well as contributors to qary.

Leave a Comment

Your email address will not be published. Required fields are marked *