@@encapsule2220not sure if sarcasm but yes. Have extracurricular activities like in school. Go to the park with your dog if you have one. To the gym. To the bar with friends. You got it
This video really made me feel so much better about where I am currently and the process I’ve gone through over the last two years to get here. Thanks for all the help you’ve given along the way.
for getting a job, I'd say spend more time making connections with other developers who might be able to refer you (spend time in online communities, join in person meet ups, etc) and work one 1 large project that you can showcase / talk about.
Top 6 tips by cody: 1) Just build stuff 2) Build LARGER projects 3) Find a team (collaborate) 4) Expose yourself to as much as you can 5) Teach others 6) Get out of comfort zone
One thing that I always recommend to people is to explore other people's code, browse other projects as an inspiration and to see many approaches to many problems and like that you will have a better understanding and you will adopt new ways to tackle things especially when debuting! Good luck everyone and happy learning
There is this technique you can use when learning after you get the basics down. First, think of a problem. Second, try to solve it yourself. Third, look at one of the answers from an experienced programmer and compare and it teaches you really fast. Let me give you an example... You want to draw a square on screen. Using documentation online, no help otherwise, you try to draw the square on screen yourself. It's gonna make your brain really get a workout. Once you've drawn the square on screen, you'll probably realize it's not well optimized or something. So then, you look at how others do it, and you may find that they use OpenGL, and you go like 'huh...I need to use a graphics API to use the GPU?', etc etc...., and seeing how others are doing it compared to your own coding, you learn ripping fast that way. That, and stepping through others code, but again it's better to try to solve a problem yourself on your own and get it wrong first, then compare. This is how I learned basic HLSL programming. I would look at others shaders and be like 'What...? How do you even BEGIN to learn this???' because of parallelism in shader programming. So, I just took a simple fragment shader, and started just trying to control things. In shader programming, you don't draw one pixel at a time, so the pixel it's drawing to screen could be anything. I realized that there's a difference between a pixel and a texel.... This all happened because I was testing it out myself, even though manuals and guides and tutorials and documentation that I read all told me 'a texel is different than a pixel' and explained it clearly, it wasn't hitting me at all, it was in one ear and out the next. It wasn't until hands on testing on a tiny step by tiny step level that finally I got it down and understood what it was, and I was able with math to start making upscaling algorithms for HLSL and GLSL. Not the best ones, but I was able to do things like that, among other things. Just go in there alone, read manuals, and try to do it yourself before asking or looking for help or looking at how others do it. Get it wrong first, then compare.
I like to read open source projects and compare it to the way I'm writing my code. That way i can quickly adapt to best practices of doing things and learn very quickly from my mistakes. For example if I'm learning NextJS and working on a new project, I'll read a medium/large open source project in that tech stack and try to understans the setup/folder structure etc.
Nice video Cody! I really like your visual style of delivering this message. Very very good advice and honestly could apply to most creative disciplines.
one thing i’ve learn throughout my coding journey, especially when you use libraries/plugins/frameworks is try to dig underneath.. understand how those tool works.. what’s the function/class doing when you call it. what happens when you pass a data to it.. etc
I know this is not the place to say it, but I'll say it, I think maybe you should rethink the idea of smart people that figure it out on the fly, apart from the fact that there's no clear way to tell how smart is someone, and that "iq" could change overtime, I think experience can be way more important than just iq, so try to make your experiences valuable, and trust them! I know I may be wrong but I think sometimes believing in something wrong to trick your brain to perform better can be helpful.
I applied for a SDE 2 position (i'm SDE-1 currently with 1.5 yrs of exp) and I got a rejection letter immediately :( even though i was confident... Anyway, great video, really appreciate it, these videos are too good!! Also if possible, could you please create a tutorial where you start from scratch (can be a mern app or anything u like), and setup all things like multiple envs, ci/cd, deployment, like a full lifecycle of a project (mirroring production), i think it will help lots of people out here... Again thanks!!!
I have been following you for more than 6 months sir. You are really helping people grow and become a better developer. Thank you for such amazing advices
Should i keep all my repos public?. Will that help me get hired because when recruiters see my github they may only find like 10-15 repos and think i am a junior dev
Thanks, really appreciate this video as someone on the lower end of the scale. Trying that leap from building small stuff to a larger project that I feel is way over my head, but picking at it bit by bit
Your honesty about how you did tutorials and sponsors is refreshing. I am in an online bootcamp (Colt Steele) and seeing your videos keeps me motivated. Not sure if you will ever see this but I wanted to personally thank you... - Joshua
About 5) Teach Others: I think a very easy win is to properly set up your stack overflow "watched tags" with topics you have learned, or are learning. Periodically, as a break from whatever project you're working on, open up SO questions and filter it to your watched tags, then see if there's any easy questions you can answer. At first, I could only answer questions which had just been posted - easy ones which hadn't yet been answered purely because they were posted a few seconds ago. However, they were very helpful at getting my confidence up
3:56 I disagree. I think absolute beginners should see these highly scripted tutorials, without the problem solving steps. That's because if you just stop what you're teaching to try to solve a problem, experimenting some possible solutions, might be confusing for absolute beginners. Then, after they are more familiar with the tech, then absolutely they MUST work on their problem solving skills. At the end of the day, solving problems is what we do. Then after that, nowadays I'd rather read the docs or watch a fast paced video (like Fireships videos) when I'm trying to learn something new.
I agree a lot with the approach of "live coding" while teaching, I do this all the time while teaching at trade schools. My advice however for anyone else who want to teach a subject is to prep by building it first the day before you teach to remove some of the messiness.
I would suggest tip nr 2. Code refactoring - Learn to improve your code and don't be afraid to throw away old one. In such way you will strive to perfection.
hey I really like the content on your channel, recently I've been trying to learn React to become a front-end developer. Most of my time I learned multiple languages at an intermediate level such as C++, C#, Java, Python and Visual basic but I've never really built a proper application (beyond). I started learning react in a few days ago after learning "enough html / CSS (I chose to know the basics of html and css and learn on the way so I can just get into JavaScript as soon as possible). So far I'm creating my own web calculator after following the react learn project tutorial. So I want to ask after I finish this project should I just continue creating projects or try to contact a mentor to critic my code?
I have actually been trying to improve and the one aspect I alway get stuck on is finding projects to work. What do you suggest in terms of projects that will level coding and problems skills...
I found that exposing myself to more 'stuff' just takes me further and further away from the basic principles, when you start learning the minutiae of MVC and OOP paradigms, templating engines, then on to server and resiliency, you no longer can be bothered writing out tables in HTML or configuring forms to send data (and BTW, do you use XHR or newer fetch methods for that or do you use something fancy like Websockets and if so which framework? which language?), even the most basic element HTML itself is far from the only or the predominant syntax oh and I couldn't even finish this message because it's too long
I could see that, but it’s better if you have a broad view of how web dev works even if you might not use the tech. All these ideas build upon each other
My fist dev job was a mid level react developer and that's because I was extremely knowledgable, the code I submitted on the test was great and I demonstrated my approach to specific needs the company had at the time. I also did a 6 month bootcamp without any degree and spent the following 18 months coding literally everyday and doing pretty much everything in this video. Only thing I didn't do was conferences
I had a similar experience. Went from Software PM to Front End but with very little knowledge. Being thrown in at the deep end had its benefits but then had to work on fundamentals (and still am)
@@daedalus5070 Oh that's quite interesting. Do you mind going into more detail about what your experience during the first few months of that transition? I think that's an impressive, gutsy move from you.
I know this is not going to make much sense to most of your audience, but I consider it essential to learn english for those of us who are not native speakers. Definitely a game changer for people in Latam.
