You'll get better answers if you post code that's runnable. Code that's runnable can be tested for bugs, timed for performance, stepped through in the debugger, and so on. For example, this detailed performance analysis and refactoring would not have been possible if the code had not been runnable.

If there's a graphical or other form of user interface, things stand out when interacting with the program that would be much harder to spot from the source code alone. For example, when reviewing this game I'd probably never have noticed that the jewels were falling upwards just from reading the source, but it was obvious as soon as I ran the game.

Even if you only want to post a small portion of your program, it's still well worth making the effort to reduce dependencies, provide stubs, or otherwise adjust the code so that it is easily runnable.

You'll get better answers if you post code that's runnable. Code that's runnable can be tested for bugs, timed for performance, stepped through in the debugger, and so on. For example, this detailed performance analysis and refactoring would not have been possible if the code had not been runnable.

If there's a graphical or other form of user interface, things stand out when interacting with the program that would be much harder to spot from the source code alone. For example, when reviewing this game I'd probably never have noticed that the jewels were falling upwards just from reading the source, but it was obvious as soon as I ran the game.

Even if you only want to post a small portion of your program, it's still well worth making the effort to reduce dependencies, provide stubs, or otherwise adjust the code so that it is easily runnable.

You'll get better answers if you post code that's runnable. Code that's runnable can be tested for bugs, timed for performance, stepped through in the debugger, and so on. If there's a graphical or other form of user interface, things stand out when interacting with the program that would be much harder to spot from the source code alone.

  For example, this detailed performance analysis and refactoring would not have been possible if the code had not been runnable.

Even if you can only post a small portion of your program (for example, just one class), it's well worth making the effort to reduce dependencies, provide stubs, or otherwise adjust the code so that it is easily runnable.

You'll get better answers if you post code that's runnable. Code that's runnable can be tested for bugs, timed for performance, stepped through in the debugger, and so on. For example, this detailed performance analysis and refactoring would not have been possible if the code had not been runnable.

If there's a graphical or other form of user interface, things stand out when interacting with the program that would be much harder to spot from the source code alone. For example, when reviewing this game I'd probably never have noticed that the jewels were falling upwards just from reading the source, but it was obvious as soon as I ran the game.

Even if you only want to post a small portion of your program, it's still well worth making the effort to reduce dependencies, provide stubs, or otherwise adjust the code so that it is easily runnable.