Been there done that. Only thing I can suggest is that you keep notes, very good notes. You start looking into the WhatchaMaCallIt.java class to fix a bug you'v

Been there done that. Only thing I can suggest is that you keep notes, very good notes. You start looking into the WhatchaMaCallIt.java class to fix a bug you've been assigned? Write down in a text editor what you think it does in human understandable sentences. Then see how it interacts with other objects in the application. Draw squiggly lines with notes on them. You get briefed by a very experienced senior developer with absolutely no time? Keep notes of what he/she is saying and try to ask questions if something doesn't make sense. Also thank them for their time, always appreciated since I'm that guy now. I remember filling up notebook after notebook at my first job out of college. I then moved on to text editors that I could keep open in a second monitor (hidden whenever coworkers came by because I was embarrassed, which was stupid in hindsight).