Frequently Asked Questions

Question

So, after looking through the discussion page for a bit, I've seen a lot of questions that are frequently asked. I don't know how many people are going to see this, but if you plan on asking a question, here are some questions I already have answers to:

Q: Where can I start programming?
A: Well, that's what this site is here for. You can start here, and after you get some basic programming skills, test them out in the Code Playground. Don't limit yourself to just this site, though. There are plenty of sites out there for programming newbies to learn the tricks of the trade, and this is just one of them.

Q: What programming language should I start with?
A: There's really no easy way to answer a question like that. The short answer is to just try one. Python is a bit easier to learn than others because it's simple, concise, and easy to read. Languages like C++, Java, and C# are harder to learn, but they are based off of C, which is basically the grand-daddy of all programming languages. If you learn how to write code in C++, learning to write code in Java and C# is a snap. If websites and web applications appeal to you, try HTML first, then CSS and JavaScript. It really depends on what you want to do. To summarize, if you want to write applications from the ground up, start with Python and learn C++, Java, etc., and if you want to write webpages, start with HTML and work your way up to CSS, JavaScript, and maybe PHP and SQL.

Q: Can someone give me the code for (insert program idea)?
A: Well, someone could, but it would be for the better if you didn't ask someone to just give you the solution to your idea. That isn't what coding is about. Coding is about problem solving, and getting someone else to solve the problem for you negates the purpose. Some hints and tips might help you learn a few things about programming, but try to figure it out on your own. If something stumps you, ask about it, but asking for the code itself won't help you learn unless you really take the time to analyze it.

Answer 1

well

Answer 2

i disagree with your answer to #2. the programming language desicion should be based on a bit more research than "try and see what you like" since that's how you half-learn something easily before giving it up and move on to another project.

imo best thing to do when regarding what language you want is to ask yourself certain questions:

what will i be using my programming for?

in the same way you can't use microsoft word to paint a pretty picture, you can't use certain languages to program certain things effectively. for example, you wouldn't use php to create a 3d client-based vr game.

(if you decide you want to make a game) what engine would best suit my needs for the game i want to design?

certain games require you to use certain languages. for example, unity engine requires c# or javascript to program their scripts. I've heard you can also use a variant of python there, but nobody really does it so eh.

(if not a game) what level of programming will i be doing?

according to most programmers, there's a sort of heigherarchy to programming. something like:

basic applications(word, paint, etc.) < games < engines, software, and website design < operating systems, mainframe architecture, IT

now my list might be different from other people's, but the idea is more programming time will go into certain things than in others, which means you'll want to factor the efficiency of the language you want more and more depending on how much you plan to do regularly.

the tl;dr is basically find out what your specific goals are, then find what language would be both versatile and efficient enough to help you reach your goals based on research and testimonials, THEN pick your language.