Forum section to show the code?

[beer-in-box]

Do we have a section to show our project codes for criticism?
And would anyone be interested in looking into some nasty code?

After struggling a long time with tutorials and trying to use ONLY what the tutorials cover, I decided it was a bad way to go for me and I should start an easy project and go with it.
I started the project with what I already knew how to use. Then I started to think "What else could this app use?" and started to implement them and if I had no idea, I learnt the topic. First a couple of examples with newly learnt thing, then trying to implement it to my little project... And it got to a stage where someone could use it in real life.
Of course it has many missing features, but I am trying to mean that, I can't post it to "What's Wrong With My Code" section, because it seems like it's working nice (Oops, I remembered some code which might create a bug while typing this).

So if we have a section for this, and of course you think people would like to have a look, I want to post it here (I think it has 1200 lines of code, comments included.

But it seems we don't have a section to this.

I commented every single thing I did. If I just copied and pasted the particular code snippet from somewhere, I commented "Learn how to do this on your own" and I put the link there so that I can follow if something new happens. I think I might have missed some though. I put comments on method, constructor and class beginnings and endings. Even the some obvious parts are commented. Variable names are self-explanatory at least to a non-native speaker

Apart from the project, I want to show my code to some people who are more experienced, so that they can criticize the code and therefore I can stop doing the wrong thing. There are tons of articles about how to avoid bad practices, but unless someone points at yours, I think you can't really avoid it.

I learnt a lot since I began this project, I will need some time to absorb the knowledge better and I want to correct at least some of my mistakes before learning something new. If I can do all the things in my head, I think I might have developed something I really missed some time ago.

Or, if we cannot do this here, can you tell me where this kind of stuff is done?

[Starstreak]

I have seen people add files as an attachment. 1200 lines is a lot to review, so I would highlight a particular section that you want feedback about.

[beer-in-box]

I was searching the net for this purpose and I noticed some people ask for money to look into the code.

I realize that inspecting a code which is not yours is though. I am also sure it is tougher if the code is written by a novice programming enthusiast (And enthusiast part is a whole new story, right?). Even I get irritated while reading a bad written code!

As I kept learning new things, I started to worry about my implementation more and more. And I am at a point that I think everything could have done in a more elegant and efficient way. Of course there is always a better way, but I meant my way might be really terrible and it might be just luck that it works. So I actually cannot highlight any particular code

So that's why I asked. Time is valuable for everyone. And after I found out that people review code for money, I just felt a little ignorant to post this

Also, while searching, I found some design patterns and learnt that their purpose is to avoid bad practice as much as possible. Maybe I take a look at them...