What python topics do I most consistently need to look up? An experiment.

A programmer's lament: Looking stuff up sucks.

I want better indexed docs. In the interest of this, I decided to do a little experiment. I wanted to figure out what, exactly, out of all the docs I looked up are important to have within reach.

What python topics do I most consistently need to look up?

I decided I would trawl my chrome history for programming-related pages.

Data

I noted in my strategic review* that I'm confused about which functions are built into python and which are class/library functions.
*(strategic reviews are when I periodically overhaul my to-do list, making a record of my successes and failures and checking in with my longer-term goals.)

•  codecs: dealing with unicode ridiculousness
• __builtin__ types
• docs: codecs
• tutorialspoint: string_decode
• modules
• init.py
• stackoverflow
• file IO
• docs: input/output
• stackoverflow: atomic file writing
• docs: io.open
• stackoverflow: readinto
• stackoverflow: writelines
• tutorialspoint: writelines
• tutorialspoint: io
• format string
• docs: formatter
• docs: strptime
• bash interactions
• bash from python
• stackoverflow: python interactive
• stackoverflow: bash shebang
• Regex
• URL parsing
• DOI parsing
• .... checking for damn validity
• .findall
• vim search
• ..vim nongreedy
• or
• docs: re
• regex101
• stackoverflow: vim nongreedy
• stackexchange: nongreedy
• stackoverflow: or
• atexit
• docs: atexit
• Exceptions
• try, catch
• error types
• docs: errors
• docs: exceptions
• tutorialspoint: exceptions
• PyCharm stuff
• adding virtualenvs
• virtualenvs
• zooming
• zooming
• highlight weirdness
• Postgres
• psycopg2
• table constraints
• character data types
• complex data types
• create table, database syntax
• install mac osx
• psycopg
• ddl constraints
• Git
• pull from other branch squash
• orphan branch
• commit release branch
• merge conflicts
• stackoverflow: push one branch
• stackoverflow: orphan branch
• merge conflicts
• previous website project
• Phone adb 
• [stackoverflow: adb pull](http://stackoverflow.com/questions/17629889/android-adb-pull-file-on-desktop_
• Datetime
• docs: datetime
• pytz
• isinstance
• json
• custom decoding
• (what's pickle anyways)
• docs: json
• atom HTML preview
• Interval data types
• markdown
• linebreaks
• markdown basics
• Javascript random
• eval()
• w3schools
• random
• stackoverflow: random selection
• javascript checker
• jsvalidate
• jslint
• getelementbyid()
• w3schools
• HTML stackoverflow: labeled checkbox
• Latex special characters
• wikibooks
• LaTeX for Anki
• install latex
• Anki
• random question generator
• LaTeX for Anki
• Anki manual: sharing decks

Conclusions

The areas I want to focus on are:

• string methods, formatting
• file input/output, incl. json
• git manipulation
• exception handling
• regex syntax
• javascript syntax
• postgres setup, syntax

Followup

Sanity Check
- Examples dominated by what I've spent time on. What have I *skipped* doing because I didn't even know where to start? noted in strategic review that I'm confused about what fns are built into python


Things I could do next:

• Create Incremental Reading cards for docs/101 tutorials on
• string methods, formatting
• file input/output, incl. json
• git manipulation
• exception handling
• regex syntax
• javascript syntax
• postgres setup, syntax

--

Was this a nice read? Does this seem like something worth performing for yourself? Take a couple seconds to comment yes or no!