Andy you are absolutely awesome and I appreciate the videos you produce. I've subscribed to your channel a few months ago so I can stay up to date on your productions. They have really helped me to push forward and not back out on my direction of becoming a programmer at the age of 41. After 4 years of uncontrollable seizures and a brain surgery your vids have given me some hope for the future! Thanks man!!
In your *first programming job* , you will be kinda nervous and confused. But *remember* !! Only starting out is difficult. Once it gets started, the *success* is on your feet. You get pleased and used to to work as a programmer. Nice day man!
I started my first dev job and it's been 10months. Still cannot used to the job, codebase, inability to accomplish work, no senior member in a team except manager and hence nobody to get answers from, except busy manager. Constantly being told to work faster. Asking questions often end up routing to manager, get them confused/pissed, so fear of asking right questions to manager while very slow in work, at the same time, too many doubts in unfamiliar codebase, delaying work. Everybody working solitary and fixing bug like less than 1 day while it takes longer for me. Stress from work everyday, anxiety, vomitting many times, and feeling I am not fit for dev or even basic human being as everybody else complete the job way faster, and my soft skills is also not improving since it just that the job requires looking PC screen for most hours, no in-person interaction.
I think people under-estimate how accepting more experienced devs are in jobs. I've always found that for the most part people are helpful to jnrs/interns we were all there once!
I started a job with one senior dev I work directly under and I've been baffled by how accepting he is of how much time I take doing things, how I fuck up, and just generally don't add much value A junior developer with not much experience is an investment to a company, not a direct cash machine and I feel like he understands this really well
Totally. I was so happy to find a team that was supportive and encouraging. I really didn't know what to expect so it was a relief to land in a supportive environment myself.
Starting your first industry position after mainly academic/tutorial-based study can be a tough transition. You're used to working on small, guided projects and suddenly you're dropped into a huge existing codebase with hundreds or even thousands of interdependent files and have to slowly piece together how different parts of it work, and start modifying/adding to it. It can be daunting, but if you get complacent, then suddenly you could be 2-3 months in and still have no idea how anything fits together or where to find what you need. That's a bad position to be in. Or at a startup or small team, you could be building something from scratch or expected to expand on a small starting point, which can be paralyzing in its own way. It's important to remember that other developers are there to help - that it's okay to ask questions or not know everything right away. Also that it's usually better to fail fast and often to reach success quicker than to never fail nor succeed.
I get it. I am in that place where spelling errors get me, I sit there and think, "this logic is good and impeccable, WHY IS IT NOT WORKING?" Then I have a mini-depression, where I think "Maybe this is not something I can do so ". But damn, I am resilient, I go back and BANG! IT HITS ME! it was such a small thing then I am so in love with coding again. awww...I love you. the hardest part about it for me at this point is those small errors,not the logics or theory. Just misspellings etc.
@Ryan Dulac I think you are right. Intellisense helps, but as you said it doesn't prevent me from making typos. I hadn't considered what you bring up about spellheckers, they wouldn't work so well with code. My problem is tha It type a variable/function a bit wrongly than Idid earlier in my code. Sometimes in not so easily detectable way. Like there would be an uppercase letter where there is lowercase. Sometimes your mind glosses over all of that when you have been sitting there for a while. That is why I think breaks help a lot, you come back and you don't take certain things for granted - its almost like you become re-acquainted.
Don't expect a company to babysit you. Don't rush and apply for jobs after 6 months of watching tutorials. Make sure you have a good amount of skills that you can actually start a project on your own from start to finish before heading into the industry.
I already got fired from my internship, now I'm being self taught. It's actually more fun and it's on my terms. Freelancing is the way I would say, if you know how to do it.
@@matinsasan They told me that I have completed my 6 months internship in just 15 days and I'm ready to take on a complete project right away. But I refused and said it's not possible, I asked them for some time of 2-3 days so that I can at least understand the starter template they were telling me to use. They said that it would be a waste of time and client is already expecting results, a few days later a new guy came to office looking for a job and the next day they fired me.
@@braindeveloperdimensional5579 Just to reassure you something at my 43. That shit had nothing to do with you, maybe they just hired the cousin's manager, since they don't expect anything from an intern, they just solved it with a relative to make a favor. Nepotism and favouritism it's a huge deal globally. So unprofessional from company, I'd say they made you a favor.
A different way of looking at this is to ask yourself what kind of person would you hire if you had to do so? Then be that kind of person. 😊 I like how you summed it up though: 1. get very comfortable getting frustrated. 2. bleed now so that when you go into battle it's not that bad. Like you said, it's simple advice but that doesn't make it easy to follow. Just as common sense is not all that common. 😁 Great video.
@@edvinas6069 You will! I almost gave up on my dream after being rejected and humiliated in brain teaser interviews, but you know what... Keep going! People always feel like giving up when they are nearly there. You will get it but you must work for it! I believe in you :)
Feeling an unreal amount of fear as I start applying to my first dev jobs to change careers. This helped SO MUCH to calm my nerves - thank you! Already threw myself in the deep end once with a long-shot department move, lived through the struggle and frustration as I absorbed it all... I can look back at that as proof that I am capable. (I'm still terrified though I will be truthful!)
I disagree. I'm not a software engineer. I do software engineering as part of my RF engineering job. Job security depends greatly on your boss. But small companies can be MUCH more job secure because you are an essential part of the team. In big companies, you are disposable.
As someone who has seen a lot of students coming into a company those who have extra-curricular programming experience (programming/tech *projects* outside university) are head and shoulders above the rest. The good news is that self-taught developers in my experience tend to have more idependent personalities and a couple more real-world projects under their belt than those who thought a degree would teach them how to be a developer. Either way the solution really is simple: do actual real world projects. Even if it's not a very serious idea/use-case at least come up with an ideas and execute them, and keep repeating that for the rest of your career.
@@rdxx4073 The most important thing of all is just repeating the process: idea, design, implementation, testing, evaluation. I suggest doing small an highly achievable projects so that you can iterate over this process without getting bogged down and burning out. The point is to get used to not having training wheels and having a bit of experience with a decent range of technologies. University/college can't really give you this - you have to do it yourself. Try participating in open source projects, there are many interesting projects out there. Some project even tag some bugs as being "beginner friendly" ( github.com/MunGell/awesome-for-beginners ). Make sure to pay attention to how other people communicate and do things - there's more to it than just writing code. Or, just come up with an idea for an app on your own. How could your hobby, home or someone else's problem be solved? Is there something in development that could be made easier or automated? Then implement it and try to get it finished enough that you can publish the code up on GitHub/GitLab (functional, properly formatted, basic documentation, tests included). Even if it is a bit of a "toy" that's OK - just say "this was a hobby project".
This is the case for a lot of different jobs, not only programming, in my case i have an auto body technician qualification and if you didn't do a certain repair, like repairing a fender during school and when the employer wants you to repair that fender but you don't really know how - you were taught the theory of it, and only a bit of practice so you're going to be overwhelmed and helpless, the employer is going to say, "look if you can't do that i can't keep you working for me". Obviously it's easier and also less expensive to do a lot of practice in programming than on auto body repairs, you only need a computer with an ide, no matter the specs, than body parts to practice, which can get expensive really quickly.
Thank you, I appreciate this great advice, especially since I recognize that I have been guilty of leaning too much on books, tutorials, and the academic side of things rather than build any projects. I found this video very helpful for setting me on the right path!
If a person can't make anything from scratch without tutorials it's going to be tough for them mostly. At some point the training wheels have to come off.
You mean like, if a person can build a fairly complex project succesfully with heavy reliance on tutorials and books... that person will struggle a lot working for a company?
I feel like this is close to it but not it exactly, a large part of programming as far as I have been is using tutorials and books to maximum advantage. The trick is to work on something that's not from a tutorial or book one where you have to actively search for and research how to solve the problem and the answer isn't in one place or even in multiple places just parts of the answer are and you have to stitch them together and make some extra on your own.
I recently started a soft dev job at a very small company. But they do not expect much, my boss told me that he spent like 4 months getting into a new ERP system. I'm just writing docus all day long, explaining the features of a new framework, because the documentary by manufacturer is not sufficient. I also figured out how to write modules within 5 weeks of being there. But I'm still learning how to write software from this ERP. I was recently announced that I will be on a conference about this framework by the end of this month. I love my new job. It feels so strange.
@@Canleaf08 Honestly I'm not surprised you were fired. You're Canadian right? Is English your native language or is it French? Your English is TERRIBLE, no offense. It brings up a lot of red flags to me just seeing your comment. Especially for a someone who is supposed to write documentation.
When everything was new projects and developers learned through getting stuff wrong, now people expect Junior Devs to know everything, paid to code... Huge red flags without Mentors.
I haven't been doing a ton of projects, but I hear this so often and I take Andy's word as truth, so I suppose it's time to get uncomfortable and build projects. I'm learning react right now and trying to master JavaScript
I was blessed with a great teacher who assigned very ambiguous projects. That was nearly 5 years ago and set a foundation I had no idea I'd be so grateful for!
1) making lot of projects 2) put yourself on challenging positions now before you get hired 3) life of software developer -getting stuck, problem solving and getting your way through it
Andy, although this video is couple of month old, it's valuable nonetheless, I think I stated my situation to you before, it's not so much I'm struggling with the subject, I'm not, because that's what I do / did before, but the application(S) size, and enormous technical depth of the project I'm working on now, makes my past experience looks like a child play, so my personal advice to anyone going from small organization to a much larger one, get ready for the big time, by studying, practicing and building side projects in order to ensure success, and, consulting with Andy wouldn't be a bad option either. Keep up the great work.
I think we can all agree the markets go up and down. With all of the fear out there right now of a potential market downturn. how do you see that affecting a developer in their first job?
The reality is you're gonna get stuck on the projects no one else wants to do and that many more before you have been fired over. Get as much exp as you can in that case and keep applying on the side till you find something better.
If your interview challenge was to spot a basic syntax error in a PHP script and you get hired the following day to code a full stack ios native app with node and mongoDb from scratch within 30 days, you know you're in deep $hit. - it happened to me
Dig in without hesitation. Google questions related to your language or third party tool. Ask for documentation on anything developed on-house. If you can't find answers, learn how to use SCM to find the developer that added the code and ask them (people love talking about their own code). If none of that works, ask your manager or team lead. Also, be honest about what you don't know. There are so many different technologies out there and no one knows them all which means that even senior engineers have to ask questions.
Actually excellent advice, as a starting developer who suffered from all these stupid mistakes and pitfalls myself, I can appreciate deeply how important the right attitude is. If people were "expecting all these cool things and tricks" from the video, joke's on them
Even building projects can’t fully prepare you for the scope and scale of massive enterprise applications that have many teams that build and maintain them. Sometimes the only way to truly learn is take the risk and get your hands in a real job.
True and not true. You can be better prepared to handle complexity of enterprise apps by building projects on your own. You should have mentorship/teammates who can you help you assimilate at your first job as well.
I think you need to fork (big) open source projects and try to understand the code and add features if you want to improve in that regard. When you make your own projects you basically know and understand all the code which isn't going to be the case in real world projects.
It's like me when i make a simple app, and i don't know what to do, then it's my first time to open StackOverflow, reading some code and I don't know how to use it in my program 😂😂😂😂
I enjoy the videos by the way, I'm a beginner but I think it's so cool to come up with a way to program something and have it actually work. It's great to be able to hear these presentations and realize certain issues I have are normal, great to be able to motivated and inspired here.
I have found myself in my first dev job, and I have to learn a whole new tech stack...It is so overwhelming. I am only 19, the youngest in the dev team and It is in a tech startup. How does ever become more comfortable?
I will probably start in a month my first dev job in a start up with some technologies I never done or have little experience, I feel comfortable yet anxious, not anxious because I think I will fail, anxious that I might not be par to what they expect me, but hey. I am really comfortable with my learning capabilities. I spent countless hours in front of my screen sacrificing my social life and fitness because I wanted to get into this field so bad. And this is what matters. Keep moving forward, you deserve a position in this field. 👍
@@aaronclare2682 It's going great, I am learning how to work as a team, stop meddling with a lot of things at the same time and stop refactoring code. I got hired as a junior last month.
I was fired from my first internship. The culture of desk jobs is vastly different than minimum wage jobs. Also, be ready to do boring stupid work even though you got hired by showing them an awesome kick ass portfolio showing you were ready for really complex work. Be ready for those two things and you'll be fine.
@AA2 BE2 "The culture of desk jobs is vastly different than minimum wage jobs." - Really? You're saying the work culture at places such as flipping burgers at McDonald's is different than at software development companies? Who would have thought? Why should someone "be ready" for "culture of desk jobs is vastly different than minimum wage jobs"? You don't make any sense. Boring stupid work? With that kind of work ethic I'd say stick to flipping burgers, leave IT for other people.
Hey, I got a new job, frontend junior dev. But I'm worried about quitting my current comfortable customer support job. Like what if I mess up in this new role and get fired
@@felicitya.9077 if you don’t take the step, you’ll always regret. You can always get back to customer support but challenging yourself is what matters in life at-least for me. I’m still struggling in my job I don’t think I’ll stay here for long but I still think it’s worth my experience I’ll have more to learn after this if I get fired. I can only suggest you to take a step according to your financial situation, don’t risk it all if you can afford it go for it.
@@Allinonetvz if I lose this new job, I can still afford my basic needs for some time. I just don't want to be jobless and regret leaving my comfortable job. A dev role is all I've been preparing for all this time. This new job seems overwhelming tho I have people I work with who are ready to assist
@@felicitya.9077 then that’s great all you need is support, I’d say go for it. Also what was the job interview like if it’s a coding interview and you passed it companies won’t kick you easily, if it’s just a verbal test of programming concepts or an multiple choice questions test then you could be let off the hook in 3 to 4 months based on performance. You can also reach out to team members all the time for additional help, they’ll always guide and help you without asking any questions. Juniors are expected to be slow at learning so most of the companies will be fair. Mine however is an internship and by firing I meant I might not be getting an offer
you will be a very excellent mentor! love your vids ! pretty straight forward, not a waste of time! hope you'll be beyond successful in your passion! keep it up!
The problem with software dev jobs is that the powers that be do not have a computer science background, and they expect unreasonable things of programmers. They don't realize that a programmer is not a business analyst, they refuse to spec anything out, projects have nothing more than a title and no description, and they don't offer business feedback that would be essential to making design decisions. Also, they expect programmers to be able to do "time-filling" and "work-finding" which is not our expertise either. They put us in cubicles, and a cubicle doesn't teach, stimulate, or inspire anybody. It's like being in a cave. That is why those jobs have so much turnover. That is the reason I chose to develop my own applications and be a business owner instead of taking on jobs as a programmer.
Thanks Andy, very informative as always. I appreciate if you give us some advice about what kind of projects we can pick as a junior software developer, so we can hone our skills and see the benefit of our toils in practice by solving real world problems.
I appreciate the video, this is my first week on the job as a developer, I am very anxious, almost feel like I am impersonating someone. This might be a dumb question, but how do you find projects to work on on a daily basis in order to keep practicing?
This is great advice for ANY profession where you're creating something technical. I'm picking up software dev as a hobby and work full time as a mechanic. It's so interesting the parallels that I see with new technicians. The guys/gals that went outside the class and did a basic diagnosis/repair on their personal / family / friends vehicles did significantly more. 75% of the job is critical thinking and keeping a cool head, 20% is wrenching and 5% is paperwork.
Awesome video bro I'm not even a programmer or desire to become one and still find the advice you give invaluable. I'm more into Linux and sysadmin stuff keep up the good work! Maybe one day I might learn some development stuff :)
At least learn bash , an then some python (there are specialized books on python for sysadmins). I suppose you know what are the good books on bash. Here they are in order of difficulty : The Linux command line 2nd Edition 2019 Linux Command Line and Shell Scripting Bible, 3rd Edition 2015 Shell Scripting: Expert Recipes for Linux, Bash 2011
Focus on screwing up as least as you can. Don't risk it, ask for help, tell others you're unsure about what you did, don't just wing it and put it on production hope for the best. Sometime things will work for weeks or months smoothly then when it breaks people will find out what happened and diminish they opinion of you.
I don't have any experience in software but workplaces, yes. Small/tiny entities the owner or similar is there all the time. You either get along or not, nothing in between. Bigger companies like 1000+ people you tend to get lost in the shuffle and/or the likelihood of another being like you is much greater. You have the time and space to adjust if needed.
May I ask a question I'm not sure has been asked or not, but how often do you need to look at time complexity? Is it ever necessary to optimize an algorithm to shave off a few microseconds? Are there areas where this is done routinely at all?
Keep working, coding is a marathon and not a race, make slow progress not fast, go into things deeply, be motivated, and dont be too critical we are all strugling
theres a series of book called Cookbook of X where X is a language/framework whorever i think about tutorials, books and courses i remember that book, when you learning normaly people will teach you a recipe "lets do a chat with input and output" let's make a menu with "switch" or things like that, people have to figure out that they have to try a little new flavor together with those recipes, take something out, put another what will happen if i put one code inside the other, if you are not confortable with projects, try little changes and misture some keywords to see the result, the pc won't explode relax.
Well to be honest, I don’t see interns are different from regular employees and all of them would know you are on learning curve so you would get more instructions while they assign new task
@@rdxx4073 ok, To find the internship is easy. How you perform in interview is matters. keep applying in intershala.com, soon you will get internship in reputed startup.
honestly, it depends on the company. Some companies want you to drink the kool-aid hard. Some only care about your technical prowess. Some will be nasty to you no matter what you do. Haven't watched the video
Got my first dev job as a consultant and feeling a bit overwhelmed, I’m pair programming with a senior Dev and one of the projects we’ve been working on code bases from 8+ years ago where the senior dev is struggling as well to work on it. I just feel like without pair programming I don’t offer much and in fear of getting fired
Hi, Andy. I'm a non-English speaker but I love programming. Recently I began to learn Python and I'm learning quickly about it. The problem is that I love programming but my English is not very good and I want to improve it. I know it isn't necessary to know English to learn programming, but I want to know both very well. What do you recommend me to do? It's very important I improve my English in 3 months. Should I improve my English first and give up programming temporally and begin learning in January? My dream is to learn programming and build some important and useful app but my programming knowledge are very basic and I need some months/years to build a decent and marketable app to change the world. I could wait for improving my English but I would like to improve in these two months. Should I keep learning Python or better give it up temporally and focus on only improve my English?
I think you should just do what you enjoy doing. If English gets in your way of programming, that also means you're learning English as you're learning programming. So your English skills should improve naturally. Reminds me how a long time ago I already understood English pretty well, but reading long texts (coding stuff like documentation and tutorials) just felt tiring. But I kept doing what I needed to do for coding and the difficulty went away over time.
an advice works for no-one. very superficial, people following your advice get constant presure and fear to lose the job, your mind is busy non-stop burn out. what's the purpose getting that job for? to get all these?? no, don't listen to this advise!
Can you give me 10 mins back on my life? This is weird shit. You know bugs are harder to fix than develop the code. Do not throw bullshit here.a person fixing bugs can be a good developer but a developer cannot be a good bug fixer.
"you don't even know how to ask questions for help" The problem I've seen in this catch 22. You need to ask questions to get the job done but then those questions can reveal ignorance which then can be used as justification to fire you. At that point you're too afraid to ask questions because it could reveal something they will use to fire you.
Is this why in job descriptions(in addition to try and weed out probably the endless amounts of resumes they see) they list so many skills(some very obscure) and so many years in those skills? I mean almost none of those jobs I'm qualified for.
Did this video help give you some reassurance about your future job prospects?
Andy Sterkowitz makes me worried that I’m not good enough at coding
Certainly did.
@@hagenrobles3582 how come?
Absolutely. I underestimated by title but found it overestimated. Just keep crushing
Andy you are absolutely awesome and I appreciate the videos you produce. I've subscribed to your channel a few months ago so I can stay up to date on your productions. They have really helped me to push forward and not back out on my direction of becoming a programmer at the age of 41. After 4 years of uncontrollable seizures and a brain surgery your vids have given me some hope for the future! Thanks man!!
Best way to learn is by building projects . Get comfortable getting frustrated . Its inevitable !
But where can i get real life project's can you recommend some
@@rdxx4073 use you mind to think 🤔
So true. I learned so much just by building projects. I get so frustrated when I cant fix a bug but eventually figure it out. The process is great
Invent one yourself. Be creative; there are 3 milion apps in Google Play, so one more won't hurt.
You cant get fired if you quit first (taps head)
Lol. I could have made this video so much shorter. 🤣
Lmao
This is what i did :D
@@ojko12345 me too call centres are the worst haha
In your *first programming job* , you will be kinda nervous and confused. But *remember* !! Only starting out is difficult. Once it gets started, the *success* is on your feet. You get pleased and used to to work as a programmer. Nice day man!
nice day man ;)
Job job explaining that
Good*
I started my first dev job and it's been 10months. Still cannot used to the job, codebase, inability to accomplish work, no senior member in a team except manager and hence nobody to get answers from, except busy manager. Constantly being told to work faster. Asking questions often end up routing to manager, get them confused/pissed, so fear of asking right questions to manager while very slow in work, at the same time, too many doubts in unfamiliar codebase, delaying work. Everybody working solitary and fixing bug like less than 1 day while it takes longer for me. Stress from work everyday, anxiety, vomitting many times, and feeling I am not fit for dev or even basic human being as everybody else complete the job way faster, and my soft skills is also not improving since it just that the job requires looking PC screen for most hours, no in-person interaction.
@@jamestanaka686 Sounds like you should be looking for a new company then
I think people under-estimate how accepting more experienced devs are in jobs. I've always found that for the most part people are helpful to jnrs/interns we were all there once!
I started a job with one senior dev I work directly under and I've been baffled by how accepting he is of how much time I take doing things, how I fuck up, and just generally don't add much value
A junior developer with not much experience is an investment to a company, not a direct cash machine and I feel like he understands this really well
Totally. I was so happy to find a team that was supportive and encouraging. I really didn't know what to expect so it was a relief to land in a supportive environment myself.
I got my first web dev job 4 months ago and I feel lost and overwhelmed every day and just keep thinking I’m gonna get fired next week 😫
How's it going?
How’s it going now?
Teach me ur ways
Same with me 😂😂
Are you alive?
Starting your first industry position after mainly academic/tutorial-based study can be a tough transition. You're used to working on small, guided projects and suddenly you're dropped into a huge existing codebase with hundreds or even thousands of interdependent files and have to slowly piece together how different parts of it work, and start modifying/adding to it. It can be daunting, but if you get complacent, then suddenly you could be 2-3 months in and still have no idea how anything fits together or where to find what you need. That's a bad position to be in. Or at a startup or small team, you could be building something from scratch or expected to expand on a small starting point, which can be paralyzing in its own way. It's important to remember that other developers are there to help - that it's okay to ask questions or not know everything right away. Also that it's usually better to fail fast and often to reach success quicker than to never fail nor succeed.
I get it. I am in that place where spelling errors get me, I sit there and think, "this logic is good and impeccable, WHY IS IT NOT WORKING?" Then I have a mini-depression, where I think "Maybe this is not something I can do so ". But damn, I am resilient, I go back and BANG! IT HITS ME! it was such a small thing then I am so in love with coding again. awww...I love you.
the hardest part about it for me at this point is those small errors,not the logics or theory. Just misspellings etc.
Use a better IDE to help with your spelling.
@Ryan Dulac Not alone. lol.
@@dickie1874 I use Visual Studio, it's pretty alright. I will check if there isn't an extra plugin I can use for that
@Ryan Dulac I think you are right. Intellisense helps, but as you said it doesn't prevent me from making typos. I hadn't considered what you bring up about spellheckers, they wouldn't work so well with code. My problem is tha It type a variable/function a bit wrongly than Idid earlier in my code. Sometimes in not so easily detectable way. Like there would be an uppercase letter where there is lowercase. Sometimes your mind glosses over all of that when you have been sitting there for a while. That is why I think breaks help a lot, you come back and you don't take certain things for granted - its almost like you become re-acquainted.
@Ryan Dulac My experience too. :)
Don't expect a company to babysit you. Don't rush and apply for jobs after 6 months of watching tutorials. Make sure you have a good amount of skills that you can actually start a project on your own from start to finish before heading into the industry.
@ImRaizex Maybe a small CRUD app using your stack of choice. Start there
I already got fired from my internship, now I'm being self taught. It's actually more fun and it's on my terms.
Freelancing is the way I would say, if you know how to do it.
Why did they fire you in internship? I mean nobody expects much from an intern?!
@@matinsasan They told me that I have completed my 6 months internship in just 15 days and I'm ready to take on a complete project right away. But I refused and said it's not possible, I asked them for some time of 2-3 days so that I can at least understand the starter template they were telling me to use.
They said that it would be a waste of time and client is already expecting results, a few days later a new guy came to office looking for a job and the next day they fired me.
@@braindeveloperdimensional5579 Just to reassure you something at my 43. That shit had nothing to do with you, maybe they just hired the cousin's manager, since they don't expect anything from an intern, they just solved it with a relative to make a favor. Nepotism and favouritism it's a huge deal globally. So unprofessional from company, I'd say they made you a favor.
@@braindeveloperdimensional5579 so they thought of you just as some extra free resources instead of person that need to be trained 🤦
@@S4NTIS0 Agree 100%
A different way of looking at this is to ask yourself what kind of person would you hire if you had to do so? Then be that kind of person. 😊
I like how you summed it up though:
1. get very comfortable getting frustrated.
2. bleed now so that when you go into battle it's not that bad.
Like you said, it's simple advice but that doesn't make it easy to follow. Just as common sense is not all that common. 😁 Great video.
Well said Bianca!
you uploaded this video at the right time, I will start my new job in a few weeks
I hope i will get job soon :(
I'm reading your mind!
@@edvinas6069 You will! I almost gave up on my dream after being rejected and humiliated in brain teaser interviews, but you know what... Keep going! People always feel like giving up when they are nearly there. You will get it but you must work for it! I believe in you :)
@@AndySterkowitz Omniscient Andy! You gave some great advice too
@@ayoopdog Thanks for inspiring me!!! 👌
Feeling an unreal amount of fear as I start applying to my first dev jobs to change careers. This helped SO MUCH to calm my nerves - thank you! Already threw myself in the deep end once with a long-shot department move, lived through the struggle and frustration as I absorbed it all... I can look back at that as proof that I am capable. (I'm still terrified though I will be truthful!)
I disagree. I'm not a software engineer. I do software engineering as part of my RF engineering job. Job security depends greatly on your boss. But small companies can be MUCH more job secure because you are an essential part of the team. In big companies, you are disposable.
As someone who has seen a lot of students coming into a company those who have extra-curricular programming experience (programming/tech *projects* outside university) are head and shoulders above the rest.
The good news is that self-taught developers in my experience tend to have more idependent personalities and a couple more real-world projects under their belt than those who thought a degree would teach them how to be a developer. Either way the solution really is simple: do actual real world projects. Even if it's not a very serious idea/use-case at least come up with an ideas and execute them, and keep repeating that for the rest of your career.
I am a fresher can you please recommend where can i get real life project's in mean stack
@@rdxx4073 The most important thing of all is just repeating the process: idea, design, implementation, testing, evaluation. I suggest doing small an highly achievable projects so that you can iterate over this process without getting bogged down and burning out.
The point is to get used to not having training wheels and having a bit of experience with a decent range of technologies. University/college can't really give you this - you have to do it yourself.
Try participating in open source projects, there are many interesting projects out there. Some project even tag some bugs as being "beginner friendly" ( github.com/MunGell/awesome-for-beginners ). Make sure to pay attention to how other people communicate and do things - there's more to it than just writing code.
Or, just come up with an idea for an app on your own. How could your hobby, home or someone else's problem be solved? Is there something in development that could be made easier or automated? Then implement it and try to get it finished enough that you can publish the code up on GitHub/GitLab (functional, properly formatted, basic documentation, tests included). Even if it is a bit of a "toy" that's OK - just say "this was a hobby project".
@@harambeexpress Thanks, I was really confused on where to find projects to practice on.
This is the case for a lot of different jobs, not only programming, in my case i have an auto body technician qualification and if you didn't do a certain repair, like repairing a fender during school and when the employer wants you to repair that fender but you don't really know how - you were taught the theory of it, and only a bit of practice so you're going to be overwhelmed and helpless, the employer is going to say, "look if you can't do that i can't keep you working for me".
Obviously it's easier and also less expensive to do a lot of practice in programming than on auto body repairs, you only need a computer with an ide, no matter the specs, than body parts to practice, which can get expensive really quickly.
I got fired by my first developer job after 5 days lol. The next job was an even better opportunity!
Why were you fired in 5 days
@@ronitroy3174 I think they lost money? It was a startup
@@aliciaweenum1248 oh
@@aliciaweenum1248 I too recently got my first job. I'm overwhelmed by all the processes here.. hope so I'll be able to learn things.
@@ronitroy3174 it took me 6 months to get a hang of things. Ask other people how long they expect the training to be
Thank you, I appreciate this great advice, especially since I recognize that I have been guilty of leaning too much on books, tutorials, and the academic side of things rather than build any projects. I found this video very helpful for setting me on the right path!
If a person can't make anything from scratch without tutorials it's going to be tough for them mostly. At some point the training wheels have to come off.
You mean like, if a person can build a fairly complex project succesfully with heavy reliance on tutorials and books... that person will struggle a lot working for a company?
I feel like this is close to it but not it exactly, a large part of programming as far as I have been is using tutorials and books to maximum advantage. The trick is to work on something that's not from a tutorial or book one where you have to actively search for and research how to solve the problem and the answer isn't in one place or even in multiple places just parts of the answer are and you have to stitch them together and make some extra on your own.
Biggest reason I’ve noticed isnt being bad technically, but being bad at communication
I recently started a soft dev job at a very small company. But they do not expect much, my boss told me that he spent like 4 months getting into a new ERP system. I'm just writing docus all day long, explaining the features of a new framework, because the documentary by manufacturer is not sufficient. I also figured out how to write modules within 5 weeks of being there. But I'm still learning how to write software from this ERP.
I was recently announced that I will be on a conference about this framework by the end of this month. I love my new job. It feels so strange.
And .... I was fired....
@@Canleaf08... 2 months ago, loving your new job.. and now 2 weeks ago, you have been fired..? :(, why were you fired though?
@@Canleaf08 Honestly I'm not surprised you were fired.
You're Canadian right? Is English your native language or is it French? Your English is TERRIBLE, no offense. It brings up a lot of red flags to me just seeing your comment. Especially for a someone who is supposed to write documentation.
When everything was new projects and developers learned through getting stuff wrong, now people expect Junior Devs to know everything, paid to code... Huge red flags without Mentors.
I haven't been doing a ton of projects, but I hear this so often and I take Andy's word as truth, so I suppose it's time to get uncomfortable and build projects. I'm learning react right now and trying to master JavaScript
I was blessed with a great teacher who assigned very ambiguous projects. That was nearly 5 years ago and set a foundation I had no idea I'd be so grateful for!
1) making lot of projects
2) put yourself on challenging positions now before you get hired
3) life of software developer -getting stuck, problem solving and getting your way through it
Andy, although this video is couple of month old, it's valuable nonetheless, I think I stated my situation to you before, it's not so much I'm struggling with the subject, I'm not, because that's what I do / did before, but the application(S) size, and enormous technical depth of the project I'm working on now, makes my past experience looks like a child play, so my personal advice to anyone going from small organization to a much larger one, get ready for the big time, by studying, practicing and building side projects in order to ensure success, and, consulting with Andy wouldn't be a bad option either.
Keep up the great work.
I think we can all agree the markets go up and down. With all of the fear out there right now of a potential market downturn. how do you see that affecting a developer in their first job?
i always had that question in my mind thanks for clearing it
Excellent
The reality is you're gonna get stuck on the projects no one else wants to do and that many more before you have been fired over. Get as much exp as you can in that case and keep applying on the side till you find something better.
If your interview challenge was to spot a basic syntax error in a PHP script and you get hired the following day to code a full stack ios native app with node and mongoDb from scratch within 30 days, you know you're in deep $hit. - it happened to me
Dig in without hesitation. Google questions related to your language or third party tool. Ask for documentation on anything developed on-house. If you can't find answers, learn how to use SCM to find the developer that added the code and ask them (people love talking about their own code). If none of that works, ask your manager or team lead. Also, be honest about what you don't know. There are so many different technologies out there and no one knows them all which means that even senior engineers have to ask questions.
Thank you ... seriously thanks for all that you do.
Insightful video ! Very true. Thank you for this 👍🏻
Glad to help!
Actually excellent advice, as a starting developer who suffered from all these stupid mistakes and pitfalls myself, I can appreciate deeply how important the right attitude is. If people were "expecting all these cool things and tricks" from the video, joke's on them
I start my new job today. Searching for a video like was the first thing I thought of when I woke up this morning 😂
Good luck Kenny!
How's it going? Update?
Even building projects can’t fully prepare you for the scope and scale of massive enterprise applications that have many teams that build and maintain them. Sometimes the only way to truly learn is take the risk and get your hands in a real job.
True and not true. You can be better prepared to handle complexity of enterprise apps by building projects on your own. You should have mentorship/teammates who can you help you assimilate at your first job as well.
I think you need to fork (big) open source projects and try to understand the code and add features if you want to improve in that regard. When you make your own projects you basically know and understand all the code which isn't going to be the case in real world projects.
Exactly. There is lots of ambiguity, change, and frustration out there. Keep calm and figure it out. Get it done and you'll be fine.
It's like me when i make a simple app, and i don't know what to do, then it's my first time to open StackOverflow, reading some code and I don't know how to use it in my program 😂😂😂😂
I enjoy the videos by the way, I'm a beginner but I think it's so cool to come up with a way to program something and have it actually work. It's great to be able to hear these presentations and realize certain issues I have are normal, great to be able to motivated and inspired here.
Thank you for the advice. I'm in the process of learning how to code and this is what I expected I'd need to do.
Unfortunately, today I got fired in my first job. :(
Best advice I’ve ever been given so far in this journey
I have found myself in my first dev job, and I have to learn a whole new tech stack...It is so overwhelming. I am only 19, the youngest in the dev team and It is in a tech startup. How does ever become more comfortable?
I will probably start in a month my first dev job in a start up with some technologies I never done or have little experience, I feel comfortable yet anxious, not anxious because I think I will fail, anxious that I might not be par to what they expect me, but hey.
I am really comfortable with my learning capabilities. I spent countless hours in front of my screen sacrificing my social life and fitness because I wanted to get into this field so bad. And this is what matters. Keep moving forward, you deserve a position in this field. 👍
@@kareklopodaros hey I am in a similar position having to learn a new stack for a job. How is it going?
@@aaronclare2682 It's going great, I am learning how to work as a team, stop meddling with a lot of things at the same time and stop refactoring code. I got hired as a junior last month.
I was fired from my first internship. The culture of desk jobs is vastly different than minimum wage jobs.
Also, be ready to do boring stupid work even though you got hired by showing them an awesome kick ass portfolio showing you were ready for really complex work.
Be ready for those two things and you'll be fine.
@AA2 BE2
"The culture of desk jobs is vastly different than minimum wage jobs." - Really? You're saying the work culture at places such as flipping burgers at McDonald's is different than at software development companies? Who would have thought?
Why should someone "be ready" for "culture of desk jobs is vastly different than minimum wage jobs"? You don't make any sense.
Boring stupid work? With that kind of work ethic I'd say stick to flipping burgers, leave IT for other people.
How did you get fired if your portfolio was impressive?
Hilarious I just celebrated last week since i got the job, now I’m searching for how to not get fired within my first week 🤣 god help me.
Hey, I got a new job, frontend junior dev. But I'm worried about quitting my current comfortable customer support job.
Like what if I mess up in this new role and get fired
@@felicitya.9077 if you don’t take the step, you’ll always regret. You can always get back to customer support but challenging yourself is what matters in life at-least for me. I’m still struggling in my job I don’t think I’ll stay here for long but I still think it’s worth my experience I’ll have more to learn after this if I get fired. I can only suggest you to take a step according to your financial situation, don’t risk it all if you can afford it go for it.
@@Allinonetvz if I lose this new job, I can still afford my basic needs for some time.
I just don't want to be jobless and regret leaving my comfortable job. A dev role is all I've been preparing for all this time.
This new job seems overwhelming tho I have people I work with who are ready to assist
@@Allinonetvz Thanks for replying, sorry I should have said this first
@@felicitya.9077 then that’s great all you need is support, I’d say go for it.
Also what was the job interview like if it’s a coding interview and you passed it companies won’t kick you easily, if it’s just a verbal test of programming concepts or an multiple choice questions test then you could be let off the hook in 3 to 4 months based on performance.
You can also reach out to team members all the time for additional help, they’ll always guide and help you without asking any questions. Juniors are expected to be slow at learning so most of the companies will be fair. Mine however is an internship and by firing I meant I might not be getting an offer
Thanks for your advices it is helpful for me 🙏🏼
you will be a very excellent mentor! love your vids ! pretty straight forward, not a waste of time! hope you'll be beyond successful in your passion! keep it up!
Great video! Thanks for sharing!
Glad to hear Katy :-)
The problem with software dev jobs is that the powers that be do not have a computer science background, and they expect unreasonable things of programmers. They don't realize that a programmer is not a business analyst, they refuse to spec anything out, projects have nothing more than a title and no description, and they don't offer business feedback that would be essential to making design decisions. Also, they expect programmers to be able to do "time-filling" and "work-finding" which is not our expertise either. They put us in cubicles, and a cubicle doesn't teach, stimulate, or inspire anybody. It's like being in a cave. That is why those jobs have so much turnover. That is the reason I chose to develop my own applications and be a business owner instead of taking on jobs as a programmer.
Thanks Andy, very informative as always. I appreciate if you give us some advice about what kind of projects we can pick as a junior software developer, so we can hone our skills and see the benefit of our toils in practice by solving real world problems.
This video just started playing in the playlist and when he said "im gonna teach you how to not get fired..." I just LOLd
I appreciate the video, this is my first week on the job as a developer, I am very anxious, almost feel like I am impersonating someone. This might be a dumb question, but how do you find projects to work on on a daily basis in order to keep practicing?
This is great advice for ANY profession where you're creating something technical. I'm picking up software dev as a hobby and work full time as a mechanic. It's so interesting the parallels that I see with new technicians. The guys/gals that went outside the class and did a basic diagnosis/repair on their personal / family / friends vehicles did significantly more. 75% of the job is critical thinking and keeping a cool head, 20% is wrenching and 5% is paperwork.
Excellent video, thanks Andy ^^
Awesome video bro I'm not even a programmer or desire to become one and still find the advice you give invaluable. I'm more into Linux and sysadmin stuff keep up the good work! Maybe one day I might learn some development stuff :)
At least learn bash , an then some python (there are specialized books on python for sysadmins). I suppose you know what are the good books on bash. Here they are in order of difficulty :
The Linux command line 2nd Edition 2019
Linux Command Line and Shell Scripting Bible, 3rd Edition 2015
Shell Scripting: Expert Recipes for Linux, Bash 2011
Focus on screwing up as least as you can. Don't risk it, ask for help, tell others you're unsure about what you did, don't just wing it and put it on production hope for the best. Sometime things will work for weeks or months smoothly then when it breaks people will find out what happened and diminish they opinion of you.
How to ask questions and helps from your co-workers?
I don't have any experience in software but workplaces, yes. Small/tiny entities the owner or similar is there all the time. You either get along or not, nothing in between. Bigger companies like 1000+ people you tend to get lost in the shuffle and/or the likelihood of another being like you is much greater. You have the time and space to adjust if needed.
May I ask a question I'm not sure has been asked or not, but how often do you need to look at time complexity? Is it ever necessary to optimize an algorithm to shave off a few microseconds? Are there areas where this is done routinely at all?
For any beginners who dont know where to start heres some tips
1st : Learn basics
2nd : Make a simple project like a notepad or something
What are the basics
Thanks you for your advice it’s very useful thank you
I want to be technically skilled but I struggle with coding. Uhg. Am I just not cut out for developing software?
Keep working, coding is a marathon and not a race, make slow progress not fast, go into things deeply, be motivated, and dont be too critical we are all strugling
@@umar_shahzad what he said. It takes time.
Great video! I totally agree with this
theres a series of book called Cookbook of X where X is a language/framework whorever i think about tutorials, books and courses i remember that book, when you learning normaly people will teach you a recipe "lets do a chat with input and output" let's make a menu with "switch" or things like that, people have to figure out that they have to try a little new flavor together with those recipes, take something out, put another what will happen if i put one code inside the other, if you are not confortable with projects, try little changes and misture some keywords to see the result, the pc won't explode relax.
Great distinction between dynamics of ‘big’ co VS ‘smaller comp’. Can you define # of employees for small med large?
Great video!
I'm going to start my intern job as full stack developer. How much did they expect from me?
Well to be honest, I don’t see interns are different from regular employees and all of them would know you are on learning curve so you would get more instructions while they assign new task
Can i ask from where you are doing the internship as i am also learning full stack development but finding hard to get internship
@@rdxx4073 you are from?
@@lohithkumar8257 west bengal
@@rdxx4073 ok, To find the internship is easy. How you perform in interview is matters.
keep applying in intershala.com, soon you will get internship in reputed startup.
Andy! How much does your guidance cost on average?
I get fired all the time, I suck! ☹
Where did you get that shirt?
"Bleed." is actually a very good programming advice. I guess that's just the way of things. xD
Welp, I just got fired today. Found this video 5 days late :(
Continue learning and apply for more jobs. Get good, get great, get better.
@@MaugzSR :(
@@superjokerrr Why are you sad????? Don't be, I was trying to encourage you!!! v.v
4 months late :(
how is it going superjoker?
Man I think I'm going to get fired everyday
Who else is here after getting 1st programming job
Thank you 🙏🏼
yeah.....I'm probably gonna get fired : (
Are there websites where you can pick up new projects ?
What are good starting projects for beginners?
honestly, it depends on the company. Some companies want you to drink the kool-aid hard. Some only care about your technical prowess. Some will be nasty to you no matter what you do. Haven't watched the video
Great
Your expression makes me feel like I just told you I got fired
Why this video is so f**king scary....
Now, I'm sweating....
Any summary for this 7 min video?anyone ?
5:12 😂
Jissmon Jose 😆
Question: are employers asking for a college degree ?
Have you looked at any of the job ads?
信心 confidence
i wish i saw this before i got fired from my first programming job😂😂😂
I’m so disappointed at this whole field
How to not get fired?
Simply quit before they fire you lol
😂😂😂😂😂
Got my first dev job as a consultant and feeling a bit overwhelmed, I’m pair programming with a senior Dev and one of the projects we’ve been working on code bases from 8+ years ago where the senior dev is struggling as well to work on it. I just feel like without pair programming I don’t offer much and in fear of getting fired
Hi, Andy. I'm a non-English speaker but I love programming. Recently I began to learn Python and I'm learning quickly about it. The problem is that I love programming but my English is not very good and I want to improve it. I know it isn't necessary to know English to learn programming, but I want to know both very well. What do you recommend me to do? It's very important I improve my English in 3 months. Should I improve my English first and give up programming temporally and begin learning in January?
My dream is to learn programming and build some important and useful app but my programming knowledge are very basic and I need some months/years to build a decent and marketable app to change the world. I could wait for improving my English but I would like to improve in these two months. Should I keep learning Python or better give it up temporally and focus on only improve my English?
I think you should just do what you enjoy doing. If English gets in your way of programming, that also means you're learning English as you're learning programming. So your English skills should improve naturally. Reminds me how a long time ago I already understood English pretty well, but reading long texts (coding stuff like documentation and tutorials) just felt tiring. But I kept doing what I needed to do for coding and the difficulty went away over time.
an advice works for no-one. very superficial, people following your advice get constant presure and fear to lose the job, your mind is busy non-stop burn out. what's the purpose getting that job for? to get all these?? no, don't listen to this advise!
Trump >> " YOU ARE FIREDDDDDD GO TO HELL "
Lol
Can you give me 10 mins back on my life? This is weird shit. You know bugs are harder to fix than develop the code. Do not throw bullshit here.a person fixing bugs can be a good developer but a developer cannot be a good bug fixer.
"you don't even know how to ask questions for help"
The problem I've seen in this catch 22. You need to ask questions to get the job done but then those questions can reveal ignorance which then can be used as justification to fire you. At that point you're too afraid to ask questions because it could reveal something they will use to fire you.
Is this why in job descriptions(in addition to try and weed out probably the endless amounts of resumes they see) they list so many skills(some very obscure) and so many years in those skills? I mean almost none of those jobs I'm qualified for.