/prog/ - Programming

>>1560

>>1562

I only found that books bore me to tears, not everyone can learn from reading just books.

>>1559

I would just dive right in and get your hands dirty, search on google when ever you get stuck. The only way you are going to learn is by actually coding, and that might seem a bit daunting at first, but once you get going and pick up the basics, learning the advanced stuff is just a google search away while using your favourite IDE to code what every it is you have chosen.

>>1572

> And if someone answers them, they respond by "code pls".

They should toss in some back doors for fun.

Personally I don't like youtube videos, unless it's demonstrating how to use software, or a particularly extensive framework. I prefer written tutorials and books.

By all means, try videos, and stick with them if you think they help best.

>How many hours should I practice?

Try to set aside an hour every day. Depending on your workload for college, add 4 hours to some of your days off. Definitely don't go more than a week without coding while you're still learning - it's very easy to get out of practice.

>How should I learn?

le generic "do wats gud for u".

But to give you a starting point, try a tutorial and/or book. When they give you some code, play around with it. Change parts of it, and see how that changes the behavior. If it breaks the program, what kind of error does it give you? etc. I recommend books, but the important thing to remember is that you cannot learn to code purely by reading - you need to do some coding too. If you have no clue what to write, follow tutorials and try to change the code to do something a little difference once you get it working. When you understand most of the basics, set small goals - a goal should always push the limits of your current skills.

Also remember: google is your friend

searching "[language] [thing you want to do]" will generally solve all your problems. Definitely google error messages too, if you don't know what they mean. An important skill to develop is to be able to break systems down into programs, programs into processes, and processes into steps. This gets easier with practice.

>How will I know if im ready?

When you can comfortably develop a desktop application using a common industry language like Java or C# which stores data using an SQL database without closely following tutorials, you'll be better than a surprising number of applicants for junior positions.

Typical things enterprise employers are looking for:

Fluency in a mainstream language

Experience with databases (use parameterized queries when dealing with user input!)

Some SQL fluency

Experience with version control (git is a good choice)

>>1559

As soon as possible you say? 1 to 2 years. That's assuming you want to actually program and engineer solutions, not just churn out shit. Oh wait, that's all this industry does.

YouTube tuts are good in general, but if you want to use PHP, watch general tutorials but don't actually use the mysql_ in your website. Look for tuts with PDO or use mysqli_

>>1560

>2015

>reading books

>not using youtube

>>3352

can you post the actual exercises listed on pic or give a sauce?

>>3357

If i understand the image, you are supposed to code something random from the list and self evaluate.

in other words, the listed items are the exercises

>>3358

It was really originally a roll thread thing on halfchan /g/. I'm not sure what's changed since then, but it has a pretty vastly varying level of effort (02 is a single expression for each conversion). I think it's got some issues (like 07 is over a month's worth of effort at the very best, with 500 unique programming problems, not to mention lazy as fuck, because it isn't a "challenge" but a link to a list of other challenges).

>>3356

>reading text from a 1080p video

>not reading text in html or PDF.

Why?

>>3356

Hello, shitty Rockstar! Indian Java coder…

>>3357

>>3358

Yes, the items in the image are the exercises.

>>3326

>start right away

I did the same, anon, and it works, but I got a lot of nasty coding habits, which took at least a year to get out of my system. I'd at least add this to this approach: Read other project's code, not snippets people post on stackoverflow and such. Find a project you're interested in and start adding features. People won't merge your code if it's badly written, and may coach you to learn to write better. No need to get deeply involved: a few bugfixes/small improvements here and there will do just fine. Also, I don't recommend the use of an IDE when starting (and even later), since you should think for yourself how you format your code/project, and learn the different ways there are to do so. Just use a regular programming text editor. Also a good thing to learn early on is to correctly comment your code. Including myself, a lot of people fail to do so, and it'll give you a great advantage because you and others will be able to read and reuse your code five years after writing.

I think you should learn how to read pseudo code first, and study some algorithms. It will teach you basic concepts such as variables, arrays, stacks, queues, etc. It will also help you to solve problems like a programmer. If you learn how to read and write algorithms before you learn how to code, you won't conflate your design with your implementation. I know a lot of beginners that like to just sit down and start coding, but that's supposed to be the easy part after you've figured out what you wanted to write ahead of time.

You may learn an imperative language along with the pseudo code and algorithms. Don't pick an object oriented language like Java or C++. Pick something purely imperative like C. Object oriented languages add new concepts on top of imperative ones that you shouldn't conflate with each other.

Just learn some simple sorting algorithms like bubble sort and data structures like linked lists, stacks, and queues. When you're ready, you can learn about time complexity and more advanced algorithms.

>>3367

Yeah. In highschool and part of college, I'd write programs to do my math homework for me, and now I can't remember what they do. I just feed them numbers and I get new numbers. It all seems random to me. I wish I commented my code.

Fellow noob here, anon.

What classes are you taking?

What language are you interested in?

What's the end-goal of your learning? Mobile apps, web development, video games, or software?

I'm currently enrolled in a mobile applications development degree at the local technical college. If you just want to learn programming, I highly recommend going to a technical college. They teach you what employers are looking for. They're very job-focused, and less research-focused.

I was in a four year college myself, for computer science. When I realized that I wanted to be a programmer, I transferred over and I am incredibly happy with their approach. A requirement for graduating with a degree is getting an internship. The last semester is completely devoted to getting an internship. Very cool!

>>1569

>About 10 years

In normie years, faggot.

>>1559

>How many hours should I practice?

10k to achieve a mastery in any field

but you can be a pro without doing that

>>3352

is a geekcode generator that hard?

>>3874

Those "programming challenge" lists have nonsensical variations in difficulty, see >>3359

>>3381

Is there any good source of common concepts you should know? This approach feels true, but a noob don't really know what you should know. At the moment I'm stuck reading programming concept articles at wikipedia haphazardly. A list of concepts in a natural order for good understanding would do many beginners great I think, and I've never found anything when searching for it.

>>3999

Books on programming for beginners almost always cover those concepts. Basically pick whatever book is recommended for the language of your choice and it will have every critical concept in the beginning because otherwise it's impossible to progress otherwise.

I kind of get where the pseudocode guy comes from, but personally I think it's much harder to start without an actual language when you can get syntax verification and interpretation.

>Chrome and Chrome OS.

Get better tastes in software.

>Shit grammar.

Learn to speak your native language first.

>YouTube tutorials and Shitty WebPages

You couldn't make a fucking Imageboard? What, are you retarded? It's the fucking FizzBuzz of back end WebDev.

Oh, and your shit site looks awful too.

Assuming your either a straightfag or a nigger, because those are the only two groups with a low enough IQ to produce something so fucking shitty.