1. How do I actually make things through programming when any

talk to god, nigger

>>58850629
welcome to programming, Pajeet. Is your family hungry yet? Then better get to crossing those oceans.

1. Just keep on learning, even if you can't see the progress, it's there. eventually everything will get easy enough for you to see the results quickly. Sadly, nowadays this field is one huge mess so you'll always have to sort through piles of information in order to do your job. You'll just get much, much better at it.

2. Python is great for tasks where you don't care if something takes 0.1s or 1s. It has other disadvantages compared to Java but it's still useful in many cases and some people enjoy coding it. Java itself used to be the slower alternative but now it got better in this regard.

3. It's like asking an engineer if using a calculator while building a bridge is cheating. You'd most likely feel better knowing that the calculator is of good quality and you'd want the engineer to know how to do all the calculations by hand and occasionally check for errors. He doesn't need to know exactly how the calculator works, but he has to realise when it fails. You still want bridges to be built relatively quickly and on the budget, though.

Not sure about the analogy but you get me, right?

>>58850629
>it's like jumping in to an ocean
how vast do you think this subject is?

>>58850629
1) Find something that piques your interest.

2) If it's too hard or abstract, break the goal into smaller concrete subgoals.

3) Use a planning/time management system. You don't need to get everything done in one day. Little by little, not through brute force, will you reach the goal.

4) Don't reinvent the wheel! Use a library, unless you want to learn how things work under the hood. Or if you are determined your approach is better.

5) Actually finish the project.
6) Goto 1.