In all reality, the code you write will most likely result in more attack vectors than any backdoors. Go with .NET core ... It is open source and can be inspected for such things.

In such a way that it fixes itself when a bug is encountered.

As someone who has done hiring of devs for years, I'd recommend a brute-force approach: Get out there and see what is needed.

What I mean: There are companies that offer Junior-level positions. Go and interview. Get your resume together, be honest about where you are coming from, what you've learned, etc. Even if you are under qualified for the position, use the experience to learn where you need to go. Examples of questions to ask the person interviewing you (if you feel that you aren't going to make the cut):

• What areas could I improve to have been a competitive candidate? (Determine the gap of where you are to where you need to be)
• What areas specifically do you want to see experience in? (Help determine what you should study next)
• Do you offer an internship program? (Willing to work for free to get the experience needed?)
• Do you know of other opportunities in the area that I could contribute to to gain experience?

Best of luck.

I would state: Learning concepts makes you a better programmer. Once you understand concepts, you can pick up any language relatively quickly.

That makes sense. This one example doesn't in any way detract from the awesome work you've done. How long was this in the making?

Wow! The program looks amazing! I tried using it with the opening piano lick to "Feelin' Alright" by Joe Cocker, and the result was, well, nothing like the song. :( There are bongo drums and another percussion instruments at the beginning that may be throwing it off... Here is a link to a small OGG file I used to test it with. I'd love to get your feedback.

Oh gawd. Just wait until he "discovers" .NET

Nowhere. As soon as you start checking a client's IP Address against a list, you are crippling your application's ability to scale as well as incur a performance hit on every connection.

Move this to a router/firewall.

As someone who just had to learn Git (coming from a Team Foundation Server background), there are aspects of Git that are Gitarded. But then, all the fanboys in my office call me gitarded: "It really is quite simple ...". Bullshit. As soon as I have to start interactively rebasing my code, all trust in the system goes out the window.

When I perform "technical" interviews, I'll pose an architectural problem as if they were a team member, and then collaborate with them to a workable solution. I'll see if they are able to see the up-sides and down-sides of the solution. If we jive, and they have great input, then they are a go in my book. I don't care if they know how many dildos there are in the world. Or if they have every nook and cranny of a particular language memorized.

Python, all the way. I'm a .NET developer, and despise Java for the few times I've had to use it.

Well, that is retarded.