One of the biggest advices I got in my early days as a developer was "Learn how to read and use any documentation". And after 25 years all I have to say is it was worth it.
@@hajji384 What really slows your down is your laziness to take an extra step to your future. With this attitude you need to look for a simpler career like making burgers.
Some documentation are terribly written and hard to understand. Around 80% of it. That's why we have forum like stack overflow because if docs were clear there wouldn't be any confusion on how to do xyz.
Not where to find it. *What* to find. Understanding when to use a for loop and when to use a while loop is more important than memorizing the exact syntax of either.
@@nikolaymatveychuk6145 Wrong. You use a *for* loop when you know (or the incoming variable will hold) the number of iterations to repeat the loop, and you use a *while* loop when you want to iterate through a loop _until_ a condition is met. Or to be more concise, a for loop uses a predefined condition, while the while loop uses an open-ended condition based on commands inside the loop. For loops iterate for a preset number of times. While loops iterate till a condition is met (conditions can be functions, formulas, etc). Sure, on the surface, they will both "do the same thing" but not always and not the way you always might expect it. You can't always swap out a for with a while, or vice versa, and always get the same results.
@@PhilLesh69 "You can't always swap out a for with a while, or vice versa, and always get the same results." - yes you can :) I just showed it. "For loops iterate for a preset number of times" - no, they don't. In most languages a condition that you put to the middle section of a loop definition is checked before each iteration. So, it is also an open-ended condition (in C++, java, php, javascript, etc... sure, it is wrong for pascal, basic and some other languages with a different for-loop syntax) "you use a while loop when you want to iterate through a loop until a condition is met" - not exactly. I use it to iterate something while a condition is true. You speak about pre-conditions and post-conditions and you are right that a programmer need to know when to use each of them, but it does nothing with for and while loops. And again nothing can stop me from using break statement on some condition at the end of a loop's body. "You use a for loop when you know (or the incoming variable will hold) the number of iterations to repeat the loop" - no, often I don't know it. That's why the for-loop definition in C++ has syntax "for (initialization; condition; final-expression) { statement; statement; ... }" and not "FOR counter := startValue TO endValue" like it is in pascal or "FOR counter = startValue TO endValue STEP incrementStep" like it is in qbasic. --- So, what you really need to know is how loops work, when to use it, and how to make pre-conditioned and post-conditioned loops. :) As Uncle Bob says, there are only 3 basic things that you need to write any program: instructions, conditions (branches) and loops. So, if you know how to execute an instruction, how to choose a branch of code based on some condition and how to repeat any block of code many times - you are bound only by limits of your imagination xD
As someone who has been a professional for several years and now working at Google , I completely agree. You will learn best by doing and implementing. I've learned the same thing several times but each time you pick it up way faster. You will go through the motions and know how to do most of your daily duties and the rest you can look up.
@@Videosuser I guess thd job interview is like (can you make a functioning website or app etc) then you say yes... it does not specify what type of app and how it will look or function etc as long as it works
Its still memorizing. because your brain knows what to do and memorizes the steps needed to accomplish the tasks needed to complete the code. When you repeat something and over over, believe it or not, your brain memorizes what you are doing. again you still have to memorize. its called long term memorization.
I always say the same thing, slightly differently " i don't need to learn by heart things, I am not a computer". But if I did not memorize things i couldn't creat new ways more efficient or innovate. You should memorize but in general.
I can add my own words here - When you understand something like those tech concepts two things happen. 1. You feel good for some time 2. It starts living inside your brain so you do not have to memorize it. It is absolutely possible to forget it. But if you do and then you refresh your memory about the concept, the above process repeats itself.
This was my approach in university. I attended lectures empty-handed, and focused on firmly grasping the concepts while everyone else jotted notes down furiously. I did quite well as a result, and set myself up better for career challenges down the road.
some people learn better that way. I am a visual learner as well. I can take notes all day but my information reception comes from watching it being done or seeing it drawn out kind of way. in high school and college I never took any notes and managed A's and B's occasionaly a C.
You need to tho, Im pretty sure the video is implying to real life work of a developer. When i was trying to apply for a job, i wasnt even allow to use google lol. So until you land a job, you need to memorize, just the basic, like for loops for coding interview and maybe how to do CRUD.
@@midenddeveloper9361 To be fair if you need to explicitly memorize the very basics (like loops) you are not a very good developper. On the other hand if a company cares about you writing 100% syntactically correct code on paper, they are not a very good company.
As a beginner, I needed to hear this. I'm doing a course that has given some intermediate challenges of reversing strings etc but without using .reverse() as a means to practice. I tried so hard to remember what to do and felt like I was cheating looking at the documentation. Thanks for the helpful tip.
Me as a former nurse of 10 years I left the field due to the pandemic and now I’m in a coding bootcamp. I’m struggling because I’m trying to remember what a Var is or a string, or a Boolean 😂 my mind is gonna explode. I’m trying to learn this in a whole new way and this vid helps a ton. As a nurse you memorize a procedure, as a developer you develop a procedure. Thanks bro!
You just gained a subscriber. Starting my first programming job at the end of the summer. Your videos have helped me focus on the task ahead without trepidation.
There are some things you should memorize. But the most important part is understanding the fundamentals and how the code works. And unless you have a photographic memory, it's not even possible to memorize everything anyway.
I think if we understand something clearly and can use the concept with confidence it is already learnt . Is there really something like photographic memory ?
I wholeheartedly agree that learning concepts and how the language as a whole works is the priority, however, once you have the basics down packed, learning the common parts of the standard library and any frameworks or libraries that you commonly use helps immensely. You don’t need to memorize exactly how they work or every parameter, but at least be familiar with them and aware of their existence.
I would be more than appreciated if you can just hint me up on how may I learn "how the language as a whole works ". I think I struggle learning basics, the concepts not that I memorize anything but I think I cant write or buid anything without looking it up on the internet.
I learned to program (in assembly language) around 1977 - the days of batch programs running in 100K of memory and 99% of all input/output based on magnetic tapes and punched cards. The "core" principles I learned at that time are still valid. Whatever the higher level additions like "events" may have added, any program boils down to: 1) sequence : instructions are executed in sequence, 2) selection: a test to break out of (1): if test goto else exec next instruction 3) iteration: repeat a given sequence until (2) a selection is false. I can also recommend studying the abstract description of programming languages like Pascal in BNF or SQL. It helps you understand structure / semantics (meaning) as a solid base for understanding syntax - the difference between programming languages.
I think for programming, you are exactly right about memorizing the basic 5 elements to programming, (I would also include syntax), and then language specific important things. Then.. I usually just pull up old programs or google things that I don’t remember exactly like what you said.
I partly agree but not completely and I would add 2 scenarios I discussed lately … - With a teacher: We brainstormed about teaching kids concepts vs. having them learning by memorization and repetition. Conclusion: After years in the field we underestimate the necesity to memorize mainly the basics to have them present in any moment. Everyone learns differently. Some by reading, some by listening, some by watching, some by doing. Sure you have to focus on the concepts, but in programming you also need your toolbox as in a productive environment you don‘t have time to look up the basics over and over again. This brings me to the second discussion where memorizing code is very important. Working on bigger projects you have to find a way to oversee the code and remember the specific statements, even if the aren‘t written by yourself. Without this ability you loose the bigger picture. These are just 2 areas to keep in mind where the ability to memorize is heavily important, whichever way of learning you choose.
Video idea: film the process of you actually preparing for a video, coding the app for the first time, googling all the things you get stuck on, etc. Because when you do it in a regular video, it seems like you know everything without any mistake :D
I remember trying to memorize 7 pages of code and getting messed up in lab exams. Never tried memorizing instead I tried to understand what functions to call and what variables are being used. Hope it helps
wish i watched this my first year into coding lmfao. luckily im passed that phase and am learning concepts etc. I DO THINK a bit of syntax memorization at this beginning is clutch tho
Totally agree. Better to understand concepts and theories. Learn how to write clean maintainable code. Learn concepts like design patterns, test driven development, how to convert legacy code, etc.
this info helped alot. as a self taught I was focused on learning every tag and bracket in JS and I thought I was billy badass cause I could write scripts then I started trying to do css and html classes and I was like...oh shit its a whole different language. I felt overwhelmed and thought to myself how could anyone memorize all this and thought that this stuff was just to past me and I am to old to learn all this now. but watching the video and coming back after a few months I can say focusing on concepts over memorizing every single little thing not only improves your speed and adaptability to different programs or languages but it helps reduce that burnout from information overload. I currently have 6 months of coding under my belt and working on stacking my portfolio in github and hopefully by 2024 Im looking to be marketable. Also working on a cool app that I want my first project to be and wow whoever is trying to pick me up.
Me: someone who can't remember shit Interviewer: what's a function? Me: ...pulls out Javascript reference book Interviewer: Get Out... we use Google here...
Yeah i just had a interview and the interviewer told me not to use internet for any kind of help because it's just a copy paste process. He wants me to do everything myself using only my brain 😂😂😂 And i made my habit to write code using "Emmet(auto completion)" and in interview i almost forgot the syntax because he told me to write code on the paper 😂😂 And the fun part is "I am a web developer frontend and he asked me to write code in c++ on paper without any kind of help from internet😂" I told him to watch my CV again, i know only html, css, JavaScript, bootstrap but he still asked me those stupid questions" This was my first interview and i was like what the hell is going on here😂
Hey just wondering if you manage to find a job yet? I am learning exactly the same you stated above(html, CSS, Java and bootstrap) and was curious if I could start looking for job with this.
You are correct about learning and understand concepts rather than everything. This applies to anything, not just programming. The important part is having the ability to problem solve which involves coming up with multiple ways to solve a problem, choosing one and generally knowing the tools available to you to accomplish the task. A google search does no good if you don't have a clue as to what you are searching for, which sometimes has to be asked in a multiple of ways before google delivers what you are actually looking for.
*shrug* call it anything you'd like. The ultimate objective is to solve a given problem. That is one of the negative traits of the education system. School teaches you how to take tests, not solve unknown questions. (unknown as in the teacher doesn't have the answer sheet.) Not using Google is like choosing to use a hammer instead of a nailgun. Even if we are only viewing this from an optimization standpoint, why would I waste time recreating a solution to something that has already been solved? Once all of the trivial tasks are finished; now you can spend time pondering the actual problems. (My subjective 3 cents.)
5:16 THIS!!! I remember my young self trying to explain to my parents/ teacher why I don't need to remember my times tables. Sure it might make me faster at those specific problems since i have the answers remembered instead of having to figure it out but it doesn't make me better at multiplication or math at all.
This video has helped me immensely. I have been coding for years, always try to memorize and now I realize it is fruitless. I end up forgetting the things I try to memorize anyways but it's always the concept you have to focus on. I think I did this because I just hate relearning things.
nice explanation sir! when he said, "When we learn math, we don't neccessary memorize the numbers (2+2 is 4) but we simply know the concept and use calculator." Ah at this moment, I get what he meant. We don't need to memorize all of the code but instead learn how is the concept.
This is actually the first video I am commenting on since i started watching RU-vid. This shows how good your content is. I like how you used the math scenario. Keep it up.
it happened to me a lot when i started coding i was thinking that if i want to be perfect i need just to memorize all these things , but over time i discovered that all what i need is mastering algorithms then i will need just to apply the method of learning on demand . thank you kayle for these valued info .
The main reason people try to memorize things is so they can remember them correctly and there's nothing wrong with that dude, you should be trying to at least remember the things you're learning/doing, just don't rely on memorization to use as your sole tool.
In my personal experience programing, trying to memorize code from others and own is a really bad idea. It is like trying to remember every word you write in a tesis word by word instead of have the whole idea and sumarize it.
First of all thanks for your time. I was thinking about how to memorize these codes in R and Phyton. Today you cleared my biggest issue and now I focus on learning, the concepts of code and how to use them. There are tens of thousands of codes and it's impossible to memorize them. We just learn how to use different factors in code and commands. We can save codes and use them according to our data. For example, I know what to do when importing data from excel, what is iris data set is, how to skip the character variable when doing PCA, etc. Now I do not need to memorize the whole script, I just need to learn the things in the script and how to use them.
I just wanted to say that I found this video at the right time and thank you for making this. I just started a month ago and I was memorizing these things, thanks for saving me from my own torture
Modern Programmers: "Stop trying to memorize coding!" Every Fortran/punch card programmer that I have met: "Man, I don't remember any of that stuff I used to do."
Man I just started the odin project a few weeks ago and I have been trying to memorize some of the code by taking notes. I was able to memorize most of what I have been writing but I am glad that I found this video, I will put this into practice.
Instead of memorizing, I build my own of what i call "short hand librarys". It's basicly a library of functions and conseps for doing tasks I do a lot of. Then I just reuse the functions in all my projects where they are applicable. This method also forces you to learn about a consept and essentially writting down notes. Bonus is that this is one of the things you can show off in a portfolio. It also takes away all the repetitive code for simple stuff like accessing and proccessing files, logs. I have functions for timing effectivness and speed of new functions to make them as efficient as possible. Stuff like common blocks of code often used, say formatting text, logging errors and frameworks for different styles of loops. Functions for key- and mouse- and UI-control and the list goes on. Think about it... If not for copy and pasting usable functions, then just to import a simple library and most of the repetitive code is just gone with the wind.
@@bijanrajaie710 I primarily do Python as it's versatile and spans a wide area of use. It is however not as fast af a compiled program. For heavy and advanced stuff I use C#, and C for simple yet intensive workloads. I have fallen in love with the .json data format for saving settings so that is what most of my data handling and saving functions cover along with .csv and .tsv (of cource along with encryption of the files if I want the data hard to get to). My largest librarys are in Python and span over 10k lines for every single use case. Categorys like UI, userinput, data manipulation, file handling, heavy math, ect. That way i can simply copy a lib-file to my project, import it and have all my lovely work at the ready.
One of my teachers taught me the following mindset: "You don't have to memorize everything, but know where to find it and how to apply it." This mindset has been instrumental in aligning my way of working accordingly. I no longer waste time memorizing things, but always remember how I can derive the solution, be it through google, my own project snippet.to, or little post-it notes on my wall. It is a disgrace that interviewers often not asked about the concepts. Best you learn MDN by heart for them. My last employer was different there. The interviewer asked me about my approach and whether I could program this or that algorithm now at the first go. I said, "But only if I could use Google to check what that one mathematical formula looked like. Because in a real situation, that's what most developers would do." He was impressed. Don't waste your time memorizing everything, but remember how to get the knowledge you need at that moment. The advice of a lazy person. 😁
Wow! This is where I have been going wrong, so true it’s futile to try and remember all codes but rather should focus on the concept and understanding! Thank you so much dude great vid🔥🔥🔥
Man it's like you read my mind just got done with a javascript training session and I felt very defeated because I can't memorize half the shit i'm learning.
Yeah agreed. When I first got into Enter the Gungeon modding (that game doesn't have official mod support so a lot of mods are setup mostly with C# in VS and such) I focused on learning the syntax and rules for C# and the environment I was using it in. Looked at existing mod's code and found bits I needed a use for. Asked for help for the bits I didn't understand. After a few months I was able to pretty much do what I wanted on my own. Don't think I ever tried to really memorize specific functions. Just the skeleton/framework of those functions. Things like setting up for loops, proper use of if checks. (that's like the bare minimum really. I can't imagine you could do much if you don't understand those basics. :P ) Then work on the more fancy stuff like setting up new methods and calling them up from other functions/etc. Just playing around with how things impacted the game and looking at the game's internal code and layout of assets and such was enough to get me where I needed to go. But perhaps I have a more unique way of learning things like this. I haven't really gotten that good at much else coding related stuff. Just C# and a tiny bit of C/C++ back when I worked on Nintendo DSi/3DS homebrew stuff. I can't imagine one trying to memorize coding like one would try to memorize stuff in history class or something. Kinda approached it like learning a language. The grammar and how the words are ordered and used are more important to learn first then the words themselves. Ironically I'm really bad at learning human languages. Dropped out of Spanish class like 3 or 4 weeks into it. I just wasn't picking it up. :P Then again I never did well with structured learning environments like that in School. I didn't have am immediate use case for Spanish and I couldn't trial and error things with that like I could with a computer language like C#. Can't exactly look at an output window and check for the errors after hitting compile when attempting to speak Spanish or something so no easy way for me to really pick that up. :P
You are right, I found this tutorial by searching for "How to memorize code" . I am a beginner and right now I am trying to learn Jquery . I have learnt Html, CSS, Bootstrep. When I was styling with Bootstrep I noticed that I am forgetting CSS and now while I am trying to learn jquery I am afraid of forgetting JavaScript. It raised a question , "Why we learn CSS so precisely if we are styling with CSS and why should we learn JavaScript with so much effort if we are going to add some interectivity with JavaScript ? I have learnt CSS twice although it took few hours to get used with CSS when I learnt it for the second time . But I think we must know the basics , there is really no shortcut.
When I was learning I jumped between a few different languages somewhat regularly. The downside being I used to lookup the syntax for things a lot, but I had a very strong understanding of the concepts. Making it really easy for me to program in basically any object oriented language very quickly. I would also add that this applies to libraries and packages, don't try to memorize how they work. Use an IDE that exposes their documentation by holding ctrl and hovering the method.
Well when using any kind of library or package, you should know the basic concepts behind how they work. Like what kind of basic document model you're setting up. And that's generally more valuable than memorizing individual methods. Like when you're learning basic DOM based JS, you need to know about the concept of event handlers and adding/deleting elements form the DOM, even if you don't know the name of the functions to do everything, you just need to know the concept of how it's laid out and what you want to do.
Here you go: www.manning.com/books/the-programmers-brain?query=The%20progra The good thing with manning is with their MEAP program you can buy an ebook and read it whilst it is being written - you get updated when new chapters are available and can give feedback to the author.
@@fooledbyrandom991 Yea, I found this too during my search. I'm curious what part of this result you find helpful, since you apparently can't even buy the book yet.
No No I don’t make money from these I just happened to have read it and passed it on. To answer the question the author posits that memorising some key syntax is useful for 2 reasons: 1) It helps with code fluency - you are better able to read and interpret someone’s else’s code (or your own from a past project) if you can know what is being done without constant referencing. 2) Given its impossible to ‘multitask’ each break you take from coding to google a term etc can lead to you coming out of “flow” and it takes you a while to settle back in - assuming also you don’t get distracted by reading all around the syntax you need. I’m not sure I agree but it’s a fair point.
Yes--learning is a skill, not just a path to a skill! Expertise is more valuable than experience. I'm a professional instructor and a contractor, and I see this in every class I teach. Companies overvalue experience and undervalue expertise--and there IS a difference between experience and expertise. You get EXPERIENCE from DOING things. You get EPERTISE from UNDERSTANDING things. If you learn the concepts very well, you don't need to have worked with X, Y, or Z before. You can use any of them, and you can use them well. If you know how things work under the hood, it doesn't matter if you've never solved that problem before, and I've seen that proven over and over again. I've seen people go from Taco Bell to giving talks on stage at worldwide conferences in a year--for one of the most complex infrastructure management tools available. "What?? Isn't that supposed to take 5 years??" Learning is likely the most undervalued skill in most enterprises. We figured that out, and we built the best training money can buy. We've had 30 year veterans say "I've never understood it so well before." So yes, expertise is just as valuable as experience! :] Don't settle forever for with "I don't really understand, but, hey, as long as it works." You might be stunned to find out much more you can understand until you try--I was, at least. :] And don't forget... your learning journey never ends. If you can't change your mind, if you can't ask questions or admit you were wrong about something... you can't grow.
So I am supposed to look everything up and I will do that for the next who knows how many years, even when I get really good? Thats relieving and kinda disappointing at the same time lol
Not everything, just don't memorize everything, as you start looking things up your brsin starts to understand it and you don't have to memorize anything, except when you're in a code interview, fuck that shit memorize it all
What do you think you're missing - large-scale design and understanding of how to make complete apps, or small-scale design and understanding of how to put them together to do a specific small thing?
thank you teacher. for me, you are the greatest teacher and mentor. Remember.. even you do not know me as your invisible student, there is a person who highly respects you and thanks you a lot. you inspire me incredibly.
is there a specific method to doing this? beyond just using new stuff everyday lol. seems a bit stressful to INTENTIONALLY do memory garbage collection
dude u rly helped me. recently i was learning javascript and found it hard to memorize every thing....but ur right i just need the concept. thank u .u helped me wake up on my journey. big respect bro
@@wuhanvirus6974 Some are really good at education like sundar pichai, ratan Tata. But The Education System is still shit as hell. Almost Every Indian student hate the education system in India.
@@henil0604 right u r dude but all the names u mentioned were never part of this shit system sundar pichai went abroad for studies and ratan tata and all other entrepreneurs always believed in practical education and experience the thing that this shit system will never be going to explain
Basic setup for developing webapps: 1. Get example or existing code, use version control like git. 2. Setup runtime env so you can run and test it 3. Setup ide to edit the code (now the round trip of writing and testing is complete) 4. Setup debugger 5. Create unit tests that covers at least 90% of the business/control logic 6. Organize sprints, backlogs, user stories, sprint logs 7. Implement changes, write unit tests for all new code 8. Use code inspection of all the code to fix impacted code 8. Perform unit tests, manual technical and functional tests 9. Fix findings until all tests pass 10. Deploy to test server, run unit tests again 11. Deliver change to deploy team. Deploy to acceptance server, let client/product owner/end users perform their tests 12. Deploy team releases to production server unless there were findings 13. Goto 6 Concepts to learn Problem solving Problem analysis Fault finding, zero assumption Cost/time estimation Code paradigms/patterns like mvc, singleton, mvvm, repository, library, classes, inheritance, namespaces, etc Programming syntax Error message interpretation Security, write unhackable code, sql injection hardening, penetration testing Privacy protection, GDPR Code styles, document, comment, symbol naming like PascalCase, camelCase, indentation Regular expressions, search and replace Sql, preparee statements, transactions, indexes, foreign keys etc Logging, monitoring Business analytics, data flow, business logic, data models,decission trees Softskills, how to deal with non technical people, management, sales people. Write understandable documentation and instructions, strategy and vision, writing reports, working with people, in teams, clear communication Scaffolding, code templates, shortcodes, code completion Exception and error handling Rest/json/xml/yaml/crud/APIs Request stack/http protocol Api testing software like postman Load/stress testing software like K6 Profiling responsetimes, memory usage, program flow etc
Posts that have replies saying it's wrong and you're bad for being wrong while not saying what you can do to improve on it other than just 'getting good' at it
bro keep up the good work, i learned sql with that 60 min video and with no background got a job, i was workong in those toxic working social environments were you learn nothing, i was tired, keep up the good workbro, currently im learning python.
I agree. That's why I wish instructional books where more survey like. I already know about loops, arrays, conditional statements, etc. Just quickly go over what is unique about the language : it's syntax, semantics, data types, and special things it can do and can't do.
Hey man great thought, I have seen some of your concepts of teaching and I commend you for all the good concepts and work arounds. I hope I get to that level of understanding one day. Keep up the good work. Thank You
I've been programming for a lot of years. With only google, I believe I could code one of my projects in pretty much any language you choose. I'm not going to say I could win in any concept like functional or procedurual but I could make it work. Even in the languages I use a lot right now, I have to look up how a particular method works. I still have the code "worked out" in my head beforehand. Once you have learned how to code in one language, there are only a few languages that require further logic learning to progress. My tip is, once you come up with a cool way of doing something, save it to your "library of code". If its a project for a third party you might not be able to retrieve the code later. Build your library with as many snippets that you have written over the years and then update the source when you have a better idea. One of my web projects has shrunk from over 2mb of code to under 400k and does about 500% more things.
@David Benjamin I'm beginner too, I've been earning through investing with expert Adam it has been a huge success, in two weeks i made $15,000 with $1,000
I typically look it up the syntax in the API docs or let my IDE help me but with an upcoming technical interview for an internship, I'm a bit worried I will forget the correct syntax during the interview and not get the role. Things like modulo I forgot what the correct syntax was during a mock interview with my professor. I think memorizing some quick important syntax is good such as in JAVA you need to declare what item you are storing in a Stack or HashMap.
Great lesson I’ve started learning solidity as my first language I became confident in 3 months, now I’m trying to learn JavaScript but the way you end Certain functions is way different
