Couldn't be truer, it's a harsh reality but keep hustling and keep the passion alive and you'll get there

Welcome to capitalism!

That's the way my friend. Just keep hustling and keep improving - as long as you have that drive you can seriously accomplish anything

Cheers bro! Glad you think so - i would’ve tried to generalise it more but I’m glad there were still some take away’s with it!

Completely agree - it's not a job for everyone, and thinking its a 'fun' or 'easy' job is only going to get you so far before either you realise you aren't enjoying it, or you struggle to keep up with the work

Hey! The age old question of which game engine should I use. At the moment, Unity is still the leading engine that the majority of studios are using, so I tend to point towards there because I also find it easier to pick up - but that being said, it largely depends what type of job you're trying to get into. Most indie studios will use a commercial engine, whereas the larger range studios (think Activision/Rockstar) will have their own in-house custom engine, and the majority of the time the custom engines use c++, which is obviously where Unreal Engine comes in handy. I think ultimately, depending on where you are in your game dev journey, whichever engine you personally find easier to use is the right choice. If a company is looking for someone with unreal engine experience and your knowledge is purely in Unity, still apply but be transparent with your knowledge on it - as I said in the video, you're likely to be hired on for your potential, not your capability, so if they think you have the knowledge and drive to learn another engine then it can definitely be applicable either way!

Sent to you on Discord! :)

Hey! Great question - and it’ll definitely somewhat vary, but as an example, I nearly failed DSA completely at university. This for me was always a weak point, so there were occasional coding interviews that would test this and I would immediately fail them - but that being said, partially it was a skill i built up over time, but you should definitely know the basics, if not at LEAST how the algorithm works. Things like Time Complexity can come later, but if you can look at pseudo code and gauge a general idea of what it’s doing and why, then you’re off to a good start. I would definitely recommend doing coding exercises to at least build a general idea, or focus on a single algorithm (Dijkstra’s for example) and have that be your strength. you’ll find that once you know or are comfortable with one, the rest start to make more sense. That being said - it ultimately depends on what the employer/application is looking for - you might be specialised in UI and have no need for it at all

@@GarnetKane Thanks brother, i'm a self-taught and DSA is something that i always hesitate to get into (my friend studying CS told me that DSA is a pain in the a$$ for him at college as well 🤣), i guess i have to get into in sooner or later.

​@@justarandomguy-gn2tu I loved DSA at uni. Leetcode is a good website for practice, just try to write all the important parts yourself instead of relying on the libraries or what the language provides you.

Hey! How are you

@@GarnetKane Well, just finished my portfolio website and you said in the video to just say hi. So I did!