OK, so congratulations on finishing this course, and thank you very much for choosing this course.
I know you have a lot of courses, especially a lot of programming courses to choose Udemy.
There's a lot of great content offered, so I am very thankful that you chose this course and I really
hope that you enjoyed it.
This bonus section here is meant to be a place where if any students comment on material that they thought
was missing or things that could be added in general, I could maybe add them to this bonus section
like some bonus lectures.
This lecture in specific was meant to just provide some take it or leave it kind of style advice on
the next steps that you could take after completing this course.
There's probably a wide demographic of people that might take this course, so not everything will necessarily
apply to you.
But nevertheless, I want to mention some things just because it's better to have it there than not
to have it at all, right?
So they there might be some people with some questions about what they should do now.
What are the next steps?
So it really depends on what your programming goals are.
Is this just a hobby?
Did you take this just because you wanted to learn how to program and you just picked one because you
like the way it looked?
Are you looking to start a career as a software engineer?
That's a big one.
Are you interested in becoming a web developer?
More specifically, are you interested in front end or back end or full stack front end being like you
want to change, like be in charge of the way that the website looks, right?
Not in charge, but you're going to write some code that will change how the website looks and how users
interact with it, right?
So you'll be dealing with the interactivity back in.
You'll kind of be dealing with a database and business logic on like server side and stuff like that.
Full stack is everything right?
You might be interested in everything you want to do, the front and back in and connect them and all
that.
So that's a possibility.
Maybe you're interested in C++ as a language and you took this course because you wanted to learn about
C++ and you also learned about some data structures.
But your main focus was being able to do stuff in C++ and you want to continue on in C++.
So for each of these, I like to give my answer, which like disclaimer is just my opinion.
A lot of people might disagree with my opinion, but everyone's entitled to their opinion so you can
take it or leave it.
If you don't agree with it, that's fine.
If you do, then I hope that it can help you in some way.
Some people may already be developers, and they took this course and I, they already know this stuff.
So this might be kind of redundant information, but I assume a lot of people will be beginners because
we tried to make the entry level the bar really low for this course.
You started zero, basically.
So I would like to offer some advice for those people who don't know what to do to take the next steps.
Maybe they're not in a university, or maybe they are, and they they're still not sure how to get into
these jobs.
So, yeah, I would like to kind of answer some of these for those people.
So let's look at number one, this is just a hobby for you.
So once again, congratulations on taking this.
This is a big course for just, you know, you casually wanting to program.
So I think that's great that you finished it.
I would say this is a hobby and it's not a career for youth and just go build something cool with your
new knowledge.
A C++ there might be some more stuff for you to learn if you want to make something graphical.
It's a great language for desktop applications.
So one of the coolest frameworks for that is Kuti, the letter Q in the letter T. There's a lot of great
material out there, and I think I've seen some really quality Udemy courses on it.
If you want to take a course on that, that will show you how to make graphical applications and the
stuff that you've just learned is like, kind of a really great base to get into that other, more advanced
stuff in making graphical applications because you'll be able to do all the logic now and create classes
and you know, and see it plus plus and data structures and all that stuff.
So I would recommend that if you're interested in making a cool graphical application just for fun,
that could be cool.
Also, Game C++ is huge for gaming.
If you want to make a game and use C++, I will say this on another slide.
I'll talk about this too, but I would recommend, I think, Unreal Engine uses C++, so that could
be a good gaming engine for you to make a gaming.
Number two, you're interested in becoming a software engineer, so if you want to work as a software
engineer and especially Fang Fang is, if you don't know what that acronym is, it's kind of like Facebook,
Amazon, Netflix, Google.
I would recommend that you do a few things to prepare for this.
The next thing you should probably do is learn in another language you shouldn't just have one language
under your belt.
A lot of the skills that you've learned in this course will be easily transferable to another language.
You'll understand the tools of programming languages.
You just need to learn the syntax for that language.
A dynamic language would be great.
So like Python, I like Python, JavaScript, Ruby, things like that.
Those might be good languages, too to use that use kind of different typing system.
And, you know, Python being a interpreted language, it could be cool to look into that, for example.
Another important thing that we didn't cover in this course that I would like to offer material on.
So if anyone has thinks that this should really be part of this course, maybe leave some feedback and
I can try and put together a crash course on this.
But I'm talking about version control, so let get.
If you've ever heard of Git and let Git Hub, GitHub is like a place to dump your code, but the way
to like, interact with the code and keep track of versions of your code and keep it safe is to use
a technology called Get.
Get is basically a way to like how people actually work on code together.
So if you're trying to collaborate with people and make small, everyone is making small changes to
the same program.
It's important that you keep track of all the different versions of the program that like existed so
you can go back and fix something if you mess something up or make sure that everything works and runs
and won't just destroy the whole application before people combine the code get is like huge.
Everyone needs to use version control.
If you're a serious programmer says you need to learn, get absolutely need to or some type of version
control.
I know there's some other ones that you can learn as well, so you can just look that up.
But Get is very popular, so I definitely recommend doing that.
And then algorithms, algorithms, algorithms are huge.
The biggest part about it getting hired at bigger companies.
And if you're trying to do, you know, smart software engineering and.
This even applies for start ups to there may be less intensive interviews, but they're still going
to be like technical interviews for a lot of these positions.
So study algorithms, I know that we had an algorithm section and I covered some.
But you need to train yourself on this so it's time to like, hit the algorithm, Jim, if you will.
You should make an account on a site like leak code, which is my number one recommendation or hacker
rank, which is not bad.
Ali code, I believe, is better just personally.
I think it has more up to date questions and a stronger community and not ripping on hacker rancor,
any other sites.
I think there's like Code Wars is one too.
But I just think the code is seems to be like the most prominent one.
These websites have challenges practice problems like algorithms and data structures.
You practice using data structures to solve problems and using algorithms, and coming up with algorithms
to solve difficult problems.
You should just go on there and seriously grind as many as you can and tell you feel pretty confident.
These jobs, like I said, are all about the interviews and preparing for them is key.
There's a very popular book that's kind of associated with Hacker Inc.
That was, I think the author is account dal or something like that.
She created cracking the coding interview.
It's a book that a lot of people really love.
It's about preparing for interviews at these big companies.
I would also strongly recommend that I read that as well.
But I think the most important thing is definitely if we code.
So if you can choose one out of everything that I've told you, I would just grind like like if you're
like, I'm not doing this, I'm not learning a new language.
I don't care about it, and I don't care about reading that book.
If I can say do one thing.
It would be to make an account and you don't have the pain account.
I think we could have paid and pay like a free version.
Just get on the code and just start smashing as many of these problems as you can.
That would be my number one recommendation.
So this is probably like it goes a lot.
This is probably useful for like students, maybe university students, because I know when I was a
student, I didn't know so much about what the next steps were to getting in the industry and working
at these jobs.
So I would totally like offer this advice to any university student that I talked to.
So the third one is if you want to be a web developer, so it's I'm not saying that like software engineering
and web development are like completely separate.
They're often going hand in hand.
You're working for companies that have like websites and web applications.
But when I say you want to be a web developer, I'm talking more about like you really want to focus
on, like making websites for people.
Maybe you're trying to do freelance and maybe you're working at like some really like brand new startups
and stuff like that, and you just need to know a lot.
Those people want you to know a lot about their tech stack and just be able to do like where they of
course, want you to know about algorithms, algorithms and stuff.
But they're not going to like, kind of like push you as hard and like a technical interview on like
advanced algorithms and stuff like that.
And like having it, you know, some of these fake companies, like for software engineering, it's
all about the algorithms, all about that technical interview.
These people want you to know.
Like if you're being a web developer making web applications for some smaller company or freelance,
it's important that you just know a lot about the tech stack.
Know a lot about web development general.
And there's a lot of languages that are used for this.
So if I have to recommend just one of them because it's kind of overwhelming if you get into this huge
ocean of web development, it's like, What do I do?
There's just so much out here.
I would recommend just one of them if I had to recommend just one of them, that's what I mean, I would
say JavaScript.
Personally, I like Python.
I'm into like writing Python code more than JavaScript.
I enjoy Python more as a language, but if I have to be completely honest, JavaScript, I'm pretty
sure it's the most popular language like ever.
So if you're interested in web development, I would say if you had to just pick one, I would pick
JavaScript and try and learn JavaScript.
If you're interested in back in web development specifically, you still should learn JavaScript first.
Just in general, I'm talking about like vanilla JavaScript, and then you should learn Node.js, probably
because that's used for back in.
So after you have a grip on JavaScript, I would do that.
If you're interested in front end web development, I would recommend learning a framework like view
or learning about TypeScript and then learning react or angular, so reacted angular.
React is like a library, an angular kind of two.
You could kind of some people call them frameworks as well.
But I think technically a lot of people like to refer to react as a library.
Those used, to my best knowledge, React uses TypeScript and I think Angular does to TypeScript kind
of like an interesting type of JavaScript, it's like JavaScript kind of used in.
So I would go look at that and kind of just learn the most you can about those things, right?
And that would kind of be the quickest path if we're talking about, like right now from this point
of view, only knowing what's been said and mentioned in this course, I would say the quickest path
to becoming a web developer would be to just grab JavaScript by the horns and like, just go learn,
you know, all this stuff about JavaScript.
So that's my advice.
Again, disclaimer remember or take it or leave it.
And this is just my opinion.
So number three, I'm interested in coding in C++ for a career.
So C++ is great, and if you took this course because it was C++ and you just love C++, it's kind of
like when I was talking about that and that hobby slide.
But let's say you're interested in having a professional career in C++.
I would like to just mention the things that C++ is most widely used for.
So you could have a better chance at succeeding.
You know you have more options, right?
If you prepare yourself for these types of careers.
So C++ is very popular for applications that require high levels of precision.
And it's also, you know, it's an older language but still very powerful, and this is used in the
modern world.
A lot, lots of engineering subfield use C++.
So it's very popular in like the aerospace industry and anything that uses IoT devices.
If you're interested in that type of stuff, you're going to be more interested in the engineering side
of programming.
So you'll want to know a lot about just kind of things that would be close like more closely coupled
with computer engineering and electrical engineering.
But I'm not saying that you have to like go being an electrical engineer.
I'm just saying that if you're interested in this, I would probably recommend focusing on embedded
systems development and learn more about low level programming and maybe even like assembly language,
you know, like the computer instructions that are kind of like a human readable version of binary,
the systems processing extra instructions, right?
I would get into that and maybe even learn a little bit of C C++ was built off of C, so you already
will kind of know some, you know, you know, you learn about structures, right?
And you learn about arrays and stuff like that.
So maybe learning some C would be good.
And of course, studying, you know, whether that be Udemy or books or YouTube or articles learn about
some embedded systems development would be my recommendation if you're passionate about, like aerospace.
You know, I have some family works in aerospace and I have worked in aerospace a little bit.
If you're interested in like rockets and things like that, I would maybe look into embedded systems
development.
And stuff like that, so the biggest thing for C++ by far is game development.
Game game development is like almost all C++ for like serious games, right?
Like big game companies like E.A. and stuff like that, you know, they develop their own game engines,
right?
And then people use those engines to make the games like and I'm talking about them internally.
They use their own game engine to create a game.
A game engine is just kind of like an environment to create a game, you know, like if you think about
like, you know, Photoshop or something like that, you're clicking on things.
You have this environment to like, make a game.
It's like a big piece of software.
It has graphics, it has a graphical user interface.
These game engines are developed at these big Triple-A companies by themselves internally, and they
are proprietary.
For the most part, and you can develop game engines with C++ and you can develop like code inside of
the engines themself if you want to make the game.
So if you're interested in working on a game engine and C++, I would recommend a great YouTube channel
and I'm not sure how much they're allowed to promote other people's YouTube channels on here.
It's not my YouTube channel, but I have seen a guy on YouTube called Chernow.
I think it's C H e r A..
And he has like a massive series on game engine development.
This is not something I'm going to make a course on because I'm not knowledgeable enough about it to
make a Udemy course on.
But if you are interested in that, I would say go over there.
He also has like so many C++ videos, so you can also, if you're not into that YouTube stuff, you
can also get a book on it.
Of course, you know, like whatever you want to do, but you're at a good point to start learning about
the game engine, right and working on game engines.
And then if you're interested in creating a game itself, so you use an engine and there's an existing
engine called Unreal Engine, and I think that you can use C++ to develop games on there.
So if you want to make a game using an existing engine, that might be a good idea to use Unreal Engine.
If you want to make a game from scratch, it's like in between developing an engine and making a game
so you want to make a game, but you don't want to like use a fancy engine with all these tools, you
kind of want to use more rudimentary stuff to make a game.
You could use things like SDL, SDL too.
I think it's the more modern version that's like real gives you like real barebones tools, kind of
just a library that you use in C++, and you can just start making games and developing graphics from
scratch.
Kind of.
So that was kind of a lot of information, but I hope that it reached somebody and helped someone as
far as next steps.
And of course, if you have any feedback to offer on this course, then I would love to hear it.
No matter how critical it may be, and I wish you the best of luck in your future career or hobby or
whatever one of those questions you know most applied to you and your situation.
All right.
So thank you again for taking the course and good luck in your future endeavors.