I've seen plenty of "entry-level" jobs that list 20 things they would like you to know and I apply even if I don't even know what they stand for.... however, I take a look and keep a list of terms or acronyms so at least I know what they are about and maybe add them to my to-do list of things to get familiar with down the road or at least know about before the interview... if I see one term or acronym that keeps popping up, I consider exploring deeper in the near future... but there are plenty so I probably will never get to most... the day only has 24 hours and I have to sleep a third of that time!!!
Don't be afraid to tell an interviewer that you do not have skills in a particular area - honesty is usually the best policy. As per this video the things they would like you to know in the entry level position are probably desirable, but not necessarily essential. The reality is that an entry level position does not usually need a lot of skills and if it does, it may be the wrong job for you to take.
The Learn Programming Channel I agree with you. I would never claim to have a skill that I don’t have, but it helps to know what they are about and get familiar at least with the terminology.
Tim, I’m taking your Java course and it has been a pleasure. This video alone makes it worth it. In graduate in a little over a month and this is the exact issue I was having when looking for jobs. Even some internships wanted years of coding experience. This video answered all the questions I had about job posts that didn’t make sense. Cheers, Daniel
Don't forget jobs that have requirements like (just thinking up an example, but they do exist): "10 years of Kotlin experience required!" (Kotlin came out 2011)
Hey Tim! I really enjoy your course on Udemy about Java, I learn a lot! But, I have a question, maybe you can cover this on one of your videos: What should a portfolio contain for a first Junior Java job? Should have 1, 2, 3 apps? How complex should they be? Does it matter ? Best regards!
I think the more the better. But looks for substantial apps - e.g. It's better to have one app that has some good functionality rather than 3 "hello world" style apps. Technically one app would be enough to demonstrate your skill.
Here's what I do I look stack of requirements in my area. See if I already know them if not look into what they are. Their list demands is great learning tool for what to learn next.
It only seems realistic to get your foot in the door if you have at least a couple of projects you completed on your own. A software portfolio. Plus whatever your prefered language is, like Python for example, you have to know the syntax like the back of your hand. To do that, you have to code like, all the time. I struggle with writing software, because I have no idea what I would like to make. Investing in a project takes a lot of time, and I can't seem to be inspired by anything. I like finance, so I am going through some Python finance courses (FinTech.) But I don't know I can't seem to get inspired. The only thing that I really like is Jet Fighter Sim development, but that is a black art. You can't really learn how to do that, and it's C++, which is really hard for most people. C++ is my favorite language, but it is so difficult and game centric, I can't stick with it. Python, C#, Java, they seem realistic to get a job with. But C++ is...basically not in my opinion. Unless you are gifted at coding, love it and do it all the time, then maybe C++ could be an option. It is not recommended though. Oh and the last thing is; Framworks. You have to be really familiar with Frameworks and how the functions work. But there are so many of them and so many functions. Syntax is one thing, but Frameworks is extremely important. You don't want to be reinventing the wheel. Question is, which Frameworks should I get really good with? Depends on what you like doing, like Desktop App, Web, Databases, it is a whole big can of worms. And if you want to go Full Stack then you have to know all of them. So, it all comes down to your ambition. Code everyday all day, don't give up and don't stop. If you do you will just forget all of it. Coding is one of those disciplines, that requires you to do it all the time. For average people anyway. I code sometimes then I stop, it is on and off, so I get nowhere.
yes the textbook definition of essential is that. What he's referring to is that in a workplace, these "essential" skills are not actually absolutely necessary, but would be better if you know them.
Hi Tim, I have a question for you please: I am okay when programming with one class. When writing a programme that requires many objects communicating with each other, I get very confused. In most of the courses(video) as well as text books it is found that most of the examples cover scenarios with one class. How can I get better at writing code where multiple classes communicate with each other? Are those concepts covered in higher level course or are they covered in design pattern course?
Watch Tim's Free Learn to Code Course on UA-cam!
ua-cam.com/play/PLXtTjtWmQhg0N08o_oSaAantmQAu-1Xad.html
I've seen plenty of "entry-level" jobs that list 20 things they would like you to know and I apply even if I don't even know what they stand for.... however, I take a look and keep a list of terms or acronyms so at least I know what they are about and maybe add them to my to-do list of things to get familiar with down the road or at least know about before the interview... if I see one term or acronym that keeps popping up, I consider exploring deeper in the near future... but there are plenty so I probably will never get to most... the day only has 24 hours and I have to sleep a third of that time!!!
Don't be afraid to tell an interviewer that you do not have skills in a particular area - honesty is usually the best policy. As per this video the things they would like you to know in the entry level position are probably desirable, but not necessarily essential. The reality is that an entry level position does not usually need a lot of skills and if it does, it may be the wrong job for you to take.
The Learn Programming Channel I agree with you. I would never claim to have a skill that I don’t have, but it helps to know what they are about and get familiar at least with the terminology.
Yes that is true - knowing what something is even if you are not skilled is better than not knowing of it at all.
Tim, I’m taking your Java course and it has been a pleasure. This video alone makes it worth it. In graduate in a little over a month and this is the exact issue I was having when looking for jobs. Even some internships wanted years of coding experience. This video answered all the questions I had about job posts that didn’t make sense.
Cheers,
Daniel
Don't forget jobs that have requirements like (just thinking up an example, but they do exist): "10 years of Kotlin experience required!"
(Kotlin came out 2011)
ha ha, yes - you know a non programmer has got involved when they start adding things like that!
I swear I saw a job advertisement that asked for 5 more years of experience in Swift than it has even existed for!
Thank you this gave me a lot of confidence.
Few would give such risky but truly helpful and valuable advice as you do.
Tim is a logic person.... he is the best instructor ever
Thanks for the support!
Hey Tim! I really enjoy your course on Udemy about Java, I learn a lot!
But, I have a question, maybe you can cover this on one of your videos:
What should a portfolio contain for a first Junior Java job? Should have 1, 2, 3 apps? How complex should they be? Does it matter ?
Best regards!
I think the more the better. But looks for substantial apps - e.g. It's better to have one app that has some good functionality rather than 3 "hello world" style apps. Technically one app would be enough to demonstrate your skill.
Came here for this question and answer. Thanks!
Here's what I do I look stack of requirements in my area. See if I already know them if not look into what they are. Their list demands is great learning tool for what to learn next.
So happy that I am getting a professional's direct interaction.
It only seems realistic to get your foot in the door if you have at least a couple of projects you completed on your own. A software portfolio. Plus whatever your prefered language is, like Python for example, you have to know the syntax like the back of your hand. To do that, you have to code like, all the time. I struggle with writing software, because I have no idea what I would like to make. Investing in a project takes a lot of time, and I can't seem to be inspired by anything. I like finance, so I am going through some Python finance courses (FinTech.) But I don't know I can't seem to get inspired. The only thing that I really like is Jet Fighter Sim development, but that is a black art. You can't really learn how to do that, and it's C++, which is really hard for most people. C++ is my favorite language, but it is so difficult and game centric, I can't stick with it. Python, C#, Java, they seem realistic to get a job with. But C++ is...basically not in my opinion. Unless you are gifted at coding, love it and do it all the time, then maybe C++ could be an option. It is not recommended though.
Oh and the last thing is; Framworks. You have to be really familiar with Frameworks and how the functions work. But there are so many of them and so many functions. Syntax is one thing, but Frameworks is extremely important. You don't want to be reinventing the wheel. Question is, which Frameworks should I get really good with? Depends on what you like doing, like Desktop App, Web, Databases, it is a whole big can of worms. And if you want to go Full Stack then you have to know all of them. So, it all comes down to your ambition. Code everyday all day, don't give up and don't stop. If you do you will just forget all of it. Coding is one of those disciplines, that requires you to do it all the time. For average people anyway. I code sometimes then I stop, it is on and off, so I get nowhere.
Is it necessary to have a college degree in order to land an IT job?
The definition of “essential” is ‘absolutely necessary’
yes the textbook definition of essential is that. What he's referring to is that in a workplace, these "essential" skills are not actually absolutely necessary, but would be better if you know them.
Hi Tim, I have a question for you please: I am okay when programming with one class. When writing a programme that requires many objects communicating with each other, I get very confused. In most of the courses(video) as well as text books it is found that most of the examples cover scenarios with one class. How can I get better at writing code where multiple classes communicate with each other? Are those concepts covered in higher level course or are they covered in design pattern course?
where's your office at Tim ? , love the nice view behind you !
Likely either a green screen or a matte background
Yep green screen!
You're a mind reader!
Awesome! :)