> I also tend to rely on documentation a lot. I rely heavily on resources like StackOverflow, Google, official docs and Dash.app is a godsend for offline-codin

> I also tend to rely on documentation a lot. I rely heavily on resources like StackOverflow, Google, official docs and Dash.app is a godsend for offline-coding. There are many functions (python) standard library functions that I know by name, but I never remember the call-signatures for. I am always looking things up in documentation. Things that I use all of the time are ingrained into memory through rote repetition. That said, the most important thing is knowing what exists. If you don't know that a function or method exists, then you don't know to use it. As long as you know that it exists, you can (usually) easily lookup the documentation for how to use it. > I freak out when I have to pair program with someone or when someone else is reviewing my code. I've always hated being in the driver's seat for pair programming. I always feel like I make stupid mistakes and my fingers stumbled over the keys whenever someone is looking over my shoulder (this doesn't just apply to pair programming). I much prefer to just put in my headphones, get into the zone and let the rest of the world melt away as I dive into the problem at hand. My suggestion here? Let someone else into the driver's seat for pair programming and don't be afraid to ask questions, especially if you consider the other person more skilled than yourself. If the person gets annoyed at your asking questions, then they aren't a very good mentor.