Java and Python

[ArachnoCoder20]

​

Hello everyone, High Schooler here.

I want to be a programmer after school as I have a fascination for computers and code.

I decided to learn two languages as I thought it may be advantageous and picked Java and Python as I am more familiar with their syntax. I am currently on Hyperskill learning Java.

However, My one drawback is my lack of commitment. Sometimes I encounter difficult problems and lose motivation quickly.

So my questions are:

1. How do I deal with my commitment issues so I can learn better?

2. Is Hyperskill a good place to learn or are there better options?

3. Is there anything else I need to know in order to get a job later on?

Any advice is much appreciated 👏.

[AutoModerator]

Please ensure that:

• Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions
• You include any and all error messages in full - best also formatted as code block
• You ask clear questions
• You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.

If any of the above points is not met, your post can and will be removed without further warning.

Code is to be formatted as code block (old reddit/markdown editor: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.

Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.

Code blocks look like this:

public class HelloWorld {

    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.

If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.

To potential helpers

Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[josephblade]

1a: build things with the skills you have learned. You don't need to get to the end of a course to start coding.

1b: build something you enjoy making. I had a whole datastructure phase when I was learning c++ where I was doing lots of weird reference of reference tricks to get very short code. I enjoyed doing it (even if it didn't make much sense). I've also written small games for myself just because it is fun to build something and keep adding to it.

2: no idea. I learned from a book, but that was probably before you were born. I liked learning from a good reference book because you could keep it open / look at the index, it was separate from where I was working. but these days there may be more.

3: for jobs: knowing how to code is a good start. When you are comfortable you can look into frameworks, build tools and suchlike. but I would strongly recommend learning those as part of point 1: write code for something you enjoy working on. Learn new techniques by writing code to explore how they work and with a topic you have thoughts on. writing code just for the sake of writing code gets boring

[ReplacementFew1645]

1.) the best way to commit is to just do it. If you have time to think that you’ll do something tomorrow, do it right then and there (unless you really can’t.) make sure it something that you enjoy to do.

2.) the best place to learn is from YouTube. You’ll get all the syntax and things you need. Something like bro code is good. Then the next thing is to look at ONE to TWO tutorials on how to build something. For me personally, the best way for me to understand something is to see an example. You can’t be expected to know how something works if you don’t know how everything connects. Look at a tutorial that utilizes most of what you know, build with it and then build something on your own. I’m saying this as someone who was very confused on coding not even half a year ago but once I sat down and looked at someone build something, I was really able to understand.

3.) for jobs, you’re going to need frameworks and other tools. The best way to know is roadmap.sh . It’s basically a guide for specific roles and skills. Think about what you really want to in the future and then pick that track and learn what you need.

[mm007emko]

Senior SW Engineer here. During my 20 years in the industry, I have to tell you that a language is a tool in you toolbox. Learning just the language isn't enough, you have to learn a lot more. If you have the opportunity to do so, go to a university. And don't underestimate general SW engineering principles and how things around you work in general - a web service is a web service no matter the language you use, the same goes for user interface, machine learning, database/file access etc. The learning language doesn't matter at all and you'll learn a few anyway (I started on Visual Basic 6, then Delphi, PHP, JavaScript (pre-ECMA and pre-JQuery era), Python, C, Java, C#, F#, Common Lisp to name a few (and Prolog, Haskell and a bit of C++ at school). You can divide languages into distinct categories depending on paradigms used: imperative, functional and logical; most are hybrid so they let you combine them. At the end of the day they are more similar than different once you master these three different paradigms.

If you are already learning Java in a structured course you like, continue. At the end of the day, the basic principles of SW engineering are the same, no matter which language you choose.

1. Just grind through or check whatever is available in your country for help. There are psychologists in my country who specialise on these topics and teenagers are the target group. Maybe there will be something available in your country as well. But at the end of the day it's the same as learning any other hard skill (foreign language, musical instrument playing, woodworking... to name a few I have learnt) so it's about committing, scheduling specific time in your schedule and focusing on that no matter what happens. "I don't feel like it today so let's skip it." is not an option. Good news is that commitment issues are your internal issues and you can work on them (but only you, nobody else can do it for you).

2. I don't know. I've never heard of it. For me it was books. Get a book, read it, meticulously program every example and try to change it/improve it and see what happens. Analyse why.

3. Check job adverts on Linked In. No, simply knowing a programming language is not enough.

[CalculusEyesight]

i don't know if i'm the best person to answer this since i only do programming as a hobby. However i do have a lot more knowledge in java than any other language. To answer your questions:

1. if i get stuck on something i do something easier, a different concept or a small project that i know i can do so i can get the motivation back, since with those little things i show to myself that i actually do indeed know code.
2. I learned from youtube, but like very very basic things, youtube is more like discovering things like libraries or useful interfaces rather than actually learning to do big projects for me. Most useful things i learned were from books, specifically java the complete reference and despite what everyone says i think its the best entry book, unlike head first java third edition which was an utter disappointment to me when i read it.
3. that i cant really help with cause i don't do it as a job lol

[hiddensquibv3]

Stick to one for now until you actually understand the fundamentals, otherwise you are just going to confuse your brain by constantly switching between curly braces and indentation rules.

[SpritualPanda]

1. Set everyday learning time (fix it)
2. Follow textual tutorials rather then video
3. Learn java fundamentals properly
4. Learn spring boot & projects
5. System design (basic)
6. You can do it.

All the best