Forgetting what you did two weeks ago is a good thing, it gives you a fresh set of eyes and a more objective view of your own code. If you document the main poi

Forgetting what you did two weeks ago is a good thing, it gives you a fresh set of eyes and a more objective view of your own code. If you document the main points of the software while you are writing it then that will save you some agony later on. Regarding technical interviews, the only thing you can do is pick a few examples that you want to retain and regurgitate as needed. If the interview is getting too focused on implementation details then it may be that they are trying to find a reason to not hire you and they will likely never be satisfied. If you find yourself in that situation again then I recommend slowing the pace of your answers way down so that you have time to think.