In a technical interview once they ask you to demo your skills you just open Jira, create an issue and plan a new sprint for next month with lots of story points and all that bullshit. Easiest way to "win"
In most professions it is assumed that you go to work, do your job, then leave work and stop doing your job. How many lumberjacks fell extra trees on the weekends? Software engineering manages to impart a mentality on a lot of people that they need to be learning and writing software all throughout their free time. Of course it's good for career aspirations, and having OSS contributions is great for your CV, but putting a lot of pressure on this leads to burnout. After 8 hours of programming during the day, the last thing I want to do in an evening is boot up a computer and do more programming. Basically what I'm saying is when looking for jobs, do all that you can, but outside of that, make sure you're living a life that you enjoy and can sustain happily. You don't need to give every waking hour of every day to more software development
This whole "must code 24/7" mentality is more prevalent with junior programmers I think. When you are still new to the game... but if you've been doing it for years you get pretty tired of the constant burnout and the junior developers will get to that point too eventually. And this whole mindset that you should know 100 different technologies is really stup|d, how do you get to be good at anything if you are constantly having to learn new things? Improving your skills is always great but learning something completely different every other week isn't improving your skills,
I feel like the lumberjack might go home and still woodwork for fun, maybe making furniture is a Hobbie. Not felling trees but still in that area... idk I'm also high af
@@gamereactz 'woodwork for fun'? Is that code for banging his wife? If that's the case, then yes, I do agree that's probably what he is doing in his free time
I have made it to round 6 of an interview, passed the final round. They told me I did everything they asked, just not well enough... Interviewing is SO much worse than the actual job and by far the worst part of being in the tech industry. There is zero acknowledgment that some of us just struggle to vomit up technical info on the spot and getting rejected from life changing jobs, where you are OVER qualified for the actual work just because you answered a question without using the proper vocabulary. I have even been rejected because the interviewer didn't like how I moved around within the browser IDE that he linked me to for the interview.... even though I did the ACTUAL work he asked for and with time to spare... I enjoy the technology, and I enjoy working with engineers. But I LOATHE basically everything else about the industry so much so that I am only in my 4th year and I am desperately looking to do ANYTHING else with my life.
This shit about everyone "needs" to code in their free time in order to get a job needs to die already. Its such terrible gatekeeping mindset to have. These kind of people who spend 80 hours a week programming but never go outside are crazy imo. They can sit down and tell me about all the side projects they made in some obscure language, but ask them to sit down in front of a client and condense what they want into an understandable ask and they are like a fish out of water. Now don't get me wrong I like learning new concepts, but not because I have this anxiety that I'm not always up to date with every new fangled JS framework. Not every person sees Programming as a hobby for some people it is just a job and guess what, that's fine guys...
Can't agree more to the "Try designing a course" part. I joined my current company about a year ago and noticed they still used JUnit 4 for testing. So I took a leading and educating role about migrating our tests to JUnit 5 and I have learned a lot in the process about some "corners" of JUnit 5 I have never had in consideration before and teaching my colleagues has helped me dive even deeper in the matter. It was also so much fun, that I consider contacting my alma mater if they are interested of me hosting some lessons.
How did you get that leading and educating role in the company. Do you just ask your boss if you can do that after you noticed that problem or how does that work? I mean initially you were hired to do something else... And when you had that role, was it like your main thing for a time to do the education or was it more like a smaller task next to your other main tasks?
@@DAD1996W We have one day every other week were we can pursue any kind of improvement of the code we can think of instead of working on our regular tasks if we want to (We call it Technical Debt Day). So initially I took that opportunity to produce some small example tests featuring JUnit 5 (esspecially parameterized tests and how to multi-thread them for shorter test cycles) and then presented it to the team and the boss. As this was only a kinda vertical slice it took 1-2 workdays at most to prepare. The team was onboard immediately and my boss did not need much convincing thanks to that. So I was given some time to properly research the methods of migrating tests and developing a proper architecture on how we would write these in the future (esspecially parameterized tests). After that I presented it to the team, making some adjustments due to their input and spearheaded the first few migrations. The mentoring was more of an ongoing on the side thing and as I am blessed with a good team it did not take long for everyone to be able to work with this without my assistance. Due to the scale of the project the complete transformation is still ongoing , but every new feature is now tested with JUnit 5 according to the specs I worked out. Needless to say, I got a sizable raise as a recognition for this work. Granted, not every company / boss will give you such an opportunity or even give you the recognition for your work, you always need to find what works best for your environment.
I disagree with almost everything being written here. Remember, companies do not know what they needed until they have the experienced people, this is very common. Having a specialization (or several) on top of practical experience is MUCH better than knowing the latest gimmick feature/language/framework. We live in the stinking dark ages of software development and a lot of it is 100% the result of people just chasing the latest hype of nonsense that tries to reinvent the wheel. Somehow they nearly always end up with almost square ones. Instead of developing the core skillset that is universally applicable. TLDR Incompetence generates insecurity! Insecurity initiates the move to jump into every new hype! Jumping into every hype never gets things done and blocks developing your core skillset as all the energy goes into retooling/learning things that are obsolete with the next hype. It is mostly outside interests, not the interest of the professional developer, to jump into new hypes.
Example conversation I had yesterday: > shake hands with guy at church, he asks what I do for a living > tell him "I write software" > "Oh, do you do side projects? I need someone to help me with the last mile of some scheduling software." > "Yes, I do side projects. Here's my email." This is on top of 2 other side projects I have going, plus my 9-2-5. Everyone needs software. Gotta leave the basement to find out what problems they need solved though.
"No one learns more than the teacher." At least, as long as the student is learning something. I swear some teachers are diametrically opposed to learning anything.
I don't agree with the advice to always learn or code outside of work. Programmers should have a life instead of sitting in front of the computer in their free time. I personally hate the cult of "constantly learning some new technologies". Technologies come and go, if you don't need it for your actual day-to-day work (which would mean you should learn it a at work BTW), it's a waste of effort as it will probably die in 5 years or sooner anyway (especially in JS world).
This take is fine. It’s just that there will be people that are willing to take some time out of work to learn new technologies due to their own interest or to keep up. They will most likely improve faster and become better than you and therefore be more likely to be selected by companies over you. I don’t disagree with you. It’s just that this kind of mindset comes with the acceptance that people that are willing to put in the work will simply just become better than you and therefore be more likely to get hired over you. Learning the technology at work is ideal situation but companies will always prefer the candidate already knowing the technology coming into the job.
Coding in your free time has nothing to do with a healthy living experience. Its about being ahead of everyone else so u can continue working or find a better job.
I never ask technical question as in "write this algorithm" It doesn't prove anything, hell I admit that I haven't implemented an algorithm or std data structure myself in 20 years, I use the STL and the STDLIB. I just ask what people wrote themselves, what was challenging how they solved it. And I give them an example of a current issue we are facing. Last tech interview I did took 10 minutes from my side and I was like: "yeah, I too love this guy". I asked him one insight question that I knew he had no experience with, just to see how he would find answers -- what to Google for is more important than having that knowledge in your head. Because sooner or later, you need to do things you've never done before. So I was taken with this guy immediately. In the past we had some tech questions and especially those that I knew people couldn't answer. I want to see if they take charge. If they say: "Okay I don't know can I use a computer to google it? Or can I grab that book of the shelf and browse through it?" Then I knew they were good. When they would just walk in circles (and not even writing compilable code just pseudo code or describe the process of solving the question) then I know that either they need mentoring or perhaps isn't the right candidate. One guy got so angry and shouted: "This is INSANE NOBODY KNOWS THIS! WHAT DOES IT PROOF?!" And my manager calmly said: "It proves if people are willing to discuss this on a professional and friendly way, anymore questions? Otherwise I think we know enough" :D
Thank you for mentioning this. Currently looking for jobs and the scene is new to me, far more than programming itself is. So seeing what's expected of me is very helpful.
@@Axlefublr My advise is (as Prime's) is to communicate. It's okay to say: "I don't know, but..." and then describe how you would go about solving the problem as if you were employed there. Employers and in my case Customers (I am freelance) want to be sure that when you are in that seat, that you can take away their worries. One tip for interviews listen to their unspoken worries or challenges or flat out ask them if you don't pick up on them. A question like: "What are your current big challenges or problems? So I can see where I can fit it and help out." Is a great thing to ask! It shows that you want to jump in. And what my former employer said before I went freelance was: "It is not what you know, but who you know." So in other words, if you know something that works for that company ask if they have openings and put that person forth as a reference. I noticed when i worked at IBM, that majority of people working there were the sons of the previous generation. And my current customer, I am working on a 4th different project. The fact that you know the organization is a leg up.
@@Axlefublr Wow! You have a lot of content on YT too. You have more videos than me and I started 2 years ago! WOAH! Be sure to list that on your Resume, the interested people will have a look and see instantly you are a linux power user, you actually love to also develop your skills in your private time. That's definitely a leg up and especially for your first or second job when you do not yet have a lot of job experience.
spot on. Communication is key. I always advice people heading for interviews to not be afraid to look dumb. The technical aspect of the interview is just the setting, the actual assessment is how you're going to be working in solving problems with the team. In my interviews I don't allow candidates to google though, I ask them to treat me as Google and ask the questions directly to me and I provide the answers accordingly. That way I can assess how they're thinking of the problem and how they would be googling for the answer.
Yeah, I agree on this. I usually struggle a lot with technical interviews even though I'm not a newbie. Often interviewers will ask me questions that I know the concept of but not the technical terminology, I lost some job offers due to that and I always wonder what if you find a person who knows the concept but doesn't know how to use it properly, and what if you find a competent candidate who doesn't know the concept but knows how to use the tools and knows how to fix things? Who's more valuable there?
I wouldn't say I necessarily struggle in the interviews on the technical side. The hard part for me is in the socialization as most technical interviews tend to copy the google interview model, which optimizes for the "Smart Extrovert". As an introvert by nature, that takes a lot out of me. I'm more used to solving problems in my head rather than talking it out, so the whole interview process takes me out of my most optimal form.
That's a really good point, and probably one of the reasons I did better in the technical interview for my current job than some previous places I'd applied; it was a timed technical problem that I could do in my own time, rather than sitting and trying to explain my thoughts to someone while I panic and second-guess myself.
for the bubble thing, I would guess it has an "on mouse up" on the content wrapper, so when his pointer went up outside of the container it didn't get triggered
My guess is that when you drag it outside on the beginning it ends up selecting something else you can't see, and because that can't be shared it blocks it from making the share bubble.
I actually disagree about not applying for jobs and instead of waiting to be approached by a recruiter or hiring manager. I've been on close to a hundred interviews over 25 years and I've only ever had luck when I was contacted first. It seems to me when that happens the people have already decided your background might be a a good fit and they want to interview you in order to validate that assumption and to sell you on the company. While when you make the contact they are looking for reasons to eliminate you from consideration. Also, I've not once been asked to write an algorithm during an interview.
I had a similar experience recently. Handful of targeted applications and one interview, then I took the job. We each knew I matched what they were looking for pretty closely. I’m not a web dev by any stretch, though, so I wonder if fluidity in that particular labor market makes it harder.
I still think applying for jobs aren't like......getting job immediately but you will get noted down like a reserve unit. If job opens, they will check the reserve and see if you are available.
I'm kind of weird in that I depended on Craigslist for a long time for programmer jobs. Yes, I know that place is bottom feeder central. But for a long time I never had any luck with recruiters that approach me, or other job boards for that matter, so oddly for me Craigslist was like the old faithful that never let me down. Like an old ugly car that I know will start. I know I should be going to better places and started taking it as a sign that my skills aren't as good as I first thought.
Programming isn't my profession (I write music), but I've never gotten any work by "putting myself out there" and applying for jobs. My work has always come from ""networking"" (ie, old friends, people who I've worked with in the past, people who are familiar with my work). In an interview, it doesn't matter how much prior experience or expertise I have, I've always been treated like a child, and inevitably get interviewed by some jackass (like the one who wrote the article) who thinks that they're the Gordon Ramsay of their field, and think that they've gotten successful hiring down to some magic formula. I suppose it's a personality issue on my part, but I have an extremely difficult time showing any enthusiasm or respect for people who are condescending (consciously or not), and who want to make me do pointless artificial busywork or meet some artificial arbitrary standard that has no real bearing on the actual quality of my work. My patience for it wears thinner and thinner as I get older. However, when you're contacted about a potential job, it's always "oh yeah, Steven's cool, he's a bit eccentric, but he can work miracles, you should have seen what he did on xxxxxx, let's take a chance and let him work on xyz and see how it goes", and it almost always goes well, because there's mutual respect there. Which one of these situations do you think is going to go better?
If there's one thing I'd take from this video; it's teach others what you know well, generally your effort is paid back though it's best not to expect it, but you will also reinforce your own understanding. It's a great win-win.
That's how I got my last job. I had my CV on the AMS (government service for workless people), but didn't actively do anything. Got called by a headhunter at 8 in the morning and scheduled a meeting. After meeting the headhunter, they arranged a meeting with the employer. It was a delphi job with some UI dev. I forced my way into backend, introduced go, d-lang and rust into the company and in the end, we were even trying out rust for cross-platform. In the end, I'm never gonna be a coder that treats things as "just another job", I'm gonna push back on bad ideas, I'm gonna tell seniors and bosses if I think something is wrong, because I'm not a code monkey. I think of myself as a professional and it's my professional duty to make sure bad decision are thought through (bad decisions are fine, if people know what they are doing and why).
Been on the job hunt since January. Well over 150 resumes sent out. Probably closer to 200. Out of those, I only got 1 interview. How do you make a network if you never have had the chance to network? Do I start adding random people on linked in?
Also be open to moving around. If you can't find a Front-End Developer role then try QA Engineering or DevOps. You probably have the skills, or can pick them up super quickly. Itll also you get into the company and very close to the dev team
I have found in my personal experience, I had to grind and find my first position -- advanced and advanced within that position learning and taking on new tasks (smaller company). Now I got people reaching out inquiring without me applying to those positions.
I finally got a job today (not programming unfortunately) after I applied for 120+ jobs in the last 5 weeks. The jobs were in many different fields like comp sci internships, data analyst (entry/junior), junior dev jobs, restaurant you name it.... Even though I have about 10 years experience in restaurants and some retail experience most of the jobs I applied to just didn't want me because I have an associates degree in math now (finishing up my BS in comp sci at a university).... it's ridiculous.
I'm currently looking for a job and it's the first time since I started coding professionally (10 years ago) that I do it without networking and gosh it's harder than I thought.
That thing in the wallet is a Dutch invention called Secrid created by Rene van Geer. When we were the first nation to put NFC into their bank cards to pay without pin number, that company was like... Maybe you ought to put that NFC enabled bankcard into a Faraday cage. You now see Ridge Wallet but that basically is a patent of the Secrid. I bought SecrId the week they came out. My customer is a bank, I am on my 4th contract and every time you leave they also give you such a cool wallet. So my mum and dad now also have one (safeguard my inheritance :P)
The appeal to put me off. Whenever someone refers to a "modern web application" I automatically assume they mean really low quality experience, really high complexity implementation.
I believe communication is a huge factor that employers consider while hiring. I had a technical interview where I did not know the proper function required to perform a specific action, but I knew what needed to get done for the program to run as intended. I asked the interviewers questions to confirm I understood the assignment and I walked them through my logic and understanding of the problem. They understood that I could easily finish the program despite not knowing the specific function because they heard me walk through the problem logically out loud with them. They get insight into your problem solving skills, communication skills, and technical skills in one fell swoop.
I havs a strong understanding of data structures and algorithms, I just can’t focus in technical interview. I feel like I lose half of my IQ from being put in the spot
What's wrong with deprecated? It's cool, as long as features remain available, receive security patches and you get the backward compatibility. I don't like the new 'meta' full stack framework just to make a GUI trend, but React has been a pretty stable and backward compatible library so far.
Regarding the bubbles, I’ll bet they did a mouse up event in the p tag or a container that doesn’t include the margins, so when you end your mouse click outside the text it doesn’t bubble
All this gatekeeping bullshit does is make you feel shitty for not getting a job in a market where getting a job is actually hard, companies are seeing this and going "fight for me you idiots", we should have more comradery with our fellow workers.
I can second try writing a course. I've been tasked to do inhouse courses to onboard new employees in my own field (in administration, not programming). It's both amazing and scary how much you learn or find out you didn't know that well.
I think the thing that strikes me as someone early in my career is just how much stuff there is to know. Nobody is going to know all there is to know about software. Some people focus on data structures/algs and trust you to be tool agnostic. Some people want 3-5 years of the .NET stack out the gate. Universities and bootcamps then have their own group of focuses. I think this is where getting into open source and networking is also a big factor
Even though I agree with everything on this video, I have to nitpick with "no one cares if you can't solve X leetcode problem". There are a few companies that I didn't get a job because, according to one of them, I "couldn't solve the [hardest] leetcode challenge [you'll ever see] required for this job". It was for a mobile game dev company. Nowadays I have a job doing much harder stuff than what I'd be doing there, and even still never ever had anything CLOSE to how hard that leetcode challenge was. Dodged a bullet, sure, but being unemployed during that time was rough.
I'm a hobbyist programmer atm. All I use in my code is vector, smart pointers, and map, and it's absolutely possible to program a video game without knowing *anything* about data structures.
ACM competitions have much higher complexity than leetcode problems, so doing ACM is like doing leetcode , but on even harder level. That’s why I think you are doing well on technical interviews without practicing leetcode. 12:04
16:50 I feel the same anxiety as you do when I scroll youtube, insta or linkedin to get out of it i just use them in browser but I still feel the anxiety (like a big burden on my brain), its really hard. I could feel you when you said it
To be fair, if you have done ACM Programming Challenges in college, you already have practiced Leetcode. Since Leetcode and all other programmig interview sites are derivatives of the OG programmming competitions.
Yeah, I don't believe anyone can be good with LeetCode style interviews without practicing unless you are super smart. Just doing theory on algos would just lead to the "illusion of competence" since you never test your understanding
"[..] the biggest issue with the current education system is that it teaches people patterns to memorize rather than understand the actual process" - Ironically, my issue is the other way around. I udnerstand the solution, then I find out it has a name. Now I do know and understand the important ones, but my process was reversed. Because I started as mostly self-educated (reading, sure but mostly practice). 15-17 years back, there werent any real programming school studies in my country. It developed to where its now while I was working and learning. But I dont mind, because its the concept what you need to understand about design patterns, so you know how and when to apply it and not just willy nilly. Design patterns are a solution, if you do not have the problem, dont use it or you'll introduce unnessary complexity (=> error prone).
I hate the advice that getting a job should be through people in your network. It's easier to get a job through people in your network, but you can develop the skills and the salesmanship that lands jobs without it. I've had maybe eight jobs in tech and one came from people in my network. I would never discourage someone from relying on their Network, but if the person giving you advice has primarily relied on their Network then don't take their advice. Relying on your network is the easiest part of the job search but it requires having a good Network. Anybody who tells you that the most important thing is to rely on your network is making the assumption that your network is good. This is a bad expectation. Most people's networks are not good during the times for which it is hardest for them to find work.
A lot of companies outside FAANG don't go that hard on DSA questions, and instead focus hard on system design, databases, design patterns, and "trivia" kinds of questions where programming knowledge/experience with a specific stack counts. These questions can run the gamut and unlike Big Tech, they're not standardized at all because every company/interviewer is looking for a different set of specific things. If you're goal is just to get into Big Tech, you can do that with essentially just DSA, however, most SWE's don't work in Big Tech and won't ever work in Big Tech. Also, if you come from a non-traditional background (e.g., math/physics to software) then good luck putting that DSA practice to use when you won't even get a chance to interview.
Never underestimate the power of networking. Got my first ever Developer job from a businesspartner of a guy who was recommendet to me by the owner of a business I had an Internship at. As time moves on, It seems to get harder and harder to put yourself out there though. Weither if times have changed, the market became more saturated or if it is just because my introvertedness became worse I can't tell. 12:40 : Partially agree. Knowing how your tools work is important. But similar to how you don't need to know every screw in your car to drive it, you also don't need to know every minute detail inside your tools to get going. It is more important to know how to use and configure them right. Rather than how they exactly function. 4:15 : The whole "Bubble" thing seems to depend on where you release the Mouse. Outside the text == no bubble.
Out of uni, I took a total of two job interviews. First one: "Where do you see yourself in 5 years?" "What are some design patterns" Second one: "What do you do in your free time?" "I play with arduinos" "Hired"
I cant do DSA, had a two year education, did not finish high school, did most of what he said to not do and still landed a job, all I did was try to get really good at JS/TS, React and writing clean code, and deep dive into what I thought would be relevant at a job.
Disagree on the "switching up paradigms". I feel like way too many people try to spread themselves too thin. Making value a lot of the time is about creating a niche for yourself. People that are unfamiliar with actually creating impact think that knowing more random stuff is valuable. No, knowing one thing very well gets you the job. Expanding after that helps you rise, but does not get you that first job. I would definitely not recommend someone trying to get their first job to learn frontend and backend in depth (maybe a little bit).
I think leetcode is more prevalent now and especially if you're entry level. Of course you can get by with algorithmic and dsa knowledge but leetcode helps to think algorithmically specifically for the types of problems new engineers will be typically asked. You get out of what you put in, as well. You need this kinds of skills to just pass the basic minimum, then your more practical knowledge shines through in the rest of the interview.
Super strong data structure will help alot though. But I agree that leetcode is basically the interview now sometimes as companies copy and paste questions from leetcode. Interviews will and always be a performance and not an actual demonstration of ur skills. At least not the first few rounds in a 7 rounds interview process….
i always saw it as a an equivalent to doing hw for a dsa course or practice problems. Its kind of like a calculus course. I can learn that an integral is the area under the curve and learn how to integrate an equation, but it also helps to also integrate a few equations to hone the skill. I think the same goes for dsa and leetcode. For the course you can learn about a linked list and implement it, but then it helps to maybe study and do a few practice problems using linked lists. Once you are out of college for some time I find that youtube and leetcode was a good tool for me for that. When I was fresh out of college though I never did it and didn't feel like I needed it.
I 100% disagree with the Leetcode comment. I think leetcode can be incredibly helpful for learning DSA and for mock interview prep. If you cannot complete easy and medium LC problems in each of the important categories, then the odds are against you in a real interview. I wish that companies didn't assess your skills via DSA so heavily but they absolutely do. If you do not use leetcode (or any of the other copycat apps), then how else are you supposed to build confidence in these niche subjects? Simply reading textbooks for these purposes is the worst advice.
Besides REact deprecating/changing every two years.. code bases often DONT rewrite entirely with the changes.. so guess what.. now you got 2/4/6 year old React code.. and new devs learning the new ways.. trying to figure out wtf prop drilling and events, etc that were "popular" years ago but aren't the way today.. are doing in this 500,000+ lines of code base.. yah.. it's maintainable..
Data structures and algorithms aren't the issue with modern software development. I mean, sure, they're something you should pay attention to. Don't go around filing Lists in reverse order because it's O(n^2), like, obviously. But at the same time, I think it's trying to put all that stuff together that's become the much larger complexity with people's code. Nowadays just about any language you can think of has a very feature complete library of collections and ChatGPT can give you a detailed and correct explaination of just about and algorithm with example code in the language you want. And if that's not enough, every single CS graduate has had multiple years of training both conceptual and formal to categorize data structures and algorithms.
Fun fact: I was always bad at DP in our ACM ICPC team - yet at work already have implemented multiple DP solutions in the past lol. Quite unexpected I guess.
@@scythazz Not satire. Sped up existing algorithm with memoization and DP I think two times. It was so visibly possible that I was amazed it was not done before. Not sure what alg it was, but some 3D graphics algorithm in one case and a regular hiperf code in the other... PS.: But I feel I am still very noob for DP problem solving, just surprised that at work it came up.
As a beginner learning the basics it's honestly demotivating, like I understand you should try new tools, learn and adapt, but is it really necessary to work in your personal projects while working full time as a dev? I want some kind of healthy work life balance, spend time with family and just relax sometimes.
i applied to like 1500 jobs last year and got maybe 10 interviews after touching up on my resume like 5x, idk. the market is fucked. the only people i know who've gotten work have been pruned for the position by other people. I get networking being important, but in small places this isn't a thing. So I network by working with people on projects online. But they are also in the same boat as me, otherwise they wouldn't be doing this. So yeah, talent kinda sinks to the bottom in this system.
1:23 never stick to your current tools, but on the other hand companies asking for X YoE in a SPECIFIC TOOL and refusing to even talk to you otherwise. Make up your minds, you want people who used the same tools for five years with zero interest in learning, or you want people who actually want to learn new things? Learning new things actually sounds like bad advice under the current job market.
any suggestions on changing from consulting to product dev? I’m a senior software dev in a consulting org…never done a technical interview and nobody from product teams will give me the time of day
In a technical interview once they ask you to demo your skills you just open Jira, create an issue and plan a new sprint for next month with lots of story points and all that bullshit. Easiest way to "win"
RUN FROM THAT JOB
LMAO this is actually how most companies work!
I thought I was doing the right thing studying software engineering, who knew what I really needed was Jira engineering! 🤯
I've wasted my life! 🥺
This is the best algorithm out there, you can apply it to almost everything, such a gem...
@@ThePrimeTimeagen dude, that is most of the jobs out there, the only people who are not using Jira, are using Azure Boards.
Required: 5 years experience with Windows 2000.
- Actual job ad I saw in 2002.
You guys are gettin paid?
LOL
Rt!😂
I am not, it is my own unsuccessful business lol
Wtf
If you write the business logic, aren’t you technically a business man?
interview: ROAR
actual job: MEOW
Today, i got an offer letter from a company for a full stack dev role. So happy 🎉
LFG!!!
In most professions it is assumed that you go to work, do your job, then leave work and stop doing your job. How many lumberjacks fell extra trees on the weekends? Software engineering manages to impart a mentality on a lot of people that they need to be learning and writing software all throughout their free time. Of course it's good for career aspirations, and having OSS contributions is great for your CV, but putting a lot of pressure on this leads to burnout. After 8 hours of programming during the day, the last thing I want to do in an evening is boot up a computer and do more programming. Basically what I'm saying is when looking for jobs, do all that you can, but outside of that, make sure you're living a life that you enjoy and can sustain happily. You don't need to give every waking hour of every day to more software development
one thing ive been saying lately: my github is empty, because i write code that gets me money
This whole "must code 24/7" mentality is more prevalent with junior programmers I think. When you are still new to the game... but if you've been doing it for years you get pretty tired of the constant burnout and the junior developers will get to that point too eventually.
And this whole mindset that you should know 100 different technologies is really stup|d, how do you get to be good at anything if you are constantly having to learn new things? Improving your skills is always great but learning something completely different every other week isn't improving your skills,
I feel like the lumberjack might go home and still woodwork for fun, maybe making furniture is a Hobbie. Not felling trees but still in that area... idk I'm also high af
I think the reason is cutting down trees is nowhere near as complex or dynamic as writing code. But yes it's important to have balance.
@@gamereactz 'woodwork for fun'? Is that code for banging his wife? If that's the case, then yes, I do agree that's probably what he is doing in his free time
I have made it to round 6 of an interview, passed the final round. They told me I did everything they asked, just not well enough... Interviewing is SO much worse than the actual job and by far the worst part of being in the tech industry.
There is zero acknowledgment that some of us just struggle to vomit up technical info on the spot and getting rejected from life changing jobs, where you are OVER qualified for the actual work just because you answered a question without using the proper vocabulary. I have even been rejected because the interviewer didn't like how I moved around within the browser IDE that he linked me to for the interview.... even though I did the ACTUAL work he asked for and with time to spare...
I enjoy the technology, and I enjoy working with engineers. But I LOATHE basically everything else about the industry so much so that I am only in my 4th year and I am desperately looking to do ANYTHING else with my life.
@@koschmx hahaha yeah that's wild
This shit about everyone "needs" to code in their free time in order to get a job needs to die already. Its such terrible gatekeeping mindset to have. These kind of people who spend 80 hours a week programming but never go outside are crazy imo. They can sit down and tell me about all the side projects they made in some obscure language, but ask them to sit down in front of a client and condense what they want into an understandable ask and they are like a fish out of water. Now don't get me wrong I like learning new concepts, but not because I have this anxiety that I'm not always up to date with every new fangled JS framework. Not every person sees Programming as a hobby for some people it is just a job and guess what, that's fine guys...
Jup... It's just a Tool and not the goal in itself
Can't agree more to the "Try designing a course" part. I joined my current company about a year ago and noticed they still used JUnit 4 for testing.
So I took a leading and educating role about migrating our tests to JUnit 5 and I have learned a lot in the process about some "corners" of JUnit 5 I have never had in consideration before and teaching my colleagues has helped me dive even deeper in the matter.
It was also so much fun, that I consider contacting my alma mater if they are interested of me hosting some lessons.
How did you get that leading and educating role in the company. Do you just ask your boss if you can do that after you noticed that problem or how does that work? I mean initially you were hired to do something else... And when you had that role, was it like your main thing for a time to do the education or was it more like a smaller task next to your other main tasks?
@@DAD1996W We have one day every other week were we can pursue any kind of improvement of the code we can think of instead of working on our regular tasks if we want to (We call it Technical Debt Day).
So initially I took that opportunity to produce some small example tests featuring JUnit 5 (esspecially parameterized tests and how to multi-thread them for shorter test cycles) and then presented it to the team and the boss. As this was only a kinda vertical slice it took 1-2 workdays at most to prepare.
The team was onboard immediately and my boss did not need much convincing thanks to that. So I was given some time to properly research the methods of migrating tests and developing a proper architecture on how we would write these in the future (esspecially parameterized tests).
After that I presented it to the team, making some adjustments due to their input and spearheaded the first few migrations. The mentoring was more of an ongoing on the side thing and as I am blessed with a good team it did not take long for everyone to be able to work with this without my assistance.
Due to the scale of the project the complete transformation is still ongoing , but every new feature is now tested with JUnit 5 according to the specs I worked out.
Needless to say, I got a sizable raise as a recognition for this work. Granted, not every company / boss will give you such an opportunity or even give you the recognition for your work, you always need to find what works best for your environment.
I disagree with almost everything being written here.
Remember, companies do not know what they needed until they have the experienced people, this is very common.
Having a specialization (or several) on top of practical experience is MUCH better than knowing the latest gimmick feature/language/framework.
We live in the stinking dark ages of software development and a lot of it is 100% the result of people just chasing the latest hype of nonsense that tries to reinvent the wheel.
Somehow they nearly always end up with almost square ones.
Instead of developing the core skillset that is universally applicable.
TLDR
Incompetence generates insecurity!
Insecurity initiates the move to jump into every new hype!
Jumping into every hype never gets things done and blocks developing your core skillset as all the energy goes into retooling/learning things that are obsolete with the next hype.
It is mostly outside interests, not the interest of the professional developer, to jump into new hypes.
During a technical interview, just conditionally iterate the print statement over all possible solutions. Make sure it’s in C so that it runs fast.
Usually a ton of job offers show up most of the time, EXCEPT when I'm out of a job and i'm actively looking. Guess that's my "luck"
Networking has gotten me every one of my jobs. Always, always shake hands and make connections. Jobs will drop out of the sky.
TCP?
Let’s just say the diameter of my graph is large
@@MoradorDeCalcada MIL-STD-1553 😉
Example conversation I had yesterday:
> shake hands with guy at church, he asks what I do for a living
> tell him "I write software"
> "Oh, do you do side projects? I need someone to help me with the last mile of some scheduling software."
> "Yes, I do side projects. Here's my email."
This is on top of 2 other side projects I have going, plus my 9-2-5. Everyone needs software. Gotta leave the basement to find out what problems they need solved though.
@@MoradorDeCalcada0
"No one learns more than the teacher." At least, as long as the student is learning something. I swear some teachers are diametrically opposed to learning anything.
I don't agree with the advice to always learn or code outside of work. Programmers should have a life instead of sitting in front of the computer in their free time. I personally hate the cult of "constantly learning some new technologies". Technologies come and go, if you don't need it for your actual day-to-day work (which would mean you should learn it a at work BTW), it's a waste of effort as it will probably die in 5 years or sooner anyway (especially in JS world).
This take is fine. It’s just that there will be people that are willing to take some time out of work to learn new technologies due to their own interest or to keep up. They will most likely improve faster and become better than you and therefore be more likely to be selected by companies over you. I don’t disagree with you. It’s just that this kind of mindset comes with the acceptance that people that are willing to put in the work will simply just become better than you and therefore be more likely to get hired over you. Learning the technology at work is ideal situation but companies will always prefer the candidate already knowing the technology coming into the job.
Coding in your free time has nothing to do with a healthy living experience. Its about being ahead of everyone else so u can continue working or find a better job.
@full-timepog6844 🎉
I never ask technical question as in "write this algorithm" It doesn't prove anything, hell I admit that I haven't implemented an algorithm or std data structure myself in 20 years, I use the STL and the STDLIB. I just ask what people wrote themselves, what was challenging how they solved it. And I give them an example of a current issue we are facing. Last tech interview I did took 10 minutes from my side and I was like: "yeah, I too love this guy". I asked him one insight question that I knew he had no experience with, just to see how he would find answers -- what to Google for is more important than having that knowledge in your head. Because sooner or later, you need to do things you've never done before. So I was taken with this guy immediately. In the past we had some tech questions and especially those that I knew people couldn't answer. I want to see if they take charge. If they say: "Okay I don't know can I use a computer to google it? Or can I grab that book of the shelf and browse through it?" Then I knew they were good. When they would just walk in circles (and not even writing compilable code just pseudo code or describe the process of solving the question) then I know that either they need mentoring or perhaps isn't the right candidate.
One guy got so angry and shouted: "This is INSANE NOBODY KNOWS THIS! WHAT DOES IT PROOF?!"
And my manager calmly said: "It proves if people are willing to discuss this on a professional and friendly way, anymore questions? Otherwise I think we know enough" :D
Thank you for mentioning this. Currently looking for jobs and the scene is new to me, far more than programming itself is. So seeing what's expected of me is very helpful.
@@Axlefublr My advise is (as Prime's) is to communicate. It's okay to say: "I don't know, but..." and then describe how you would go about solving the problem as if you were employed there. Employers and in my case Customers (I am freelance) want to be sure that when you are in that seat, that you can take away their worries. One tip for interviews listen to their unspoken worries or challenges or flat out ask them if you don't pick up on them. A question like: "What are your current big challenges or problems? So I can see where I can fit it and help out." Is a great thing to ask! It shows that you want to jump in.
And what my former employer said before I went freelance was: "It is not what you know, but who you know." So in other words, if you know something that works for that company ask if they have openings and put that person forth as a reference. I noticed when i worked at IBM, that majority of people working there were the sons of the previous generation.
And my current customer, I am working on a 4th different project. The fact that you know the organization is a leg up.
@@Axlefublr Wow! You have a lot of content on YT too. You have more videos than me and I started 2 years ago! WOAH!
Be sure to list that on your Resume, the interested people will have a look and see instantly you are a linux power user, you actually love to also develop your skills in your private time. That's definitely a leg up and especially for your first or second job when you do not yet have a lot of job experience.
spot on. Communication is key. I always advice people heading for interviews to not be afraid to look dumb. The technical aspect of the interview is just the setting, the actual assessment is how you're going to be working in solving problems with the team.
In my interviews I don't allow candidates to google though, I ask them to treat me as Google and ask the questions directly to me and I provide the answers accordingly. That way I can assess how they're thinking of the problem and how they would be googling for the answer.
Yeah, I agree on this. I usually struggle a lot with technical interviews even though I'm not a newbie. Often interviewers will ask me questions that I know the concept of but not the technical terminology, I lost some job offers due to that and I always wonder what if you find a person who knows the concept but doesn't know how to use it properly, and what if you find a competent candidate who doesn't know the concept but knows how to use the tools and knows how to fix things? Who's more valuable there?
I wouldn't say I necessarily struggle in the interviews on the technical side. The hard part for me is in the socialization as most technical interviews tend to copy the google interview model, which optimizes for the "Smart Extrovert". As an introvert by nature, that takes a lot out of me. I'm more used to solving problems in my head rather than talking it out, so the whole interview process takes me out of my most optimal form.
That's a really good point, and probably one of the reasons I did better in the technical interview for my current job than some previous places I'd applied; it was a timed technical problem that I could do in my own time, rather than sitting and trying to explain my thoughts to someone while I panic and second-guess myself.
Final form?
for the bubble thing, I would guess it has an "on mouse up" on the content wrapper, so when his pointer went up outside of the container it didn't get triggered
My guess is that when you drag it outside on the beginning it ends up selecting something else you can't see, and because that can't be shared it blocks it from making the share bubble.
I actually disagree about not applying for jobs and instead of waiting to be approached by a recruiter or hiring manager. I've been on close to a hundred interviews over 25 years and I've only ever had luck when I was contacted first. It seems to me when that happens the people have already decided your background might be a a good fit and they want to interview you in order to validate that assumption and to sell you on the company. While when you make the contact they are looking for reasons to eliminate you from consideration. Also, I've not once been asked to write an algorithm during an interview.
I had a similar experience recently. Handful of targeted applications and one interview, then I took the job. We each knew I matched what they were looking for pretty closely. I’m not a web dev by any stretch, though, so I wonder if fluidity in that particular labor market makes it harder.
i think this is a perspective problem
first job tends to be reach out
second and beyond tends to be reached to (not always)
3:05
I still think applying for jobs aren't like......getting job immediately but you will get noted down like a reserve unit. If job opens, they will check the reserve and see if you are available.
I'm kind of weird in that I depended on Craigslist for a long time for programmer jobs. Yes, I know that place is bottom feeder central. But for a long time I never had any luck with recruiters that approach me, or other job boards for that matter, so oddly for me Craigslist was like the old faithful that never let me down. Like an old ugly car that I know will start. I know I should be going to better places and started taking it as a sign that my skills aren't as good as I first thought.
Programming isn't my profession (I write music), but I've never gotten any work by "putting myself out there" and applying for jobs. My work has always come from ""networking"" (ie, old friends, people who I've worked with in the past, people who are familiar with my work).
In an interview, it doesn't matter how much prior experience or expertise I have, I've always been treated like a child, and inevitably get interviewed by some jackass (like the one who wrote the article) who thinks that they're the Gordon Ramsay of their field, and think that they've gotten successful hiring down to some magic formula. I suppose it's a personality issue on my part, but I have an extremely difficult time showing any enthusiasm or respect for people who are condescending (consciously or not), and who want to make me do pointless artificial busywork or meet some artificial arbitrary standard that has no real bearing on the actual quality of my work. My patience for it wears thinner and thinner as I get older.
However, when you're contacted about a potential job, it's always "oh yeah, Steven's cool, he's a bit eccentric, but he can work miracles, you should have seen what he did on xxxxxx, let's take a chance and let him work on xyz and see how it goes", and it almost always goes well, because there's mutual respect there.
Which one of these situations do you think is going to go better?
If there's one thing I'd take from this video; it's teach others what you know well, generally your effort is paid back though it's best not to expect it, but you will also reinforce your own understanding. It's a great win-win.
So basically, sacrifice your life completely, and keep grinding to the bone 24×7 till death to get a job.
It's all about that sigma grindset
An interviewer would pick the guy that is doing that
You thought getting a very good jib was gonna be easy ?
That's how I got my last job. I had my CV on the AMS (government service for workless people), but didn't actively do anything. Got called by a headhunter at 8 in the morning and scheduled a meeting. After meeting the headhunter, they arranged a meeting with the employer. It was a delphi job with some UI dev. I forced my way into backend, introduced go, d-lang and rust into the company and in the end, we were even trying out rust for cross-platform.
In the end, I'm never gonna be a coder that treats things as "just another job", I'm gonna push back on bad ideas, I'm gonna tell seniors and bosses if I think something is wrong, because I'm not a code monkey. I think of myself as a professional and it's my professional duty to make sure bad decision are thought through (bad decisions are fine, if people know what they are doing and why).
Been on the job hunt since January. Well over 150 resumes sent out. Probably closer to 200. Out of those, I only got 1 interview. How do you make a network if you never have had the chance to network? Do I start adding random people on linked in?
You go to the meetups and prepare interesting things you can talk about.
Also be open to moving around. If you can't find a Front-End Developer role then try QA Engineering or DevOps. You probably have the skills, or can pick them up super quickly. Itll also you get into the company and very close to the dev team
I have found in my personal experience, I had to grind and find my first position -- advanced and advanced within that position learning and taking on new tasks (smaller company).
Now I got people reaching out inquiring without me applying to those positions.
does that mean you network a lot?
The bubble only appears when the mouseup event fires in the text area. The mouse was outside of the area when it failed to appear.
Wow nice spot
@@Manhunternew I've spent WAY too much time thinking about such things. :)
I finally got a job today (not programming unfortunately) after I applied for 120+ jobs in the last 5 weeks. The jobs were in many different fields like comp sci internships, data analyst (entry/junior), junior dev jobs, restaurant you name it.... Even though I have about 10 years experience in restaurants and some retail experience most of the jobs I applied to just didn't want me because I have an associates degree in math now (finishing up my BS in comp sci at a university).... it's ridiculous.
i think they dont want you because they think you're likely to get a better job in your degree related field and leave.
I'm currently looking for a job and it's the first time since I started coding professionally (10 years ago) that I do it without networking and gosh it's harder than I thought.
That thing in the wallet is a Dutch invention called Secrid created by Rene van Geer. When we were the first nation to put NFC into their bank cards to pay without pin number, that company was like... Maybe you ought to put that NFC enabled bankcard into a Faraday cage. You now see Ridge Wallet but that basically is a patent of the Secrid. I bought SecrId the week they came out. My customer is a bank, I am on my 4th contract and every time you leave they also give you such a cool wallet. So my mum and dad now also have one (safeguard my inheritance :P)
I love your content, I am by no means a great programmer yet but your passion inspires me to keep going. Thank you
He asked to stop asking about blue hair, but in the end it doesn't even matter... Because after 6 month blue hair found him.
The appeal to put me off. Whenever someone refers to a "modern web application" I automatically assume they mean really low quality experience, really high complexity implementation.
I believe communication is a huge factor that employers consider while hiring. I had a technical interview where I did not know the proper function required to perform a specific action, but I knew what needed to get done for the program to run as intended. I asked the interviewers questions to confirm I understood the assignment and I walked them through my logic and understanding of the problem. They understood that I could easily finish the program despite not knowing the specific function because they heard me walk through the problem logically out loud with them. They get insight into your problem solving skills, communication skills, and technical skills in one fell swoop.
"I don't want your bubbles" - The man who played unsolicited audio on Netflix' main.
This really is a great video, knowing what not to do will help you do the right things.Will not work 100% but will help guide you in a good direction.
I havs a strong understanding of data structures and algorithms, I just can’t focus in technical interview. I feel like I lose half of my IQ from being put in the spot
What's wrong with deprecated? It's cool, as long as features remain available, receive security patches and you get the backward compatibility. I don't like the new 'meta' full stack framework just to make a GUI trend, but React has been a pretty stable and backward compatible library so far.
"The Witcher is about to come out"
Prime my dude while I do love you, you could not have picked a worse show to use as an example.
just picking a top of mind show
also the witcher, i watch it and wonder "what the hell is going on here..."
@@ThePrimeTimeagen get ready to wonder a whole lot more... Henry Cavill ain't in the next installment.
That "Bubble! - No Bubble!" talk is most interesting part of the article review 😁
Regarding the bubbles, I’ll bet they did a mouse up event in the p tag or a container that doesn’t include the margins, so when you end your mouse click outside the text it doesn’t bubble
All this gatekeeping bullshit does is make you feel shitty for not getting a job in a market where getting a job is actually hard, companies are seeing this and going "fight for me you idiots", we should have more comradery with our fellow workers.
Is it weird that I'm nodding my head in acceptance to some of points made, negative as they are.
hah, its made for you, potentially even by observing your life
I can second try writing a course. I've been tasked to do inhouse courses to onboard new employees in my own field (in administration, not programming). It's both amazing and scary how much you learn or find out you didn't know that well.
I think the thing that strikes me as someone early in my career is just how much stuff there is to know. Nobody is going to know all there is to know about software.
Some people focus on data structures/algs and trust you to be tool agnostic. Some people want 3-5 years of the .NET stack out the gate. Universities and bootcamps then have their own group of focuses. I think this is where getting into open source and networking is also a big factor
I didn't expect this from an educational channel. 😢
you are welcome
the mistake was thinking this was an educational channel
@@bigmistqke holding the flag for your username I see.
@@danielphil80 🚩
How to never get a job?
1. Be in Venezuela.
2. The first one is enough.
I already don't have one.
Even though I agree with everything on this video, I have to nitpick with "no one cares if you can't solve X leetcode problem". There are a few companies that I didn't get a job because, according to one of them, I "couldn't solve the [hardest] leetcode challenge [you'll ever see] required for this job". It was for a mobile game dev company. Nowadays I have a job doing much harder stuff than what I'd be doing there, and even still never ever had anything CLOSE to how hard that leetcode challenge was. Dodged a bullet, sure, but being unemployed during that time was rough.
Disappointed that we didn't hear grug's opinion on this
I'm a hobbyist programmer atm. All I use in my code is vector, smart pointers, and map, and it's absolutely possible to program a video game without knowing *anything* about data structures.
All that other stuff is pushed to filter out people. Unless your doing backend there is no reason to really learn that stuff. Until you get advanced
ACM competitions have much higher complexity than leetcode problems, so doing ACM is like doing leetcode , but on even harder level. That’s why I think you are doing well on technical interviews without practicing leetcode. 12:04
16:50 I feel the same anxiety as you do when I scroll youtube, insta or linkedin to get out of it i just use them in browser but I still feel the anxiety (like a big burden on my brain), its really hard. I could feel you when you said it
Finally a topic Tom knows nothing about.
does tom even apply?
@@ThePrimeTimeagenTom probably has recruiters sending him beer and fruit baskets all the time.
To be fair, if you have done ACM Programming Challenges in college, you already have practiced Leetcode. Since Leetcode and all other programmig interview sites are derivatives of the OG programmming competitions.
Yeah, I don't believe anyone can be good with LeetCode style interviews without practicing unless you are super smart. Just doing theory on algos would just lead to the "illusion of competence" since you never test your understanding
"[..] the biggest issue with the current education system is that it teaches people patterns to memorize rather than understand the actual process"
- Ironically, my issue is the other way around. I udnerstand the solution, then I find out it has a name. Now I do know and understand the important ones, but my process was reversed. Because I started as mostly self-educated (reading, sure but mostly practice). 15-17 years back, there werent any real programming school studies in my country. It developed to where its now while I was working and learning.
But I dont mind, because its the concept what you need to understand about design patterns, so you know how and when to apply it and not just willy nilly. Design patterns are a solution, if you do not have the problem, dont use it or you'll introduce unnessary complexity (=> error prone).
The frontend JS frameworks change their paradigm every month so you'll always be behind with that.
LMAO, imagine having to do all these computer science courses just to web development. a waste of time and talent.
There’s no way PrimeTime has done only 20 leetcode questions in his lifetime. What?!
You guys have jobs?
!(How To Never Get A Job)
BTW first comment
Just found about this channel this is like Gary and His demons, if Gary was a developer... awesome keep it up!
I hate the advice that getting a job should be through people in your network. It's easier to get a job through people in your network, but you can develop the skills and the salesmanship that lands jobs without it. I've had maybe eight jobs in tech and one came from people in my network. I would never discourage someone from relying on their Network, but if the person giving you advice has primarily relied on their Network then don't take their advice. Relying on your network is the easiest part of the job search but it requires having a good Network. Anybody who tells you that the most important thing is to rely on your network is making the assumption that your network is good. This is a bad expectation. Most people's networks are not good during the times for which it is hardest for them to find work.
My theory is that the bubble doesn't appear if you release the mouse button on the margin
bubble. no bubble. bubble no bubble. 3:45
bubble bubble bubble gummy gummy gummies
bubble bubble bubble gummy gummy gummies
bubble gummies.
it feels like the bubble comes out if you do it quickly. if you're more gentle with the mouse it doesn't come up.
A lot of companies outside FAANG don't go that hard on DSA questions, and instead focus hard on system design, databases, design patterns, and "trivia" kinds of questions where programming knowledge/experience with a specific stack counts. These questions can run the gamut and unlike Big Tech, they're not standardized at all because every company/interviewer is looking for a different set of specific things.
If you're goal is just to get into Big Tech, you can do that with essentially just DSA, however, most SWE's don't work in Big Tech and won't ever work in Big Tech. Also, if you come from a non-traditional background (e.g., math/physics to software) then good luck putting that DSA practice to use when you won't even get a chance to interview.
Re the bubbling, I'm pretty sure it's because your selection ended outside the paragraph element
Scrolling through twitter instantly triggers me so I keep it handy for gym days
Never underestimate the power of networking. Got my first ever Developer job from a businesspartner of a guy who was recommendet to me by the owner of a business I had an Internship at.
As time moves on, It seems to get harder and harder to put yourself out there though. Weither if times have changed, the market became more saturated or if it is just because my introvertedness became worse I can't tell.
12:40 : Partially agree. Knowing how your tools work is important. But similar to how you don't need to know every screw in your car to drive it, you also don't need to know every minute detail inside your tools to get going. It is more important to know how to use and configure them right. Rather than how they exactly function.
4:15 : The whole "Bubble" thing seems to depend on where you release the Mouse. Outside the text == no bubble.
The problem is that it’s hard to transition to new tech since you need years of xp to do so
Its also often not really a good thing to do
This is the new -10x engineer video, I can feel it
Hi could you post the link of the article ?
9:10 wait ? WTF isn't like every programmer supposed to be able to do that ? know I see why people are afraid of "AI"
For a second I forgot the title and was going to comment how terrible these advices are
beautiful
Out of uni, I took a total of two job interviews.
First one: "Where do you see yourself in 5 years?" "What are some design patterns"
Second one: "What do you do in your free time?" "I play with arduinos" "Hired"
17:40 finally I couldn't figure out who I thought he sounded like
I cant do DSA, had a two year education, did not finish high school, did most of what he said to not do and still landed a job, all I did was try to get really good at JS/TS, React and writing clean code, and deep dive into what I thought would be relevant at a job.
The bubble thing is simply that it appears if you release the mouse button on the praragraph
Disagree on the "switching up paradigms". I feel like way too many people try to spread themselves too thin. Making value a lot of the time is about creating a niche for yourself. People that are unfamiliar with actually creating impact think that knowing more random stuff is valuable. No, knowing one thing very well gets you the job. Expanding after that helps you rise, but does not get you that first job. I would definitely not recommend someone trying to get their first job to learn frontend and backend in depth (maybe a little bit).
I think leetcode is more prevalent now and especially if you're entry level. Of course you can get by with algorithmic and dsa knowledge but leetcode helps to think algorithmically specifically for the types of problems new engineers will be typically asked. You get out of what you put in, as well. You need this kinds of skills to just pass the basic minimum, then your more practical knowledge shines through in the rest of the interview.
Super strong data structure will help alot though. But I agree that leetcode is basically the interview now sometimes as companies copy and paste questions from leetcode. Interviews will and always be a performance and not an actual demonstration of ur skills. At least not the first few rounds in a 7 rounds interview process….
i always saw it as a an equivalent to doing hw for a dsa course or practice problems. Its kind of like a calculus course. I can learn that an integral is the area under the curve and learn how to integrate an equation, but it also helps to also integrate a few equations to hone the skill. I think the same goes for dsa and leetcode. For the course you can learn about a linked list and implement it, but then it helps to maybe study and do a few practice problems using linked lists. Once you are out of college for some time I find that youtube and leetcode was a good tool for me for that. When I was fresh out of college though I never did it and didn't feel like I needed it.
What if i dont want to become a better programmer and instead just wanna coast and move to management
I 100% disagree with the Leetcode comment. I think leetcode can be incredibly helpful for learning DSA and for mock interview prep. If you cannot complete easy and medium LC problems in each of the important categories, then the odds are against you in a real interview. I wish that companies didn't assess your skills via DSA so heavily but they absolutely do. If you do not use leetcode (or any of the other copycat apps), then how else are you supposed to build confidence in these niche subjects? Simply reading textbooks for these purposes is the worst advice.
13:45 wait ? its C-lion ? not Cli-On ?
Besides REact deprecating/changing every two years.. code bases often DONT rewrite entirely with the changes.. so guess what.. now you got 2/4/6 year old React code.. and new devs learning the new ways.. trying to figure out wtf prop drilling and events, etc that were "popular" years ago but aren't the way today.. are doing in this 500,000+ lines of code base.. yah.. it's maintainable..
Data structures and algorithms aren't the issue with modern software development. I mean, sure, they're something you should pay attention to. Don't go around filing Lists in reverse order because it's O(n^2), like, obviously.
But at the same time, I think it's trying to put all that stuff together that's become the much larger complexity with people's code. Nowadays just about any language you can think of has a very feature complete library of collections and ChatGPT can give you a detailed and correct explaination of just about and algorithm with example code in the language you want. And if that's not enough, every single CS graduate has had multiple years of training both conceptual and formal to categorize data structures and algorithms.
12:56 Didn't Microsoft initially develop LSP specifically for VS Code and later made it a publicly available open standard protocol?
Just went to the article , They fixed the bubble bug xD
Fun fact: I was always bad at DP in our ACM ICPC team - yet at work already have implemented multiple DP solutions in the past lol. Quite unexpected I guess.
It's all fun and games until you get DP'd at work
facts. don't dp at work
Is this satire? Would love to know what you do at work that needs DP lol….
@@scythazz Not satire. Sped up existing algorithm with memoization and DP I think two times. It was so visibly possible that I was amazed it was not done before. Not sure what alg it was, but some 3D graphics algorithm in one case and a regular hiperf code in the other...
PS.: But I feel I am still very noob for DP problem solving, just surprised that at work it came up.
Didn't know that language servers were a thing... Huh, you learn something new every day..
As a beginner learning the basics it's honestly demotivating, like I understand you should try new tools, learn and adapt, but is it really necessary to work in your personal projects while working full time as a dev? I want some kind of healthy work life balance, spend time with family and just relax sometimes.
i applied to like 1500 jobs last year and got maybe 10 interviews after touching up on my resume like 5x, idk. the market is fucked. the only people i know who've gotten work have been pruned for the position by other people. I get networking being important, but in small places this isn't a thing. So I network by working with people on projects online. But they are also in the same boat as me, otherwise they wouldn't be doing this. So yeah, talent kinda sinks to the bottom in this system.
not working(
What's DP? What's the cityscape problem? What's league code?
1:23 never stick to your current tools, but on the other hand companies asking for X YoE in a SPECIFIC TOOL and refusing to even talk to you otherwise. Make up your minds, you want people who used the same tools for five years with zero interest in learning, or you want people who actually want to learn new things?
Learning new things actually sounds like bad advice under the current job market.
Streamberry reference was pure gold
What’s the best place or books to learn algorithms and data structures?
any suggestions on changing from consulting to product dev? I’m a senior software dev in a consulting org…never done a technical interview and nobody from product teams will give me the time of day
I started using grep, and i feel grapes in my stomach
10:12 note to self : free stuff