When watching a video or reading, I will summarize what I have learned with a hand written note and draw an example.
Communication skills like public speaking (demos), writing (technical pitches or design documents), and group conversation etiquette (inclusive communication) are really important. For example, it doesn’t matter how good you are at coding if you interrupt people in meetings so they don’t want to work with you.
Ask questions, research, and learn new things. This doesn't have to be entirely new things. You will improve productivity if you learn shortcuts and hotkeys for your tools. Read documentation for the things that you use.
Use version control, write unit tests, and document your code so that the next person working on it doesn't have to guess.
Build, rebuild, and break it. Don't be afraid to break something in a tutorial. Learning to fix things is important.
Do a tracer bullet first, before you start with robust functionality. Make the smallest end-to-end, full stack "Hello World" that touches everything you plan to integrate. Make sure that it works. Then start building out your functionality.
Code Connector Contributors: Walker Laury, Corey McCarty, Dennis Kennetz, George Spake, Isaac Arcos Huicochea, Steve Hallman MBA, PSM, PSPO, PAL