Profile the code. Once you understand where the time is spent, its probably the main loop of the program or atleast will give you a clue to the main function. O

Profile the code. Once you understand where the time is spent, its probably the main loop of the program or atleast will give you a clue to the main function. Ofcourse you can ask someone or read the docs, but profiling it has the added advantage of giving you the map of implementation to the intended algorithm. Further when you profile you can get a call graph nicely drawn out using many utils available online. This instantly gives you a big picture. I also second stepping in, adding feature, fixing a bug etc.