Learning docker was honestly a game changer, aside from making it easier to launch web apps. The ability to setup an sql server etc with one command is so convenient
Thanks! I watched this video right before taking an interview for an engineer position I really wanted. It gave me a lot of confidence and I managed to get the job. Thanks for making this videos!
An update: (for context I live and work for LATAM companies) I worked for seven months on the job I landed, though it ended being more of a data engineer job i learned a lot about working on an IT area (tikcets, sprints, comunication and technologies). But I got lucky and by chane found a job offering that all that it asked for was solving a case given by them (building a mail indexer with a backend and a frontend) in 4 weeks. They liked my solution to the case and now I'm working for a Y combinator alumni Colombian startup called Truora as a software engineer. Part of my onboarding is passing through many teams and right know I am on the devops teams learning about infra, aws and terraform
As a rule of thumb: If you know half of the things on the list, and are *excited to learn* about the other half on the new job, chances are you'll get the deal. For example I did not write a single unit test in my prior 3 years of experience as a PHP dev, also had no experience with using docker. And I told the new company during interviews I chose them BECAUSE I will be able to learn and use those things effectively there, and they were happy to hear that.
Based take. Had the same experience as well prior getting my first job, didn't know unit testing at all, but talking with my now boss, I showed that I was very excited and disposed to learning it, and he hired me on the spot.
Over time you'll build up those skills and experience, too. I started as a software engineer for the first 3 years of my career before I transitioned to DevOps/SRE. My first three years as a SWE let me focus on just coding and now I'm focusing on all the skills to be a better DevOps/SRE while using my SWE background to compliment my current role. You don't need to learn everything all at once.
Haha, I hope this is how it works for me too, I had no clue how much I genuinely like DevOps. I'm happy to be in SWE for now, but once that starts to become routine, I hope there is some spot for me to become a wizard with tons of machines and pipelines running at my behest :D
Fundamentals, fundamentals, fundamentals! Believe it or not, as a Netflix engineer, I don't know everything. However, I at the very least have a very, very basic understanding of a lot of technologies and if I ever need to use those technologies, I TITS (time in the saddle) my way through in order to achieve the ultimate goal of building the solution that the business requires. This is what I firmly believe, not exhaustive, exemplifies a really good engineer. 👍
And what would you say are the fundamentals? Let's call them axioms, for the sake of discussion.... I say that partially, because if you e.g. say data structures & algorithms, someone might say that this is a fairly broad/vague term? What we be other fundamentals? Understanding the 'compiling process' down to logic gates? I'm genuinely interested what you think, so that I can prioritise =)
@@kusocm I think it really depends but in my experience, it's not just the technical know-how but also skills that are seemingly undervalued by many. Some of those skills are communication, cross-team and stakeholder partnership management, humility, empathy, and the like. These type of skills, I think, are more difficult to hone than technical concepts/products which in most cases are pretty straightforward if you have no problem reading documentation, trying it out, and iterating on it. I will say that an engineer that is flexible is extremely valuable to any organization that they are employed at because it instills confidence to the team that they can trust that engineer to get the job done despite the challenges.
it's less about the skills but more about how much professional experience you have. I graduated 4 months ago and am still searching. Some even don't count internship time as experience. it's so frustrating.
Just one thing at a time! :) There is a really wide spectrum of breath and depth on the knowledge that you can have on software engineering. Some people want to do it all, some others want to focus. I find myself cycling through between both every few years. I find something I love and I go deep but when I'm tired of that I keep trying new stuff.
The most on point argument ever! I showed this to my brother, he is starting to code, I have 8 years of experience and I keep telling him not to give up just because of a big list on job posts
Great message. "imma knock out w/e they throw at me" not only makes you more motivated, but also builds the necessary qualifications and skillset to succeed in you job/ life. After a while you won't even remember the time you didn't know some of the concepts.
Great message! You won me over with the vim speed run but using your platform to let people know what to actually do succeed in this field is invaluable.
+1 to everything you said, the best thing a junior dev can do is to, explore a breadth of technologies and find out how they work in tandem. Some frontend, backend and devops. This will really help in new teams and interviews.
I like the message of “just do it”! And I know this wasn’t the point of the video but what DO you think is the best way for companies to interview people?
i think having a conversation where i know some technical depth about the same topic and we just talk about your experience. I like seeing how much a person knows about a topic. Depth tends to be the greatest identifier for me, at least.
As often happens, Prime is the realist and I’m the idealist. This video is the “right advice to get your first gig and start on the right path” If you’re on the other side and want to make interviews suck less hard, I have a video on that part 🙏
i am totally on the side of get in and try to fix interviews, but there is also a question that must be asked, or is implicitly asked, what is it that you are going to fix and how does your fix fix it? The reality is that I can talk to an engineer for ~1 hour and know if they will be a success or not. But I have also busted my ass for +15 years to gain this "ability." Would I trust a fresh grad to interview like me? No, please, I would expect less experience to use different filters for evaluation that I would use. i know, very unhot take ;)
As someone who is currently going through a Bootcamp for full-stack web development, being overwhelmed with all the technologies out there. This helps, Thanks Prime
Completely agree. Learning Linux and configuring Vim is what really pushed me to learn more and take more interest in what I was doing. I attribute the vim curiosity to you and fireship actually lol
As an IT professional who has to constantly adjust to new standards, all I have to say is knowing the minimum of something is important. Do you need to know 100% about vCenter? No, but being able to interact with the team who you might need to work alongside is important. An hour a day of practice on any topic you want to learn, will put you above the majority of professionals. I believe it was 30 minutes a day for a year will put you in the top 5% of any given field. That’s insane.
@@plaidchuckthe problem isn't even the udemy/youtub courses per say though of course quality varies, the root of the issue is lack of curiosity and intentional practice. Expecting any course to do this for you when you are passively watching and at best copy/pasting is a recipe for failure.
I needed this and baba delivered it and I like it. I am in this same scenario. And i am just trying to do it. Will do regularly though because I am in support role and it sucks. It's hard for me so i am spending sometime but as soon as you start getting a concept and try out some problem related to that DS and it will stick with you and you can switch to some other DS and then just continue. Thanks!!
You got it babe! You have to dig deep and go through things. I would first recommend making sure you are great at building things, and every day read a bit about algorithms. I don't think leet code is that great.
@@ThePrimeagen actually i am working on a project with node as BE and react as FE. Basically it will generate digital brochures in pdf format. I am taking my time and learning a lot of stuff from that. As soon as I learn go i will switch my BE to it. And i am experimenting with AWS S3 bucket as well. I try to read DSA but don't spend much time on it. Just a glance and done.
This video is awesome! I feel like the illusion that your interviewer is all-knowing and expects pure elegant solutions on the fly is common yet flawed.
Sounds like a Facebook interview. You got the easiest questions man. It happens. Merge overlapping was one of the questions I got that prevented from getting a new grad position at Meta (only because the interviewer English was the worse and his communication was “just do it” as I asked what are the inputs. This was my Meta new grad onsite only 3 interviews. 2 technical and one behavioral. 3/4 solved and did a great behavioral interview = no offer. Also the interviewer cut off his Zoom and left (never got a second chance as I complained to my recruiter).
@@markvaldez8602 I know it is easy to say... but that was not the person to let you in the door. Apply again and get someone else. I like Primes Iday of going to companies you dont want to work at and interview there. Just... keep... going...Churchill said "When going through hell.... keep going...."
@2:08 knowing the terminology and what to search on your own is the most important skill in my day to day job. That is what colleage supopose to be. Training the brain of young adults to find and filter knowledge without the assistance. (Good luck to all you folks who are struggling to get hired. Keep on learning.)
@@ThePrimeagen I'm trained in "public administration" but have the luck to work as dev. Education helps for sure but with a bit of effort it is possible to fill the gap :-)
I think most of this is true but I also think the missing part is learning, even to an exploratory level, without actively working in that space for a while, won’t solidify the concepts enough. A lot of time is needed unless some sort of refresher is done before the interview, which I highly suggest btw.
CS student here. First I want to layout what my life looks like, I am 23, married (no kids thank god), live on my own, work full-time, take 12-18 credit hours every semester, building a project that is way over my head and feels like another full time job, and i still have time for hobbies, family, friends, etc. Also, a little bit of background on me, I was never the good grade kid or a good student through out my early life. I am now a Junior in college and I am happy to say that I am killing it academics wise, I had a lot of catching up to do the first 2 1/2 years of college, developing good habits, studying techniques that are good for me, and getting rid of the procrastination and bad habits. This is my take when it comes to these "technologies companies request": - Learning these technologies is not hard, you are just being lazy. - NO, what you learn in class will NOT get you job ready. - If you don't code outside of class, and learn technologies/concepts/theory and so forth, then you are not doing enough. - All these things that feel daunting looking from the outside in, they turn out to be pretty simple and easy to learn once you get to it. - My advice, stop building generic projects using youtube tutorials and come up with a project that will challenge you, then put together this project with the technologies you want to learn. Only use tutorials to learn how specific components that you want to build. Then, apply your own solution/sauce to it. Look, at the end of the day, its not easy. I go to bed at 12am to wake up at 4:30am every day of the week, including weekends, but i only have another 3 years of this and then its over (I'm doing a 4+1 for a masters in cs). Yes, there are days where i wake up and i just wanna throw in the towel, there are moments where i feel like I am at my breaking point (gym/running or any kind of pt usually helps me with this). But it is what it is, I have dreams and aspirations which I want to make reality. If you have something you truly want, then just do it.
You will never learn enough in a couple weeks. Your best bet is to learn by projects. I learned Typescript+React Docker/Kubernetes Java w/ Spring, Go and Message Queueing with RabbitMQ all in one project for banking/fintech. Coupled with NodeJS and ReactJS which I knew already, I worked on a microservice service environment that mimics what real world work would be like working on multi-language projects and pushing to github. This also allowed me to learn CI/CD pipelines. I "finished" out the project by learning Nginx Reverse Proxy which allowed me to host it on AWS EC2 cloud where I have a Google domain rerouted to AWS Route53 (DNS hosting) and then the Nginx serves my react/typescript build. My Spring Boot Java app talks to a cloud database in Amazon (RDS --> Postgres) and my Golang microservice talks to a Cloud DB (Non-RDS --> MongoDB). In total this took me roughly 3 months learning everything but nodejs and JS from scratch. My only other experience was with python for which I did no type of API development. Was it hard? A little bit because you have to code when you do not want to in order to get where you want to, but now, I can ATLEAST hold a conversion in regards to these different technologies and what their purpose is. Now I focus primarily on my weaker points (Algorithm and Dynamic Programming) for interviews. The best advice I can give you is you have to be comfortable being alone and focused on your grind, because it can be hard. If a job wants you to know more than 5 tech stacks and flows at a deep level to get a job, then its more than likely they are looking for a 10X programmer and not someone who is just starting out. Side note: I have absolutely 0 experience in SWE/Web dev as my current job is cyber security.
@@kofiboateng9181 Thanks for your response, it was helpful! I'm currently looking to get my first job as a web developer so I can later transition into cyber security, quite funny
@@tears_falling I still plan on doing cyber security in the future as well, but I started my dev journey to further my knowledge of cyber security and internet knowledge as well! Can't protect what you don't know thoroughly! haha Good luck on your journey and glad I was able to shed some light on a possible course of action for ya!
The defacto standard hiring practices are bullshit and I’m happy the company I work for does things different. For people breaking in we value seeing personal projects and will ask them to explain the technical decisions they made within. Critical thinking abilities also take precedence over institutional compsci knowledge or proficiency in any one tool.
yeah this is all true. the hard part is sussing out critical thinking. That is why we have what we have now, because its hard. I don't think its the best, I have a method I like, but I don't want people using my method because I think some people are unable to suss out things in the same way.
Experience is learning. It's just learning that you can't do in school. It's one thing to learn to configure a Raspberry Pi as a server and it's a completely different one to upload a new bare metal search algorithm on a million Google servers. Google will trust you with the latter... AFTER you have acquired the necessary experience to do it safely. Why would they let a rookie crash a hundred billion dollar search business? :-)
@@lepidoptera9337something so simple, but it makes complete sense. I think as juniors, we have a sense of entitlement to a job we realistically aren’t qualified for and feel too good for that IT Help Desk job because it’s no “culture” or ping pong tables and 6 figures. Nobody seems to want to start from somewhere anymore. We just want to get started with the big boys lol
@@lepidoptera9337they can give said rookie a smaller and less risky responsibility and he or she can learn the ropes and eventually become a full-fledged developer. But no, keep making excuses for not hiring juniors and then cry about not having enough developers to work on your projects.
Yes, but the problem is not the recruiter. Recruiters will choose the best candidate, that's their job. If there are more available jobs than there are candidates, then finding a job will be quite easy, even without experience. But sometimes, because of the economy, there will be more candidates than available jobs, which means that some people will be unemployed no matter what they do. But that's not the recruiter's fault. That's definitely a bad system (because you can't say "No company needs me? Great, less work to do!", and instead, you usually say "I have to find something to produce even if there is no need to produce anything more"), but if you accept it, then you have to play by its rules.
Bring on you portfolio the history of you solving problems. New job won't have the same problems, your ability to solve them is that's valuable. It may even be worth to go for a worse more junior job for a while if it allows you to build up your knowledge in the area that you are interested in, or contribute to open source and make your contributions publicly visible for future applications. "I did stuff" is always more impressive than "I know stuff".
Thanks for the video! I really like the approach your latest videos have, and how with your experience you can help us get our first job in technology. by the way, the meme is far the best of the video
All of that is in every BSc in CS, the problem is, that they require several years of working experience in these technologies. So getting an entry into these companies is more difficult than it has to be.
One way to look at it is that everything is grids of data. Maybe start by working with Excel and spreadsheets and go from there. For front end, layout colored boxes for a while with CSS.
I largely agree but the issue I have with the wish list, is that resume's are often automatically filtered based on those keywords. You can pick the right skills to learn. Can you confidently defend your skill in tech X though? If it's not on the resume, you can be filtered. If it's on there, you need to be prepared to defend. Resumes which just list tech after tech start to look like BS.
Not a software dev here, I'm a DevOps/SRE/integration engineer, but in my experience actual sane employers who are really in need of a (mostly junior, but not necessarily) software engineer, or a sysadmin, or an SRE guy, or whatever similar position really, and aren't MANGA so that they have a huge pool of extremely talented people to pick and choose from, are willing to look past not having some particular skills and experiences if you have something similar in your portfolio, or can demonstrate the understanding of why those skills are needed, and/or know and understand how the required tech works under the hood at least on a high level, and don't underestimate the significance and apparently rarity of an arcane skill of googling, whatever that is. If you can show the ability to quickly figure out the problem and how to solve it, little else matters really.
In fairness their are some completely unreasonable job requirements, the one I always remember is someone wanted a junior Dev with 15 years of experience in swift, yeah, 15 Years in swift
This is totally true. One thing I want to add is that every good engineer that I know of is a T shaped person. T means having a breadth amount of knowledge and being specialised in one of them hence the T shape. Sure I don't need to care about Docker or Kubernetes because of our DevOps team takes care of it. But knowing these "irrelevant" topics helps me to understand the process and therefore I might be able to fix a simple error myself so I can ship faster. Even if you don't need specific knowledge anymore most of the concepts/frameworks you learn help you to better understand new things because there is almost always something that can carry over to the new topic or give you new insights to what you already know.
I think what sucks with learning hard things is, you don't really know when it makes sense. Like for me, learning is 100% plateau after plateau. It's each one of those a-ha! moments that cements an idea for me, and sometimes it'll just randomly happen when I wake up, or when I'm taking the dog out. I guess I've kind of shifted my mindset from chasing "knowing/understanding" to "waiting" for my brain to click everything into place.
I agree a lot with Primegen that you should just go and learn the things they list if you want to work there. But it also depends on the position; If the things they require and ask you about isn't related to the job that they're hiring for, better avoid that company as it usually means that they don't know how to do interview processes.
Super based take. Looking at all the things i have to learn as an exciting opportunity to become a real professional is exactly how Ive stayed motivated to learn. I got a STEM degree but i got my degree in biology. And as much as i wish i could go back and discover my passion for programming and switch to computer science i think the most valuable thing i attained with my degree was actually the mentality i developed around learning very difficult concepts. Once you’ve done it in one area, you understand the process, and have one huge takeaway from the experience. NEVER confuse recognition for recollection. That lesson has kept me far more aware of my actual abilities than almost every collaborator Ive had on projects, until i came across my current collaborator that has the same mentality as me. Prime is dead on here
Good stuff here! I think one thing that most people tend to forget is (I quote someone, don't remember who it is tho): "People overestimate what can be done in a day and understimate what can be done in a year" I mean, it can seem daunting at first when you see all the stuff you need to learn, but guess what, you don't have to do it in a week, just put in the time and you'll be very surprised where you are in few weeks/months/years.
I think this is one of the best advice out there, nobody knows it all, but you gotta get good at solving problems and know how to look for useful information quickly
They only want developers that have experience and or people that can code projects that can run on their own. The kid that made Million.Js is NOT hunting hand to mouth for jobs. Alot of these techs as a regular everyday dev you dont have anything to build with some of these things. You only really have access when you work at a company. I jumped shipped and going into backend.
Just know that you have changed peoples lives and given them hope...I pray for health wealth and happiness of you and your family. Thank you for these gems.
wow, you just gave THE mindset for all and every things guys that we want in our whole life: We can get all we want and almost all we want is free, but cost something. How to 'pay' what you want is really a simple decision over: give $$ or give your time/patience/something inside you. Thank you !
I'm working on a test project for a junior front-end position right now, and when I got the assignment I didn't know half of the technologies they wanted me to use. Three weeks later and I feel like I know them like the palm of my hand. Modern technologies usually have pretty good documentation and "getting started"-type tutorials, so just learn it, man. It's really not that hard if you give it enough or your time and build a couple of practice projects with them.
Read about 'four stages of competence', it is 'natural' to think you're more competent than you actually are when starting to learn a new technology. Even when knowing about this I must admit I have multiple times overestimated my competence, or underestimated the time/effort I need to learn.
2:20 thank you for mentioning this. It's not about being a master in all these technologies, but it's important to at least know something about those technologies in order to be able to have a conversation. What they do, why they might be used and so on. Just being curious and learning about basics about many tools and technologies has allowed me to make better decisions in my work, remember that X tool exists when I have a certain problem or just being able to google stuff better because I know something similar might exist and might push me in the right direction. Curiosity and thirst for knowledge is really valuable in this line of work.
You don't need to know anything if you still don't know Git. So my number one recommendation to anyone who still feels "kind of beginner" is to learn Git before ANYTHING else, just start with raw text files and version control them as a practice! And become fluent enough in it so that you feel "confident". You don't need to master it all at once, you can't, you don't need to, and you shouldn't. After that start doing a quick project such as a todo list AND PUT ENOUGH TIME ON IT, remember, "commitment and consistency is the key". Also here's a quotation I've extracted from this Primeagen's video if someone's taking notes: "Be able to practice the art of discussing your ideas in a situation which it's just tossed on you, because most of the time interviewers are looking for someone that can discuss ideas and come to solutions, they're not necessarily always looking for someone that's going to give them the most pristine answer in that moment, and they're often not looking for someone that knows all the technologies that they've listed. ... I would highly recommend looking at life as a challenge not an inconvenience, and to look at it as an adventure not some sort of injustice or ill will towards yourself."
This is the realistic/honest take. It wouldnt be fair if employers expected you to be great at all of this while paying you junior salary, but usually they just want you to have a broad understanding and having played around with it a little. Unless you absolutely want a job at one of the Big5/FAANG/MANGA/whatever the bar is really just at "did you bother to look up the core infrastructure tech every major company uses and did you use it enough so we dont have to send you off to weeks of training before we can even see how you are at your main job". I am regularly amazed at how many people come out of university and cant write up basic SQL commands or a simple Docker config. Few jobs today are just coding within one language and one framework. I feel like thats what FullStack usually means: you should have a good idea how most of the stuff every company uses works and be really good at 1 or 2 of them. And that is achievable. And who knows, you might actually start using those technologies as auxiliaries to improve your main-proficiency.
Thank you for the inspiration! The problem with fundamentals for me is to how to make them FUNdamental - if i don't initially get WHY i would need something unreasonable on my resume, it is just so difficult to learn. And with deep stuff it's not easy to see unless you wait and think about reasoning of these requirements. So yea, considering requirements and skills required not as "requirements", but as a blank checklist of things to explore, helps a lot with making it fun. "Ok but WHY i need to know what's a hash-map? Ok but WHY they want to use Docker when our dev cycle is already in 3 VM's?" etc etc. Having and finding energy to wonder is a whole another problem, so good self-management and taking care of oneself is kinda the most crucial skill any person in any field could have. The final boss is not your interviewer, it's you.
As usual, the real question they are asking is "how to I learn the bare minimum to get a well paid job where I would be doing as little as possible to get paid". Why would anyone in their mind hire a "software engineer" who doesn't like algorithms and technology stacks? Would you go to a doctor who doesn't want to know basic biology?
Pretending a way of interviewing and assessing someone skills as necessary for the job when its not, still playing into that game.... There's nothing wrong with inconformity, the fact that there's this hairbrained process to get a job will lead to people learning everything there is to know, asking themselves, why do i need a job again if i can do everything myself.
It took me about 2 months to learn FFT, its a bit embarrassing it took so long but its true. I mean to really understand and know how to use it with other math, It was sooooo worth it, the coolest thing in programming.Those algorithms you will learn on University. it will take like 6 week. Take you're time and understand it deeply. Those algorithm "are used" all the time. You need to know them.
Thanks & broadly agree, esp with the point that you're getting a checklist which you can address directly. For specific techs like Docker, frameworks and even infra, you can spin up projects (often for free) easily and get real exposure to them. I think the hard part applying this to requirements faced by non-jr but non snr candidates when they get the bad luck of not having exp at shops with appropriate tech set ups e.g. using a range of databases for different types of solutions in a monolithic codebase with one big postgres instance. Not sure you can hard work yourself into experiencing a more distributed architecture, or managing challenging projects. Would like everyone's takes on how they recommend tackling this scenario!
This is true. You cannot possible craft a solution that met needs while having 10k customers to scale to 1million and find all the wrong decisions you have made. That is experience that only come with tears and time :)
Honestly this is what i recommend: Looking for a job? Learn a bit of everything and find information what is important to go ahead and learn. Just coding for for fun/hobby? Well learn what you need to learn only and do some research because you might find something that you prefer over what you are doing right now and it will also give you new ideas of what you can build with those new tools your using.
but people think "it should be fair." and that is the problem. Life isn't fair is a statement of absolutes in a sense, it will never be fair, and you shouldn't assume its default state is fair.
When I get a job I would feel better if I at least half knew what I was doing. I find that motivating. There is a lot to learn. Isn't that the beauty of the industry?
Hot Take: all SWEs and aspiring ones should make an effort to share and publicly shame stupid job postings -- for example "Must have 15 years experience in Golang" ... take your pick.
The real skills of software engineering: - Always be learning - Solve problems Languages, APIs, algorithms, design patterns, OOP, etc are the tools. At some point you know enough, you can "learn whatever you need to" on the job. But until then: take your time, learn *and apply* each thing until you actually feel like you know its strengths and weaknesses. Then, repeat. A career in software engineering is doing this over and over and over again. So if it is unfair to know all this to get past the interview: it might also be a sign that this is a career you'd hate... And that's okay: it is more important to learn what things you don't like. And SE isn't the only role in technology or the only job that writes code... So maybe there's a different role that you'd like even more.
OK but learning all of these things takes Time. Time which most people do not have. Since you can't devote much time to learning since you have to find a job to pay bills. I no longer think learning to program is something meaningful, all of these absurd wants and needs of companies have made it something I hate. And I loved programming.
...you are given a requirement list to dunk on to get a 6 figure sallary. Developers in third world countries with the same list getting a max of ~40k / year: 👁👄👁
I'm not getting the taste in Web Dev. What should I do? I'm following Machine Learning alongside AWS. Is there something else I could learn to get into SDE
I got an interview for an internship and it went very well, I'm gonna use vim as my IDE, if they hire me or fire me it's your fault Prime, love from Serbia ♥️
What kind of data structures are we talking about? I am halfway through the web developer bootcamp and the only CS term I know is "compexity". Dont even know where to start.
there is a book called Algorithms on Amazon for ~$120 . its my personal favorite here is my NON AFFILIATE CODE (because i really rec this book). www.amazon.com/Introduction-Algorithms-fourth-Thomas-Cormen/dp/026204630X
I have a confidence issue where the basic understanding often times doesn’t feel good enough and I feel obligated to know everything end 2 end which just leaves me feeling like I actually know nothing. (When I probably now more than avg)
![*Next-door 10x Software Engineer* [FULL]](/img/n.gif)
Learning docker was honestly a game changer, aside from making it easier to launch web apps. The ability to setup an sql server etc with one command is so convenient
i do it so often now.
Docker and linux coreutils are like having superpowers
which resource you used to learn docker? I know a couple basics about it, but would love to get a deeper understanding of it
@@Fran-kc2gu I learned with a udemy course, unfortunately I don’t exactly remember which course it was
@@klc3rd thanks!
Thanks! I watched this video right before taking an interview for an engineer position I really wanted. It gave me a lot of confidence and I managed to get the job. Thanks for making this videos!
Did you get it mate? Come back with some good news 👍
@@zzMigMitzz I did! Working there for almost 2 months already and loving it so far :D
@@thewalkthroughmaking what skills you have? How you Larned programming? Did it take long to get this job?
An update: (for context I live and work for LATAM companies) I worked for seven months on the job I landed, though it ended being more of a data engineer job i learned a lot about working on an IT area (tikcets, sprints, comunication and technologies). But I got lucky and by chane found a job offering that all that it asked for was solving a case given by them (building a mail indexer with a backend and a frontend) in 4 weeks. They liked my solution to the case and now I'm working for a Y combinator alumni Colombian startup called Truora as a software engineer. Part of my onboarding is passing through many teams and right know I am on the devops teams learning about infra, aws and terraform
0p.
As a rule of thumb: If you know half of the things on the list, and are *excited to learn* about the other half on the new job, chances are you'll get the deal. For example I did not write a single unit test in my prior 3 years of experience as a PHP dev, also had no experience with using docker. And I told the new company during interviews I chose them BECAUSE I will be able to learn and use those things effectively there, and they were happy to hear that.
Are you sure? All the things is not easy as php, bro 🤣🤣🤣 php is for non-cs
@@tuanva6484 yeah, real programmers do web development in assembly (not even web assembly, sir!)
Based take. Had the same experience as well prior getting my first job, didn't know unit testing at all, but talking with my now boss, I showed that I was very excited and disposed to learning it, and he hired me on the spot.
@@tuanva6484 unit tests and docker are easy asf to learn tbh
But when was that ? 5+ years ago people got hired almost just by passing few easy Leetcode questions .
"see life as an opportunity not an inconvenience"
True.
Over time you'll build up those skills and experience, too. I started as a software engineer for the first 3 years of my career before I transitioned to DevOps/SRE. My first three years as a SWE let me focus on just coding and now I'm focusing on all the skills to be a better DevOps/SRE while using my SWE background to compliment my current role. You don't need to learn everything all at once.
agreed. tackle the most important things and go from there.
Haha, I hope this is how it works for me too, I had no clue how much I genuinely like DevOps. I'm happy to be in SWE for now, but once that starts to become routine, I hope there is some spot for me to become a wizard with tons of machines and pipelines running at my behest :D
Fundamentals, fundamentals, fundamentals!
Believe it or not, as a Netflix engineer, I don't know everything. However, I at the very least have a very, very basic understanding of a lot of technologies and if I ever need to use those technologies, I TITS (time in the saddle) my way through in order to achieve the ultimate goal of building the solution that the business requires. This is what I firmly believe, not exhaustive, exemplifies a really good engineer. 👍
this is the way
And what would you say are the fundamentals? Let's call them axioms, for the sake of discussion....
I say that partially, because if you e.g. say data structures & algorithms, someone might say that this is a fairly broad/vague term?
What we be other fundamentals? Understanding the 'compiling process' down to logic gates?
I'm genuinely interested what you think, so that I can prioritise =)
@@kusocm I think it really depends but in my experience, it's not just the technical know-how but also skills that are seemingly undervalued by many. Some of those skills are communication, cross-team and stakeholder partnership management, humility, empathy, and the like. These type of skills, I think, are more difficult to hone than technical concepts/products which in most cases are pretty straightforward if you have no problem reading documentation, trying it out, and iterating on it. I will say that an engineer that is flexible is extremely valuable to any organization that they are employed at because it instills confidence to the team that they can trust that engineer to get the job done despite the challenges.
it's less about the skills but more about how much professional experience you have. I graduated 4 months ago and am still searching. Some even don't count internship time as experience.
it's so frustrating.
update?
Just one thing at a time! :) There is a really wide spectrum of breath and depth on the knowledge that you can have on software engineering. Some people want to do it all, some others want to focus. I find myself cycling through between both every few years. I find something I love and I go deep but when I'm tired of that I keep trying new stuff.
The most on point argument ever! I showed this to my brother,
he is starting to code,
I have 8 years of experience and I keep telling him not to give up just because of a big list on job posts
Great message. "imma knock out w/e they throw at me" not only makes you more motivated, but also builds the necessary qualifications and skillset to succeed in you job/ life. After a while you won't even remember the time you didn't know some of the concepts.
exactly
Great message! You won me over with the vim speed run but using your platform to let people know what to actually do succeed in this field is invaluable.
yayaya!
+1 to everything you said, the best thing a junior dev can do is to, explore a breadth of technologies and find out how they work in tandem. Some frontend, backend and devops. This will really help in new teams and interviews.
agreed.
I like the message of “just do it”! And I know this wasn’t the point of the video but what DO you think is the best way for companies to interview people?
i think having a conversation where i know some technical depth about the same topic and we just talk about your experience. I like seeing how much a person knows about a topic. Depth tends to be the greatest identifier for me, at least.
Theo has a good rant about the final part of your comment
@@jupyter5k647 ❤️❤️
As often happens, Prime is the realist and I’m the idealist. This video is the “right advice to get your first gig and start on the right path”
If you’re on the other side and want to make interviews suck less hard, I have a video on that part 🙏
i am totally on the side of get in and try to fix interviews, but there is also a question that must be asked, or is implicitly asked, what is it that you are going to fix and how does your fix fix it? The reality is that I can talk to an engineer for ~1 hour and know if they will be a success or not. But I have also busted my ass for +15 years to gain this "ability." Would I trust a fresh grad to interview like me? No, please, I would expect less experience to use different filters for evaluation that I would use.
i know, very unhot take ;)
who are you
The positivity keeps me going. Thanks dude
yayaya! get it
"have the language and understanding to be able to google and build the solution for them" 100% YES!
yaya
As someone who is currently going through a Bootcamp for full-stack web development, being overwhelmed with all the technologies out there. This helps, Thanks Prime
yaya!! Just get after it, it wont be long before you cant even remember what it was like to not know it all :)
Thank you! I sooo completely needed to hear this precisely now. Perfect!
Love the message, thanks for this! It’s definitely great to see the wish lists more like the general stuff you need for a great job
yaya! having fun making these.
Completely agree. Learning Linux and configuring Vim is what really pushed me to learn more and take more interest in what I was doing. I attribute the vim curiosity to you and fireship actually lol
As an IT professional who has to constantly adjust to new standards, all I have to say is knowing the minimum of something is important. Do you need to know 100% about vCenter? No, but being able to interact with the team who you might need to work alongside is important. An hour a day of practice on any topic you want to learn, will put you above the majority of professionals. I believe it was 30 minutes a day for a year will put you in the top 5% of any given field. That’s insane.
Depends on the quality of training and practice. Any mope can watch UA-cam and udemy courses for hours and still not learning anything usedul
@@plaidchuck that’s usually why I stay away from either due to the quality of content being low since the bar for entry is extremely low
@@plaidchuckthe problem isn't even the udemy/youtub courses per say though of course quality varies, the root of the issue is lack of curiosity and intentional practice. Expecting any course to do this for you when you are passively watching and at best copy/pasting is a recipe for failure.
Yea that’s bull shit
@@plaidchuckwhat are few best "gold standard" resources for learning DSA or other core CS subjects?
I needed this and baba delivered it and I like it. I am in this same scenario. And i am just trying to do it. Will do regularly though because I am in support role and it sucks. It's hard for me so i am spending sometime but as soon as you start getting a concept and try out some problem related to that DS and it will stick with you and you can switch to some other DS and then just continue.
Thanks!!
You got it babe! You have to dig deep and go through things.
I would first recommend making sure you are great at building things, and every day read a bit about algorithms. I don't think leet code is that great.
@@ThePrimeagen actually i am working on a project with node as BE and react as FE. Basically it will generate digital brochures in pdf format. I am taking my time and learning a lot of stuff from that. As soon as I learn go i will switch my BE to it. And i am experimenting with AWS S3 bucket as well.
I try to read DSA but don't spend much time on it. Just a glance and done.
This video is awesome! I feel like the illusion that your interviewer is all-knowing and expects pure elegant solutions on the fly is common yet flawed.
exactly. I often really liked people that could talk through why they did it. I cared a lot less for the "best" solution.
Just had an interview this morning. Got asked leetcode merge overlapping tuples and valid parentheses. Bombed it so badly lol.
rough. I hate those, but not as much as permutations.
Sounds like a Facebook interview. You got the easiest questions man. It happens. Merge overlapping was one of the questions I got that prevented from getting a new grad position at Meta (only because the interviewer English was the worse and his communication was “just do it” as I asked what are the inputs.
This was my Meta new grad onsite only 3 interviews. 2 technical and one behavioral. 3/4 solved and did a great behavioral interview = no offer. Also the interviewer cut off his Zoom and left (never got a second chance as I complained to my recruiter).
I got asked a Leetcode hard during a Jr level interview and the recruiter told me they would only ask easy lol
@@markvaldez8602 gawd damnnnnnnnn. You got fucked lol
@@markvaldez8602 I know it is easy to say... but that was not the person to let you in the door. Apply again and get someone else. I like Primes Iday of going to companies you dont want to work at and interview there. Just... keep... going...Churchill said "When going through hell.... keep going...."
@2:08 knowing the terminology and what to search on your own is the most important skill in my day to day job. That is what colleage supopose to be. Training the brain of young adults to find and filter knowledge without the assistance. (Good luck to all you folks who are struggling to get hired. Keep on learning.)
yaya!
Also don't let college be the thing that teaches you what to search for. Most of industry is practical application of theoretical knowledge.
@@ThePrimeagen I'm trained in "public administration" but have the luck to work as dev. Education helps for sure but with a bit of effort it is possible to fill the gap :-)
"I am gonna figure what they want, i am going crush what they want" has become my motto now a days.
Thanks Prime, I just watch that twitch videos a day ago and it pumped me to take my time to learn things even when I feel I don't have time
This was so cool! i really like this vision, you just changed my year, keep it up!
hio!
I think most of this is true but I also think the missing part is learning, even to an exploratory level, without actively working in that space for a while, won’t solidify the concepts enough. A lot of time is needed unless some sort of refresher is done before the interview, which I highly suggest btw.
CS student here. First I want to layout what my life looks like, I am 23, married (no kids thank god), live on my own, work full-time, take 12-18 credit hours every semester, building a project that is way over my head and feels like another full time job, and i still have time for hobbies, family, friends, etc. Also, a little bit of background on me, I was never the good grade kid or a good student through out my early life. I am now a Junior in college and I am happy to say that I am killing it academics wise, I had a lot of catching up to do the first 2 1/2 years of college, developing good habits, studying techniques that are good for me, and getting rid of the procrastination and bad habits. This is my take when it comes to these "technologies companies request":
- Learning these technologies is not hard, you are just being lazy.
- NO, what you learn in class will NOT get you job ready.
- If you don't code outside of class, and learn technologies/concepts/theory and so forth, then you are not doing enough.
- All these things that feel daunting looking from the outside in, they turn out to be pretty simple and easy to learn once you get to it.
- My advice, stop building generic projects using youtube tutorials and come up with a project that will challenge you, then put together this project with the technologies you want to learn. Only use tutorials to learn how specific components that you want to build. Then, apply your own solution/sauce to it.
Look, at the end of the day, its not easy. I go to bed at 12am to wake up at 4:30am every day of the week, including weekends, but i only have another 3 years of this and then its over (I'm doing a 4+1 for a masters in cs). Yes, there are days where i wake up and i just wanna throw in the towel, there are moments where i feel like I am at my breaking point (gym/running or any kind of pt usually helps me with this). But it is what it is, I have dreams and aspirations which I want to make reality. If you have something you truly want, then just do it.
Now please make a video on "how to use your time effectively", such that someone can learn those things you mentioned in a couple weeks
Seconding ^
have you not applied yourself rigorously to a topic and not made great strides in a couple weeks?
You will never learn enough in a couple weeks. Your best bet is to learn by projects. I learned Typescript+React Docker/Kubernetes Java w/ Spring, Go and Message Queueing with RabbitMQ all in one project for banking/fintech. Coupled with NodeJS and ReactJS which I knew already, I worked on a microservice service environment that mimics what real world work would be like working on multi-language projects and pushing to github. This also allowed me to learn CI/CD pipelines. I "finished" out the project by learning Nginx Reverse Proxy which allowed me to host it on AWS EC2 cloud where I have a Google domain rerouted to AWS Route53 (DNS hosting) and then the Nginx serves my react/typescript build.
My Spring Boot Java app talks to a cloud database in Amazon (RDS --> Postgres) and my Golang microservice talks to a Cloud DB (Non-RDS --> MongoDB).
In total this took me roughly 3 months learning everything but nodejs and JS from scratch. My only other experience was with python for which I did no type of API development. Was it hard? A little bit because you have to code when you do not want to in order to get where you want to, but now, I can ATLEAST hold a conversion in regards to these different technologies and what their purpose is. Now I focus primarily on my weaker points (Algorithm and Dynamic Programming) for interviews. The best advice I can give you is you have to be comfortable being alone and focused on your grind, because it can be hard. If a job wants you to know more than 5 tech stacks and flows at a deep level to get a job, then its more than likely they are looking for a 10X programmer and not someone who is just starting out.
Side note: I have absolutely 0 experience in SWE/Web dev as my current job is cyber security.
@@kofiboateng9181 Thanks for your response, it was helpful! I'm currently looking to get my first job as a web developer so I can later transition into cyber security, quite funny
@@tears_falling I still plan on doing cyber security in the future as well, but I started my dev journey to further my knowledge of cyber security and internet knowledge as well! Can't protect what you don't know thoroughly! haha
Good luck on your journey and glad I was able to shed some light on a possible course of action for ya!
This video is just gold! Thanks for all the advice!
The defacto standard hiring practices are bullshit and I’m happy the company I work for does things different.
For people breaking in we value seeing personal projects and will ask them to explain the technical decisions they made within.
Critical thinking abilities also take precedence over institutional compsci knowledge or proficiency in any one tool.
yeah this is all true. the hard part is sussing out critical thinking. That is why we have what we have now, because its hard. I don't think its the best, I have a method I like, but I don't want people using my method because I think some people are unable to suss out things in the same way.
learning is not a problem, the problem is when people require experience.
Experience is learning. It's just learning that you can't do in school. It's one thing to learn to configure a Raspberry Pi as a server and it's a completely different one to upload a new bare metal search algorithm on a million Google servers. Google will trust you with the latter... AFTER you have acquired the necessary experience to do it safely. Why would they let a rookie crash a hundred billion dollar search business? :-)
@@lepidoptera9337something so simple, but it makes complete sense. I think as juniors, we have a sense of entitlement to a job we realistically aren’t qualified for and feel too good for that IT Help Desk job because it’s no “culture” or ping pong tables and 6 figures. Nobody seems to want to start from somewhere anymore. We just want to get started with the big boys lol
Experience is Learning.
@@lepidoptera9337they can give said rookie a smaller and less risky responsibility and he or she can learn the ropes and eventually become a full-fledged developer. But no, keep making excuses for not hiring juniors and then cry about not having enough developers to work on your projects.
Yes, but the problem is not the recruiter. Recruiters will choose the best candidate, that's their job.
If there are more available jobs than there are candidates, then finding a job will be quite easy, even without experience.
But sometimes, because of the economy, there will be more candidates than available jobs, which means that some people will be unemployed no matter what they do. But that's not the recruiter's fault.
That's definitely a bad system (because you can't say "No company needs me? Great, less work to do!", and instead, you usually say "I have to find something to produce even if there is no need to produce anything more"), but if you accept it, then you have to play by its rules.
Bring on you portfolio the history of you solving problems. New job won't have the same problems, your ability to solve them is that's valuable. It may even be worth to go for a worse more junior job for a while if it allows you to build up your knowledge in the area that you are interested in, or contribute to open source and make your contributions publicly visible for future applications. "I did stuff" is always more impressive than "I know stuff".
i did stuff >>>>>>> i know stuff
New sub here from the Fireship collab. Love the no-nonsense practical approach 🍻.
:) Thank you! I just try to be an engineer and that is it. Not trying to sell you anything, just give out advice from a possibly skewed perception :)
Dude love your content and how real you are.
yaya. ty
Thanks for the video! I really like the approach your latest videos have, and how with your experience you can help us get our first job in technology. by the way, the meme is far the best of the video
yaya
All of that is in every BSc in CS, the problem is, that they require several years of working experience in these technologies. So getting an entry into these companies is more difficult than it has to be.
Great advice Mr. Prime! All about time in the saddle!!
TimeInTheSaddle
One way to look at it is that everything is grids of data. Maybe start by working with Excel and spreadsheets and go from there. For front end, layout colored boxes for a while with CSS.
I largely agree but the issue I have with the wish list, is that resume's are often automatically filtered based on those keywords. You can pick the right skills to learn. Can you confidently defend your skill in tech X though? If it's not on the resume, you can be filtered. If it's on there, you need to be prepared to defend. Resumes which just list tech after tech start to look like BS.
yeah, that seems about right.
Not a software dev here, I'm a DevOps/SRE/integration engineer, but in my experience actual sane employers who are really in need of a (mostly junior, but not necessarily) software engineer, or a sysadmin, or an SRE guy, or whatever similar position really, and aren't MANGA so that they have a huge pool of extremely talented people to pick and choose from, are willing to look past not having some particular skills and experiences if you have something similar in your portfolio, or can demonstrate the understanding of why those skills are needed, and/or know and understand how the required tech works under the hood at least on a high level, and don't underestimate the significance and apparently rarity of an arcane skill of googling, whatever that is. If you can show the ability to quickly figure out the problem and how to solve it, little else matters really.
In fairness their are some completely unreasonable job requirements, the one I always remember is someone wanted a junior Dev with 15 years of experience in swift, yeah, 15 Years in swift
This is totally true.
One thing I want to add is that every good engineer that I know of is a T shaped person.
T means having a breadth amount of knowledge and being specialised in one of them hence the T shape.
Sure I don't need to care about Docker or Kubernetes because of our DevOps team takes care of it.
But knowing these "irrelevant" topics helps me to understand the process and therefore I might be able to fix a simple error myself so I can ship faster.
Even if you don't need specific knowledge anymore most of the concepts/frameworks you learn help you to better understand new things because there is almost always something that can carry over to the new topic or give you new insights to what you already know.
Thanks! I've been searching how to get it and this is brilliant :D
I think what sucks with learning hard things is, you don't really know when it makes sense. Like for me, learning is 100% plateau after plateau. It's each one of those a-ha! moments that cements an idea for me, and sometimes it'll just randomly happen when I wake up, or when I'm taking the dog out. I guess I've kind of shifted my mindset from chasing "knowing/understanding" to "waiting" for my brain to click everything into place.
Great wrap-up. As a savvy software developer, I'd say if you're passionate about it, dive deep and code your way through it.
I agree a lot with Primegen that you should just go and learn the things they list if you want to work there. But it also depends on the position; If the things they require and ask you about isn't related to the job that they're hiring for, better avoid that company as it usually means that they don't know how to do interview processes.
Super based take. Looking at all the things i have to learn as an exciting opportunity to become a real professional is exactly how Ive stayed motivated to learn. I got a STEM degree but i got my degree in biology. And as much as i wish i could go back and discover my passion for programming and switch to computer science i think the most valuable thing i attained with my degree was actually the mentality i developed around learning very difficult concepts. Once you’ve done it in one area, you understand the process, and have one huge takeaway from the experience. NEVER confuse recognition for recollection. That lesson has kept me far more aware of my actual abilities than almost every collaborator Ive had on projects, until i came across my current collaborator that has the same mentality as me. Prime is dead on here
all the things you listed in the thumbnail are awesome. those arent things i have to know those are things i want to know
"Look at life as an adventure, not an injustice". Forget engineering, or even careers, this is just good life advice.
Good stuff here!
I think one thing that most people tend to forget is (I quote someone, don't remember who it is tho):
"People overestimate what can be done in a day and understimate what can be done in a year"
I mean, it can seem daunting at first when you see all the stuff you need to learn, but guess what, you don't have to do it in a week, just put in the time and you'll be very surprised where you are in few weeks/months/years.
I think this is one of the best advice out there, nobody knows it all, but you gotta get good at solving problems and know how to look for useful information quickly
yaya!
What a godly mustache. This channel makes me so happy
Thanks for this video. I’m gonna apply for the startup. Yayaya.
GET IN THAT STARTUP
They only want developers that have experience and or people that can code projects that can run on their own. The kid that made Million.Js is NOT hunting hand to mouth for jobs. Alot of these techs as a regular everyday dev you dont have anything to build with some of these things. You only really have access when you work at a company. I jumped shipped and going into backend.
Just know that you have changed peoples lives and given them hope...I pray for health wealth and happiness of you and your family. Thank you for these gems.
dude, thanks! this was a nice note.
wow, you just gave THE mindset for all and every things guys that we want in our whole life:
We can get all we want and almost all we want is free, but cost something.
How to 'pay' what you want is really a simple decision over: give $$ or give your time/patience/something inside you.
Thank you !
:)
I hate this take, because I’m dumb and lazy
Screw IT, pay is a joke anyway. Why would anyone even try... people who love tech can build indie projects and save their minds of lunacy.
Yes, you can, but who is going to pay you for another version of Tetris? ;-)
Looking forward to your future algorithms course on Frontendmasters
very excited
I'm working on a test project for a junior front-end position right now, and when I got the assignment I didn't know half of the technologies they wanted me to use. Three weeks later and I feel like I know them like the palm of my hand.
Modern technologies usually have pretty good documentation and "getting started"-type tutorials, so just learn it, man. It's really not that hard if you give it enough or your time and build a couple of practice projects with them.
Read about 'four stages of competence', it is 'natural' to think you're more competent than you actually are when starting to learn a new technology. Even when knowing about this I must admit I have multiple times overestimated my competence, or underestimated the time/effort I need to learn.
keep crushing it kris.
The only thing that should matter is your curiosity and the pleasure of understanding. Everything else can go f**k itself.
If you can't easily retain 40 years of experience and expertise in one if not two professions, then you never had any curiosity. ;-)
2:20 thank you for mentioning this. It's not about being a master in all these technologies, but it's important to at least know something about those technologies in order to be able to have a conversation. What they do, why they might be used and so on.
Just being curious and learning about basics about many tools and technologies has allowed me to make better decisions in my work, remember that X tool exists when I have a certain problem or just being able to google stuff better because I know something similar might exist and might push me in the right direction. Curiosity and thirst for knowledge is really valuable in this line of work.
"I'm gonna figure out what they want, and I'm going to crush what they want" .... I live by this!
You don't need to know anything if you still don't know Git. So my number one recommendation to anyone who still feels "kind of beginner" is to learn Git before ANYTHING else, just start with raw text files and version control them as a practice! And become fluent enough in it so that you feel "confident". You don't need to master it all at once, you can't, you don't need to, and you shouldn't. After that start doing a quick project such as a todo list AND PUT ENOUGH TIME ON IT, remember, "commitment and consistency is the key".
Also here's a quotation I've extracted from this Primeagen's video if someone's taking notes:
"Be able to practice the art of discussing your ideas in a situation which it's just tossed on you, because most of the time interviewers are looking for someone that can discuss ideas and come to solutions, they're not necessarily always looking for someone that's going to give them the most pristine answer in that moment, and they're often not looking for someone that knows all the technologies that they've listed. ... I would highly recommend looking at life as a challenge not an inconvenience, and to look at it as an adventure not some sort of injustice or ill will towards yourself."
> "You're handed the exact checklist that you need"
Doesn't hand me a checklist.
This is the realistic/honest take. It wouldnt be fair if employers expected you to be great at all of this while paying you junior salary, but usually they just want you to have a broad understanding and having played around with it a little. Unless you absolutely want a job at one of the Big5/FAANG/MANGA/whatever the bar is really just at "did you bother to look up the core infrastructure tech every major company uses and did you use it enough so we dont have to send you off to weeks of training before we can even see how you are at your main job". I am regularly amazed at how many people come out of university and cant write up basic SQL commands or a simple Docker config. Few jobs today are just coding within one language and one framework. I feel like thats what FullStack usually means: you should have a good idea how most of the stuff every company uses works and be really good at 1 or 2 of them. And that is achievable. And who knows, you might actually start using those technologies as auxiliaries to improve your main-proficiency.
Thank you for the inspiration!
The problem with fundamentals for me is to how to make them FUNdamental - if i don't initially get WHY i would need something unreasonable on my resume, it is just so difficult to learn. And with deep stuff it's not easy to see unless you wait and think about reasoning of these requirements.
So yea, considering requirements and skills required not as "requirements", but as a blank checklist of things to explore, helps a lot with making it fun. "Ok but WHY i need to know what's a hash-map? Ok but WHY they want to use Docker when our dev cycle is already in 3 VM's?" etc etc.
Having and finding energy to wonder is a whole another problem, so good self-management and taking care of oneself is kinda the most crucial skill any person in any field could have. The final boss is not your interviewer, it's you.
As usual, the real question they are asking is "how to I learn the bare minimum to get a well paid job where I would be doing as little as possible to get paid".
Why would anyone in their mind hire a "software engineer" who doesn't like algorithms and technology stacks?
Would you go to a doctor who doesn't want to know basic biology?
best progrmmming channel hands down
i like these meaningful short videos.thanks
yayaya! that is the goal
Pretending a way of interviewing and assessing someone skills as necessary for the job when its not, still playing into that game....
There's nothing wrong with inconformity, the fact that there's this hairbrained process to get a job will lead to people learning everything there is to know, asking themselves, why do i need a job again if i can do everything myself.
It took me about 2 months to learn FFT, its a bit embarrassing it took so long but its true. I mean to really understand and know how to use it with other math, It was sooooo worth it, the coolest thing in programming.Those algorithms you will learn on University. it will take like 6 week. Take you're time and understand it deeply. Those algorithm "are used" all the time. You need to know them.
Thanks & broadly agree, esp with the point that you're getting a checklist which you can address directly. For specific techs like Docker, frameworks and even infra, you can spin up projects (often for free) easily and get real exposure to them.
I think the hard part applying this to requirements faced by non-jr but non snr candidates when they get the bad luck of not having exp at shops with appropriate tech set ups e.g. using a range of databases for different types of solutions in a monolithic codebase with one big postgres instance. Not sure you can hard work yourself into experiencing a more distributed architecture, or managing challenging projects.
Would like everyone's takes on how they recommend tackling this scenario!
This is true. You cannot possible craft a solution that met needs while having 10k customers to scale to 1million and find all the wrong decisions you have made. That is experience that only come with tears and time :)
Love you Prime ❤
love you too
Good for us you are going to do a new Front End Masters course on algorithms and data structures :) Yes? If so, when? :)
you are a great motivator sir. I enjoy your no bullshit advice
yaya
tldr: good things take time
Thank you bro!
yayaya
The editor account you've mentioned in the description (That account doesn’t exist)
oh snap! He changed his name and I thought I updated my defaults.
its twitter.com/FlipMediaProd
Inspiring! Thank you.
Honestly this is what i recommend: Looking for a job? Learn a bit of everything and find information what is important to go ahead and learn. Just coding for for fun/hobby? Well learn what you need to learn only and do some research because you might find something that you prefer over what you are doing right now and it will also give you new ideas of what you can build with those new tools your using.
"No, I don't think it's fair, but at the same time life is not fair." Words of true wisdom. Great talk!
Pretty sure most (young) adults know, and have experienced, life isn't fair, calling this 'true wisdom'..
but people think "it should be fair." and that is the problem. Life isn't fair is a statement of absolutes in a sense, it will never be fair, and you shouldn't assume its default state is fair.
When I get a job I would feel better if I at least half knew what I was doing. I find that motivating. There is a lot to learn. Isn't that the beauty of the industry?
i feel that way. I get super motivated by knowing there is more to learn.
Hot Take: all SWEs and aspiring ones should make an effort to share and publicly shame stupid job postings -- for example "Must have 15 years experience in Golang" ... take your pick.
hah, i just want someone who has been writing Rust for 17 years, why is that a big deal?
@@ThePrimeagen tha'ts me.. in spirit. (blazingly fast spirit)
TBH, does companies require all this stuff YES. Do they really need it for one position, NO.
My man's mindset is on point
just trying out here tom.
@@ThePrimeagen You're doing good work
The real skills of software engineering:
- Always be learning
- Solve problems
Languages, APIs, algorithms, design patterns, OOP, etc are the tools. At some point you know enough, you can "learn whatever you need to" on the job. But until then: take your time, learn *and apply* each thing until you actually feel like you know its strengths and weaknesses. Then, repeat. A career in software engineering is doing this over and over and over again. So if it is unfair to know all this to get past the interview: it might also be a sign that this is a career you'd hate... And that's okay: it is more important to learn what things you don't like. And SE isn't the only role in technology or the only job that writes code... So maybe there's a different role that you'd like even more.
learn java ;)
@@RR-et6zpbecause of Java i almost have not gotten liking programming
same, how did you survive? @@emptybottle1200
OK but learning all of these things takes Time. Time which most people do not have. Since you can't devote much time to learning since you have to find a job to pay bills. I no longer think learning to program is something meaningful, all of these absurd wants and needs of companies have made it something I hate. And I loved programming.
That's why you need to get experience on the job. Nothing can replace that.
...you are given a requirement list to dunk on to get a 6 figure sallary.
Developers in third world countries with the same list getting a max of ~40k / year:
👁👄👁
This guy interviews, also great video!
ty yoni
So basically put in the hard work. Thanks.
I'm not getting the taste in Web Dev. What should I do? I'm following Machine Learning alongside AWS. Is there something else I could learn to get into SDE
Great Video, Thank You!
I got an interview for an internship and it went very well, I'm gonna use vim as my IDE, if they hire me or fire me it's your fault Prime, love from Serbia ♥️
Gleda se Primeagen i u Srbiji =) Pozdrav brate.
What kind of data structures are we talking about? I am halfway through the web developer bootcamp and the only CS term I know is "compexity". Dont even know where to start.
there is a book called Algorithms on Amazon for ~$120 . its my personal favorite
here is my NON AFFILIATE CODE (because i really rec this book).
www.amazon.com/Introduction-Algorithms-fourth-Thomas-Cormen/dp/026204630X
When the going gets tough, the tough get going.
yayaya
That was helpful! Thank man
I have a confidence issue where the basic understanding often times doesn’t feel good enough and I feel obligated to know everything end 2 end which just leaves me feeling like I actually know nothing. (When I probably now more than avg)