These videos are genuinely both entertaining and informative while being straight to the point. Looking forward to more system design in the future. Keep up the good work!
@@anonforever123that's an odd way of thinking about this. There's no such thing as "I've learned x amount of programming" or that "I've dived this deep into y", therefore I am now a god at this. Just like in every craft, with each project, you'll improve, but there's no end point to it. You can't "finish" it my guy xD You just continuously learn and continuously dive deep into the current project you're working on. What's in the video is correct, all that's left for you to do is create a bunch of them until you've become a "backend god"
@@Faun471This is so true. And i agree with this 💯. There's no end to this. You have to keep going on with learning and other stuff. And this goes on as long as you're alive. Because this is not a video game. It's a real life thing and it will only end when you die. So keep on learning and happy coding.
It's not the videos that teach you how to think like a back end developer but the videos that teach you how to be a back end developer that reign youtube. It simply amazes me.
I clicked because the title promised a lot haha. But it kinda oversimplifies the backend a bit too much. I expected more. I feel like beginners gloss over what makes backend hard. No offense tho. What I got from the video is all know how to code + database (store data woohoo)api (serve data woohoo) + tests + system design (I kinda wish you talked about a VPS, CDNs, SES, or even just S3 here). There's definitely a lot harder parts I wish I learned better back then: • REST and the HTTP Protocol • Parts of the Request-Response lifecycle (You should definitely learn how Request and Response headers work or how cookies pass through between the browser and your backend, or how you can redirect browsers using the Header) • Implementing your auth from scratch (JWTs vs Sessions) - This is probably super fundamental and I did not see it talked about here at all. Implementing UN/P and OAuth2. • Setting up a database migration system (actually enlightening as hell when you first learn it) - migrate:up, migrate:status, migrate:down, etc. • Backend Architecture - Actually knowing how to vertically/horizontally slice your backend codebase into layers. Appropriately of course. DDD is a must-learn for intermediate developers (a bit overkill in some projects but learning these concepts changed my life). Learn what DAOs, DOs, Repository Pattern, Entities, Aggregates, DTOs, etc. are. You don't need to apply all the concepts but just pick what makes sense. • And yeah, Systems Design probably. Like maybe just an explanation of why you'd probably need S3 (because you can't store blobs in the database, which is a very common usecase for saving pictures, videos, pdfs, etc), and a bunch of other cloud services. • A little bit of CI/CD as well. GitHub actions, making a deployment to a VPS upon pushing to the repo. There's a ton of uncomplicated examples out there (Kamal for example). • A bit of Linux and VPS skills as well: NGINX or Caddy, TLS, adding a domain name, PM2, etc. Deploying a node application on a VPS is a grueling, but valuable learning effort that platforms like Vercel just spoonfed to most devs nowdays.
I appreciate you taking the time to leave a detailed comment! Yeah you’re right about everything, but it’s very hard to fit all of these topics into a video meant to serve as an introduction. I will of course expand on these topics in later videos, but I personally feel it’s hard to understand these concepts without having the grasp of the fundamentals of backend engineering. For example, how can you understand slicing your backend codebase into layers when you don’t even know what a backend codebase looks like? TL;DR - Very good points, but I feel these advance concepts are more suited for a more advanced video - this roadmap is meant to highlight stuff for people looking to just get started with backend engineering.
Being a junior developer can be very overwhelming. Which IT branch should I choose? Web, gaming, AI, science, mobile, hardware? Which path should I choose? Backend, frontend, forehand, fullstack? What technology? .NET? React? Next.JS? Django? Oh, something new has come out, I'll check it out too. What languages to practice? C, C++, C#, Java, Python, JS? Or maybe TS, maybe some Go, Rust, Carbon etc.? Any Python libraries? One roadmap? Second? TH-cam? Books? Courses? Documentation? ProjectOdin? Leetcode? AdventOfCode? Kaggle? What else? Maybe design patterns and paradigms? Terribly frustrating and mentally damaging. It is a scandal that neither universities nor companies want to help young people enter the market and become good, happy employees. (I appreciate how many opportunities the IT industry offers, how interesting it all is, but we are not robots to understand it all.)
let's go for a walk : but wait should i start walking from a left leg ?, a right leg?, a jump?, should i really go for front? maybe i should go on my 2 wheeler ohh no, How about the latest electric one? should i not walk with a friend or family member? i don't know it's terribly frustrating and mentally damaging how the hell and where the hell am i supposed to start from ? there are many ways ?????? --start from anywhere you like buddy but make sure you enjoy the walk :)
My "struggle" with backend after 2 years of working as a backend dev mainly consists of just the sheer number of technologies I have to be familiar with beyond surface level. Headers, migrations, auth, caching, redis, redis clustering, azure, docker, containers, kubernetes, logging, elastic, kibana, grafana, jaeger, Java - maven/gradle, nexus, Linux, "insane" db designs, security, microservice architecture, kafka, holy **** kafka, dealing with bad data, testing, fkin java 6 legacy systems build with ant or smth ffs, postman/curl, Prometheus, Jenkins haha more like Hudson. Sometimes even understanding the hierarchy of your own company, zero documentation beyond detail design with no understanding what the thing you're writing is even supposed to do, very busy seniors that always answer stuff after 8pm, meetings where you have exactly 0 idea what's even being discussed, outdated internal wiki... But I love it honestly because even though I'm lost most of the time, the high you get when you overcome something like this is insane
Aaah you just sound like a friend of mine who's also a backend dev It's true as I've seen him that he's really busy and always postpones our plans to just get some fresh air and he literally gets frustrated as he doesn't get time for himself and to the one's that he wants to date...😂 ,really it seems like he's involved In some kind of cult that he doesn't want us to know that what's really happening inside his life It literally make me laugh and also jealous😅
Learned frontend and was interviewed with the front end mindset.. have been full stack since day one.. fire hose tactic starts to go down smooth after a while lmao
i started with javascript, coded 1.5 years in it, then moved to python bcs i lost my job, now i find python easier then javascript/typescript. but in general my preferred way is first to learn JS/TS and then move to full stack
Thank you so much this was so informative and helpful, much much better than 99% popular youtubers who only talk about shitty AI and give nothing useful to viewers
I'd do more than just print or log while debugging. Place more effort on step debugging with breakpoints to widen the context and shorten your time guessing what could be wrong.
good, you explained all the fundamentals and everything, sure there are many other things as well but these are so important and any beginner and someone who has atleast less than 3yoe should know these very well, because some stuff like system design can be considered for 3+ yoe . But the main things you listed them out well WOrth a like! cheers
“Most backend engineers don’t learn how to work with SQL or databases”. 🙄 I would say learning advanced SQL and database is fundamental for backend engineers.
@@rex_richies if you know C and C++ it means you know the working of pointers ,stack ,heap . Now choose any domain like web dev , mobile app dev , blockchain dev or embedded system in which you are interested . Java and javascript is the most used language in the market so it will be better to learn any of it and its framework if you want job asap
@@rex_richiesbcuz most (if not all)modern languages are influenced by C and C++. That's why if you'll start with basics, it will be easier to you in the future.
I think the goal is to become someone useful and not just someone versed in academic programming. Java and golang… Even google doesnt use golang that much. And I remember trying to learn Clean Coders stuff for java. its like a talmud 6000pages long. Id still take something useful like js or python over java and golang.
Yes 100%. Every engineer should be full stack somewhat. Backend engineers’ work impacts the frontend, and vice versa. Also gives you more job opportunities, especially at startups where all engineers are required to work on all parts of the stack.
Or, you could try C# + Dapper + Stored procs and enjoy life ..... Go is adorable, but it's got nothing on the speed and vast abilities of C#. Yes, I know. Concurrency models and panics. C# has had most of what Go has and much, much more. Way more support for xplat as well, don't have to use templ to do basic HTML from BE, etc. I could go on....
I want to become Java developer but before that do you think it would be better to learn First html,css and JS? According to some jobs offers for Java or backend developers is desirable to know html,css and JS. Not 100% this is the right path but we will see, but I would appreciate any suggestion on this Path. Thank you very much
Its good to know web dev as a fundamental knowledge being a com sci student , it is important to know how web is developed how it works , it does not matter if you are perfect at it or not at least u should know. For me web dev is a basic skill a com sci student should have ,even though u are bad at it or u are interested in diff. Domain 😂
If you want to be a backend engineer, don't be a coder, don't learn "coding principles" based on poor tutorials, be an engineer, study real principled knowledge backed by centuries of science and engineering, be smart. Otherwise, you will be a cheff saying that is doing chemistry. Choose your destinty, or destiny will choose for you. -- Albert Einstein
Honestly, I would rather not recommend anyone start with Java if they're doing backend. Java backend usually means Spring and learning Spring won't teach you as much about the backend as something like Golang where you have to build a lot of stuff yourself and learn how to do things.
"Most backend engineers do not learn how to work with SQL or databases" 😒, I guess you are right when someone simply identifies as a backend engineer but isn't one.
What are you talking about?? That's how you are supposed to do it. It's stupid to try to learn multiple languages at once. Focus on python first then other languages.
@@aristonsaizoxic1048 I started learning with Python too! There’s nothing wrong with Python at all, it’s one of the most used languages for a reason! I just recommend that after you feel comfortable with Python, you should take a quick look at a language like Java (or C if you’re brave) to understand a few things that Python does automatically for you. You may work with another language in the future so it’s good to know those things. Keep up the great work, you’ll be an excellent engineer!
Just go over pointers, memory concepts in c/c++ after python and you should be good at a high level. But do go over c/c++ if you get the time as it will make transition of languages easy
He's talking about things like 'pythons' so maybe he's talking about how to deal with snakes? No clue tbh, he's just blabbering nonsense, 0/10, left a dislike smh
Im sorry be the laguages that you should really start with should be either C or Assambly x86 if you got much freetime. Then C++ and OOP in C++. Here you've mastered algorithms and OOP time for some DBs and .net with C#. And finaly ur ready to learn whatever you want.
These videos are genuinely both entertaining and informative while being straight to the point. Looking forward to more system design in the future. Keep up the good work!
Thank you! Excited to get to the system design content!
what a username
This feels like more of an intro to backend engineering, rather than a roadmap.
Ikr. Just click bait. All this info is entry level.
@@anonforever123that's an odd way of thinking about this. There's no such thing as "I've learned x amount of programming" or that "I've dived this deep into y", therefore I am now a god at this. Just like in every craft, with each project, you'll improve, but there's no end point to it. You can't "finish" it my guy xD
You just continuously learn and continuously dive deep into the current project you're working on. What's in the video is correct, all that's left for you to do is create a bunch of them until you've become a "backend god"
@@Faun471This is so true. And i agree with this 💯. There's no end to this. You have to keep going on with learning and other stuff. And this goes on as long as you're alive. Because this is not a video game. It's a real life thing and it will only end when you die. So keep on learning and happy coding.
It's not the videos that teach you how to think like a back end developer but the videos that teach you how to be a back end developer that reign youtube. It simply amazes me.
I clicked because the title promised a lot haha. But it kinda oversimplifies the backend a bit too much. I expected more. I feel like beginners gloss over what makes backend hard. No offense tho.
What I got from the video is all know how to code + database (store data woohoo)api (serve data woohoo) + tests + system design (I kinda wish you talked about a VPS, CDNs, SES, or even just S3 here).
There's definitely a lot harder parts I wish I learned better back then:
• REST and the HTTP Protocol
• Parts of the Request-Response lifecycle (You should definitely learn how Request and Response headers work or how cookies pass through between the browser and your backend, or how you can redirect browsers using the Header)
• Implementing your auth from scratch (JWTs vs Sessions) - This is probably super fundamental and I did not see it talked about here at all. Implementing UN/P and OAuth2.
• Setting up a database migration system (actually enlightening as hell when you first learn it) - migrate:up, migrate:status, migrate:down, etc.
• Backend Architecture - Actually knowing how to vertically/horizontally slice your backend codebase into layers. Appropriately of course. DDD is a must-learn for intermediate developers (a bit overkill in some projects but learning these concepts changed my life). Learn what DAOs, DOs, Repository Pattern, Entities, Aggregates, DTOs, etc. are. You don't need to apply all the concepts but just pick what makes sense.
• And yeah, Systems Design probably. Like maybe just an explanation of why you'd probably need S3 (because you can't store blobs in the database, which is a very common usecase for saving pictures, videos, pdfs, etc), and a bunch of other cloud services.
• A little bit of CI/CD as well. GitHub actions, making a deployment to a VPS upon pushing to the repo. There's a ton of uncomplicated examples out there (Kamal for example).
• A bit of Linux and VPS skills as well: NGINX or Caddy, TLS, adding a domain name, PM2, etc. Deploying a node application on a VPS is a grueling, but valuable learning effort that platforms like Vercel just spoonfed to most devs nowdays.
This is very helpful. Can you recommend sources for learning these concepts? I would like to study them on my own.
I appreciate you taking the time to leave a detailed comment! Yeah you’re right about everything, but it’s very hard to fit all of these topics into a video meant to serve as an introduction. I will of course expand on these topics in later videos, but I personally feel it’s hard to understand these concepts without having the grasp of the fundamentals of backend engineering. For example, how can you understand slicing your backend codebase into layers when you don’t even know what a backend codebase looks like?
TL;DR - Very good points, but I feel these advance concepts are more suited for a more advanced video - this roadmap is meant to highlight stuff for people looking to just get started with backend engineering.
@@Codebagel would you mind sharing resources for understanding these topics for someone who is doing a self study?
Send resources my dudes
Quite extensive, definitely agree with you
Being a junior developer can be very overwhelming. Which IT branch should I choose? Web, gaming, AI, science, mobile, hardware? Which path should I choose? Backend, frontend, forehand, fullstack? What technology? .NET? React? Next.JS? Django? Oh, something new has come out, I'll check it out too. What languages to practice? C, C++, C#, Java, Python, JS? Or maybe TS, maybe some Go, Rust, Carbon etc.? Any Python libraries? One roadmap? Second? TH-cam? Books? Courses? Documentation? ProjectOdin? Leetcode? AdventOfCode? Kaggle? What else? Maybe design patterns and paradigms?
Terribly frustrating and mentally damaging. It is a scandal that neither universities nor companies want to help young people enter the market and become good, happy employees.
(I appreciate how many opportunities the IT industry offers, how interesting it all is, but we are not robots to understand it all.)
hahah i feel it
@@EliiiXD How do you deal with it?
Do you know analysis = paralysis?
If you want money and stability. Dont choose gaming.
let's go for a walk :
but wait should i start walking from a left leg ?, a right leg?, a jump?, should i really go for front? maybe i should go on my 2 wheeler ohh no, How about the latest electric one? should i not walk with a friend or family member? i don't know it's terribly frustrating and mentally damaging how the hell and where the hell am i supposed to start from ? there are many ways ??????
--start from anywhere you like buddy
but make sure you enjoy the walk :)
My "struggle" with backend after 2 years of working as a backend dev mainly consists of just the sheer number of technologies I have to be familiar with beyond surface level. Headers, migrations, auth, caching, redis, redis clustering, azure, docker, containers, kubernetes, logging, elastic, kibana, grafana, jaeger, Java - maven/gradle, nexus, Linux, "insane" db designs, security, microservice architecture, kafka, holy **** kafka, dealing with bad data, testing, fkin java 6 legacy systems build with ant or smth ffs, postman/curl, Prometheus, Jenkins haha more like Hudson. Sometimes even understanding the hierarchy of your own company, zero documentation beyond detail design with no understanding what the thing you're writing is even supposed to do, very busy seniors that always answer stuff after 8pm, meetings where you have exactly 0 idea what's even being discussed, outdated internal wiki... But I love it honestly because even though I'm lost most of the time, the high you get when you overcome something like this is insane
Aaah you just sound like a friend of mine who's also a backend dev
It's true as I've seen him that he's really busy and always postpones our plans to just get some fresh air and he literally gets frustrated as he doesn't get time for himself and to the one's that he wants to date...😂 ,really it seems like he's involved In some kind of cult that he doesn't want us to know that what's really happening inside his life
It literally make me laugh and also jealous😅
Genuinely a good roadmap because it gave context around everything
I’m glad it was helpful! I’ll be making more roadmaps for other specializations going forward so stay tuned!
@@Codebagel as a frontend engineer, I'd love to see what you put in frontend roadmap! best of luck.
i truly feel like if you know the database really well then rest is really easy
Why is that?
Lol it’s far from it
Lmao 😂😂 not at all
Absolutely
ORM ?
Man, found your videos like 1h ago. Can't stop watching as you're nailing everything i need.
Learned frontend and was interviewed with the front end mindset.. have been full stack since day one.. fire hose tactic starts to go down smooth after a while lmao
i started with javascript, coded 1.5 years in it, then moved to python bcs i lost my job, now i find python easier then javascript/typescript. but in general my preferred way is first to learn JS/TS and then move to full stack
My first time watching your video and I had to subscribe right away! Amazing video, thank you.
earned yourself a sub buddy, good stuff!
Thanks so much!
A great straightforward video. You are the best.🤝
Great stuff, both comprehensive and interesting, keep up
Worth subscribing.
I'm glad it was recommended to me
Thanks! I’m glad it was recommended to you too!
You don't need fireship, we have fireship at home. fireship at home:
I loved your content man! I learned new perspective, new insights. Thank you, keep it up! ❤😊
Great video and great comments!
i become god at backend, wait how should i write the db queries again ?!
You are a good man. Wish you will continue to come up with good content.
Comments like these make it easy to continue! Lots of content coming up!
That lead up made 'cache's make perfect sense!
Use debugger and breakpoints are game changer for me on testing and debugging part.
where do i find it in notepad?
looking forward for system design videos, that is beginner friendly and have study case examples
Thank you so much this was so informative and helpful, much much better than 99% popular youtubers who only talk about shitty AI and give nothing useful to viewers
Is it weird that I watched this video while being a back-end engineer, writing code and eating a bagel?
I'd do more than just print or log while debugging. Place more effort on step debugging with breakpoints to widen the context and shorten your time guessing what could be wrong.
Thank you so much! It was extremely helpful and informative.
Good introductory video. Such things are not available on youtube
good, you explained all the fundamentals and everything, sure there are many other things as well but these are so important and any beginner and someone who has atleast less than 3yoe should know these very well, because some stuff like system design can be considered for 3+ yoe . But the main things you listed them out well
WOrth a like! cheers
such an amazing video. Straight to the point and very informative
Thanks
“Most backend engineers don’t learn how to work with SQL or databases”. 🙄 I would say learning advanced SQL and database is fundamental for backend engineers.
I agree! Every backend engineer should know SQL and database work!
Good video, I really like how you summarize the info
Thanks so much!
Great video!
I'm a frontend dev and I know all that stuff. I was hoping for something more in depth. Or maybe I'm ready and don't even know it
Awesome content ! Also please tell, how to apply for jobs as backend developer.
I’ll make a video on this in the future!
Amazing well put!
people should start from C or C++ and then after they can choose lang. according to their liked domain
Sir please can you educate me more based on your experience, i started with C++
@@rex_richies if you know C and C++ it means you know the working of pointers ,stack ,heap . Now choose any domain like web dev , mobile app dev , blockchain dev or embedded system in which you are interested . Java and javascript is the most used language in the market so it will be better to learn any of it and its framework if you want job asap
@@rex_richiesbcuz most (if not all)modern languages are influenced by C and C++. That's why if you'll start with basics, it will be easier to you in the future.
C++ is garbage.
I started with C++ and honestly fuck you and fuck pointers
Good video, great voice & simple explanation
I think the goal is to become someone useful and not just someone versed in academic programming. Java and golang… Even google doesnt use golang that much. And I remember trying to learn Clean Coders stuff for java. its like a talmud 6000pages long. Id still take something useful like js or python over java and golang.
Really nice video, could you do one for data/cloud engineering?
Great video, the animations are on point and you also explained everything really well. I'm currently trying to improve at making APIs
Thanks so much! It’s good that you’re improving - one day you’ll be able to write APIs in your sleep haha
This is becoming a backend beginner lol. All info in here is entry level
That's really good info 👌🏻
“java: easy to learn“, yeah definitely 💯
Sarcasm??
Yes @@alyjahbarros5175
Lol it’s intimidating as a first language, but it isn’t that bad.
Skill issue
It's only hard for idiots
my face when i saw ad 2:31
For current job market i think java go and js are best
Video Title: Backend Roadmap
Actual Video: Buy it on Course Careers
Is it worth going full stack in this day and age?
Yes 100%. Every engineer should be full stack somewhat. Backend engineers’ work impacts the frontend, and vice versa. Also gives you more job opportunities, especially at startups where all engineers are required to work on all parts of the stack.
bro i can tell one thing you're are great that's all.
Thank you,
siva
This video is all over the place. Learn python, django, maria db for database, learn to deploy the python app, call it a day
what about DSA? Shouldn't I learn that ?
Java, no way, C/C++ is the GOATed starting point.
very insightful
Or, you could try C# + Dapper + Stored procs and enjoy life ..... Go is adorable, but it's got nothing on the speed and vast abilities of C#.
Yes, I know. Concurrency models and panics. C# has had most of what Go has and much, much more. Way more support for xplat as well, don't have to use templ to do basic HTML from BE, etc. I could go on....
Very nice explained ❤
The recommendation algorithm, backend!?
Ooh men, that's from Machine Learning Engineers/Data Sciencetists.
That's still something that happens in the backend I believe
thanks for this video
Thanks for watching!
who's here from the frontend video 3:02
thanx for your video.can there be any possible way to work out for youtube backend engineer in real too
PHP left the group
Is JAVA modern COBOL ?
It's wild how he intentionally left out PHP
"Golang" not "go" , right?
The debugging part is so oversimplified that its lowkey plain wrong.
Thank you.
An Advice ╰(*°▽°*)╯
Don't pick Rust as your first language Trust me
Pick Rust when you have done coding at least a year or 2
Came here for some advices as a backend myself, ended up hearing absolutely basic shit 😂😂!! 👍 Great video for beginners though.
No one mentions authentication
I want to become Java developer but before that do you think it would be better to learn First html,css and JS?
According to some jobs offers for Java or backend developers is desirable to know html,css and JS.
Not 100% this is the right path but we will see, but I would appreciate any suggestion on this Path.
Thank you very much
Its good to know web dev as a fundamental knowledge being a com sci student , it is important to know how web is developed how it works , it does not matter if you are perfect at it or not at least u should know. For me web dev is a basic skill a com sci student should have ,even though u are bad at it or u are interested in diff. Domain 😂
@ I agree as well, it's like a basic requirement for developers regardless if you will end up as back-end developer.
Thanks a lot
@@rudycarv2197 👍😀
“It’s time to move on to what takes up the majority of a backend engineers time - API development” er no, that would be
calls and meetings 🙈
If you want to be a backend engineer, don't be a coder, don't learn "coding principles" based on poor tutorials, be an engineer, study real principled knowledge backed by centuries of science and engineering, be smart. Otherwise, you will be a cheff saying that is doing chemistry. Choose your destinty, or destiny will choose for you.
-- Albert Einstein
i need one for data analyst plss
What about kotlin?
Not even mentionning PHP OMEGALUL
great info
Start with php... ;)
No, HTML
PHP is valid choice. People are just not so well informed.
No don't learn php is not worse it
great video
Backend engineer does sound like a euphemism though.
im already a backend god, if you know what i mean, if you feel me
This feels similar to fireship
Most of this data should be illegal...
Invasion of privacy.
Honestly, I would rather not recommend anyone start with Java if they're doing backend.
Java backend usually means Spring and learning Spring won't teach you as much about the backend as something like Golang where you have to build a lot of stuff yourself and learn how to do things.
I would think python with flask
"Most backend engineers do not learn how to work with SQL or databases" 😒, I guess you are right when someone simply identifies as a backend engineer but isn't one.
I will never learn java, even if I had to learn 10 more languages to avoid it
Unfortunately, I already started learning python and I intend to finish learning python before switching another language.
What are you talking about?? That's how you are supposed to do it. It's stupid to try to learn multiple languages at once. Focus on python first then other languages.
@@Ohiostategenerationx I see. Thank you for reminding me that I'm on the right track.
@@aristonsaizoxic1048 I started learning with Python too! There’s nothing wrong with Python at all, it’s one of the most used languages for a reason! I just recommend that after you feel comfortable with Python, you should take a quick look at a language like Java (or C if you’re brave) to understand a few things that Python does automatically for you. You may work with another language in the future so it’s good to know those things.
Keep up the great work, you’ll be an excellent engineer!
@@Codebagel I have misunderstood. Thank you for clarifying 😊.
Just go over pointers, memory concepts in c/c++ after python and you should be good at a high level. But do go over c/c++ if you get the time as it will make transition of languages easy
The non-sense thing about this video is distracting and annoying background music.😡
Content was good. 😊 👍🏻
I just feel you broke up with node 😅
Why not javascript for backend?????
Becoz it's mainly a frontend language
will this roadmap get me a lambo tho?
Much more than that🤑🤑
the fireship pandemic
tf is he talkin about
sharks
he is trying to describe how to correctly butcher a goose, but he is having trouble coming up with it
He's talking about things like 'pythons' so maybe he's talking about how to deal with snakes? No clue tbh, he's just blabbering nonsense, 0/10, left a dislike smh
No PHP mentioned, opinion rejected. jkjk
is cloud deploy as backend?
Im sorry be the laguages that you should really start with should be either C or Assambly x86 if you got much freetime.
Then C++ and OOP in C++.
Here you've mastered algorithms and OOP time for some DBs and .net with C#.
And finaly ur ready to learn whatever you want.
pure balloney
Why not javascript ?
fireship 2.0
Start with GoLang
I believe Go will be one of the most used languages in the world in a couple years!