Wow. I forgot this was online! (I"m the guy who did that talk) Thanks for the kind words, everyone. I love to do this talk, so let me know if you run a user group or something and want me to zoom in or something.
Sir, I am learning C#, and I was starting to feel like I was making great progress, then I decided it was time to take the hackerranker(dot) Com test for entry-level programmers and got slapped in the face. So I was feeling discouraged, and downright depressed about my ability to do this. This talk has reinvigorated my drive, and I feel so much better about it. Do you have any tips for getting your first job as a programmer? I am a comp sci student in my 30's (changing careers from IT Support), and am desperate to get out of the IT Break Fix industry, any advice would be monumentally appreciated.
I'm so glad this was helpful. My general advice is this: Don't compare what you can do today to what others can do after years of study and practice. Compare what you can do today to what you could do yesterday. As for the job thing, that's a bit tricky, because hiring managers often don't really understand code and they're just looking for a bunch of keywords to filter against. At some level you'll need to know some languages and frameworks, but the strongest thing you can do is pick any language (Python is a great choice) and learn how to solve problems with it. Start building a portfolio of projects you're working on. Don't worry about the language or framework yet. Just prove you can build cool stuff, and you can keep working on a project even when things get hard. Ultimately, that's the most important job skill in most industries, but especially in programming. Keep up the great work! -Andy
I have some course on Udemy (web and game programming mostly) My university tapes my courses at de.cs.iupui.edu (they're a little old, but have some good content.) -Andy
I am a beginner in programming, I'm learning Python as a 1st language but as I was learning I realized I just don’t want to be learning the syntax and copying code. What I wanted was the correct approach to programming, how to break-down a problem and then go about writing code. And your video gave me just that. If possible please market this video a bit, obviously you don’t care about views, but this is going to help so many people who are getting started with programming but are going about it the wrong way.
Hey, I'm now where you were 3yrs ago. Would you be interested in answering a few questions? Are you content with Python as your fist language? Would you pick any other as first? Did you learn any other language in the meantime? Did you find a job where you use Python? What would you change in your approach, now that you are 3yrs in if you were to start from the beginning ? What are some common mistakes you made that would help others?
This was excellent! 20+ years in the business, could not agree more. A friend of mine recently asked me, how to get into coding as an adult. Sent her the link to this video right away.
Legit smile across my face when he said: "If you don't like failure then you're in the wrong business." After much time spent searching for the "right" entry point as a beginner, I have never felt more confident that this is THE correct approach. Love this lecture.
I'm a new programmer as well single parent working 2 jobs and learning. I have noticed courses don't teach you how to break things down they just show you what to do.. it's been about 6 months and the hardest part for me is understanding the breakdowns. I didn't go to college I have a technical degree. But looking at the whole is something that is a frustrating habit. Thank you for the talk!
So many legendary snippets in this: "First of all, you hated math class, I'm not sure you've met math" There are heaps too many to log here, happy learning! Thank you @AndyHarrisProgramming ! & @sixfeetupcorp
They're in there, either in-depth or alluded to, just not listed in strict numerical form. I can't speak for Andy, but for me: 1. Variables (and their data types [integers, strings, arrays, floating-point numbers, objects], and how they're defined [constants, or variable] whether this deserves its own number is up to you!) 2. Input 3. Output 4. Algorithms 5. Control flow (has 3 types, sequential [code is usually read sequentially, top to bottom], conditional [if, if else, ternary, switches, etc.], iterative [loops]) 6. Functions (what does my algorithm do, is it repetitive, is it event-driven? etc.) 7. Source code (the language you choose and the actual code you decide to write - usually immaterial!) 8. Compilers (turn your source code into machine code) And depending on what you're doing with your programs I suppose the 9th can vary depending on your chosen paradigm (object oriented programming, mathematical etc.) so you could look at arithmetic, objects and classes, that sort of thing.
@@dylcode9375 Awesome, thank you for taking the time, it means a lot! I appreciate it. I will look to better familiarize myself with the concepts you pointed out like control flow.
But he explains things while there they try hard to not explain anything 😃 They also do not mention older implementations as Gothic Arianism branch ;-)
Andy Harris you mentioned about one expert programmer can not understand the real problem,this is why some programmers don't have the way of true and natural thinking!
This is great, I’ve been doing exactly what he said beginners do, I would look at a problem and quit right away because I would think there’s no way I would remember all the JavaScript syntax to even start. I’m even thinking to perhaps maybe stop JavaScript and try Python?? Any ideas ????
Just pick a language and learn just that language. Don't keep flip flopping. Also, don't try and learn two languages at once, your first time. Understand the basic concepts that the speaker discusses in one language, and then every language after that will be trivial.
The more you do it the more you understand it. Ground up. Some things will work despite you getting only 50% of it. Coming back after some time reading the same concepts you start seeing more abstraction & patterns. Brain needs to put pieces together and it makes it slower at start and then you get surprised why so simple thing appeared so complex. Because brain has limited capacity & overloads easily. Like with driving a car first time. In time two small parts become one bigger and picture becomes clearer. After a good night sleep, fresh, undistracted, in optimal state focus gets better and taking it in your personal pace you see how brain is fed & processing like a computing stack, taking part after part with a natural flow until untrained focus runs out haha but the feeling is great as if every part was easy until something too hard comes then stack overflows & the abyssal black fog arrives and you know nothing again. And it makes me afraid of using any boosters for learning except coffee, it may boost the good feel and then boost the mental crash stronger... Check out the Odin project you get a complete path of learning step by step lesson after lesson and for free! The world is so great!
Sir,I am sorry but it is little big difficult to understand that you said programming is not math,programming is not algorithm,programming is not writing code so what is programming?
I think programming IS about algorithms and data structures. I think it is about learning to solve problems by slowing down your thinking and breaking large problems into smaller problems that are eventually so granular that you can convert your thoughts to code that the idiot computer can understand.
Like dismounting a car engine into all basic parts, examining each one, fixing or replacing with a new one of the same functionality. Debugging being analysing parts sensors messages (debugging console code breakpoints) to the car analytics screen. But it means having a knowledge about parts, their functions & wrong broken state sounds. BTW debuggers producing a different sound for each type of bug could come handy ;-) or even visualising code/stack_operations chain execution as a chain of ideograms. It would be super handy when trying to understand somebody else's code. Your idea of comments into code is close to telling machine data & it's type, type of algorithm, expected output & pushing "Go find a code doing it" button. I mean machine could teach us more itself if we find a way to ask right questions. I have a flashback of the second book of Ender's Gate series now.
Wow. I forgot this was online! (I"m the guy who did that talk) Thanks for the kind words, everyone. I love to do this talk, so let me know if you run a user group or something and want me to zoom in or something.
Do you have a tutorial or a course where we can learn programming? Love your style ;)
Sir, I am learning C#, and I was starting to feel like I was making great progress, then I decided it was time to take the hackerranker(dot) Com test for entry-level programmers and got slapped in the face. So I was feeling discouraged, and downright depressed about my ability to do this. This talk has reinvigorated my drive, and I feel so much better about it.
Do you have any tips for getting your first job as a programmer? I am a comp sci student in my 30's (changing careers from IT Support), and am desperate to get out of the IT Break Fix industry, any advice would be monumentally appreciated.
I'm so glad this was helpful. My general advice is this: Don't compare what you can do today to what others can do after years of study and practice. Compare what you can do today to what you could do yesterday.
As for the job thing, that's a bit tricky, because hiring managers often don't really understand code and they're just looking for a bunch of keywords to filter against. At some level you'll need to know some languages and frameworks, but the strongest thing you can do is pick any language (Python is a great choice) and learn how to solve problems with it. Start building a portfolio of projects you're working on. Don't worry about the language or framework yet. Just prove you can build cool stuff, and you can keep working on a project even when things get hard. Ultimately, that's the most important job skill in most industries, but especially in programming.
Keep up the great work!
-Andy
I have some course on Udemy (web and game programming mostly) My university tapes my courses at de.cs.iupui.edu (they're a little old, but have some good content.)
-Andy
Love this!
I am a beginner in programming, I'm learning Python as a 1st language but as I was learning I realized I just don’t want to be learning the syntax and copying code. What I wanted was the correct approach to programming, how to break-down a problem and then go about writing code. And your video gave me just that.
If possible please market this video a bit, obviously you don’t care about views, but this is going to help so many people who are getting started with programming but are going about it the wrong way.
Hey, I'm now where you were 3yrs ago. Would you be interested in answering a few questions? Are you content with Python as your fist language? Would you pick any other as first?
Did you learn any other language in the meantime? Did you find a job where you use Python? What would you change in your approach, now that you are 3yrs in if you were to start from the beginning ?
What are some common mistakes you made that would help others?
This was excellent! 20+ years in the business, could not agree more. A friend of mine recently asked me, how to get into coding as an adult. Sent her the link to this video right away.
Legit smile across my face when he said: "If you don't like failure then you're in the wrong business."
After much time spent searching for the "right" entry point as a beginner, I have never felt more confident that this is THE correct approach. Love this lecture.
I actually watched it till the end. That's not common for me for such a long Video on TH-cam. Very good
I swear, that one line: "Code is there to teach the computer how to understand the comments."
Git comments seems highly underrated too. There is more to this craft than I ever imagined.
I'm a new programmer as well single parent working 2 jobs and learning. I have noticed courses don't teach you how to break things down they just show you what to do.. it's been about 6 months and the hardest part for me is understanding the breakdowns. I didn't go to college I have a technical degree. But looking at the whole is something that is a frustrating habit. Thank you for the talk!
This talk is so great! What a nice guy! I recommend closing your eyes and imagining Will Ferrell delivering the talk (RIP).
RIP? lol Will Ferrell isn't dead though
by far the most helpful video I have watched yet
This is the most fun lecture I have ever heard :D
Thank god I've found this video! Thanks, Andy Harris.
His Words are Catalyst for me as a 'begineer'.
And how it went until now? :-)
This autoplayed on my TV, and I thought I was listening to Tony Robbins delivering a talk on dabbling in programming.
Problems are super difficult when you have a bad cold, I totally agree with coding second, get so confusing when theirs no real order. Thanks
So many legendary snippets in this:
"First of all, you hated math class, I'm not sure you've met math"
There are heaps too many to log here, happy learning!
Thank you @AndyHarrisProgramming ! & @sixfeetupcorp
Watched this from start to finish, outstanding; from an older career changer just starting to learn.
How are you getting on? Did you end up making the switch?
I keep coming back ack to this lecture, it has a lot gems. Can you list out the 8-9 main concepts?
They're in there, either in-depth or alluded to, just not listed in strict numerical form. I can't speak for Andy, but for me:
1. Variables (and their data types [integers, strings, arrays, floating-point numbers, objects], and how they're defined [constants, or variable] whether this deserves its own number is up to you!)
2. Input
3. Output
4. Algorithms
5. Control flow (has 3 types, sequential [code is usually read sequentially, top to bottom], conditional [if, if else, ternary, switches, etc.], iterative [loops])
6. Functions (what does my algorithm do, is it repetitive, is it event-driven? etc.)
7. Source code (the language you choose and the actual code you decide to write - usually immaterial!)
8. Compilers (turn your source code into machine code)
And depending on what you're doing with your programs I suppose the 9th can vary depending on your chosen paradigm (object oriented programming, mathematical etc.) so you could look at arithmetic, objects and classes, that sort of thing.
@@dylcode9375 Awesome, thank you for taking the time, it means a lot! I appreciate it. I will look to better familiarize myself with the concepts you pointed out like control flow.
I made a follow-up video to answer this question. (and shortened the list to 7 main ideas) th-cam.com/video/y6dS-xX_Nt4/w-d-xo.html
BEST TALK FOR BEGINNERS. PERIOD! 👏🤓
I haven't listened to a lecture like this since last time I went to church.
But he explains things while there they try hard to not explain anything 😃 They also do not mention older implementations as Gothic Arianism branch ;-)
This was by far one of the most entertaining and informative lectures I've ever had the pleasure of listening to!
Andy Harris you mentioned about one expert programmer can not understand the real problem,this is why some programmers don't have the way of true and natural thinking!
What is the true and natural thinking?
What a genius!
Thank you very much indeed,that is a good conversation.
Love this guy!!
Really great video your awsome at teaching
Thank you, it was awesome!
Very lovely tutor!!!
Thanks
Slide used for this presentation can be found here:
slides.com/twopi/deck#/1
Could you link to the html table you mention around 22:10, please?
I have the feeling this guy was the one with the beer in that classroom
Great video!
I did a computer science degree and not one of my programming classes was like this. I feel cheated. lol
Life is about random luck and digging fast enough & wide enough to gather more of it than others and then share with those you like ;+)
This is great, I’ve been doing exactly what he said beginners do, I would look at a problem and quit right away because I would think there’s no way I would remember all the JavaScript syntax to even start. I’m even thinking to perhaps maybe stop JavaScript and try Python?? Any ideas ????
Just pick a language and learn just that language. Don't keep flip flopping. Also, don't try and learn two languages at once, your first time. Understand the basic concepts that the speaker discusses in one language, and then every language after that will be trivial.
The more you do it the more you understand it. Ground up. Some things will work despite you getting only 50% of it. Coming back after some time reading the same concepts you start seeing more abstraction & patterns. Brain needs to put pieces together and it makes it slower at start and then you get surprised why so simple thing appeared so complex. Because brain has limited capacity & overloads easily. Like with driving a car first time. In time two small parts become one bigger and picture becomes clearer. After a good night sleep, fresh, undistracted, in optimal state focus gets better and taking it in your personal pace you see how brain is fed & processing like a computing stack, taking part after part with a natural flow until untrained focus runs out haha but the feeling is great as if every part was easy until something too hard comes then stack overflows & the abyssal black fog arrives and you know nothing again. And it makes me afraid of using any boosters for learning except coffee, it may boost the good feel and then boost the mental crash stronger... Check out the Odin project you get a complete path of learning step by step lesson after lesson and for free! The world is so great!
Thankyouu!!!
This is great because he sounds just like Will Ferrell
Sir,I am sorry but it is little big difficult to understand that you said programming is not math,programming is not algorithm,programming is not writing code so what is programming?
I think programming IS about algorithms and data structures. I think it is about learning to solve problems by slowing down your thinking and breaking large problems into smaller problems that are eventually so granular that you can convert your thoughts to code that the idiot computer can understand.
@@AndyHarrisProgramming BravO!
@53:22 there is cut... what/how much left out from ur conclusion.
Like dismounting a car engine into all basic parts, examining each one, fixing or replacing with a new one of the same functionality. Debugging being analysing parts sensors messages (debugging console code breakpoints) to the car analytics screen. But it means having a knowledge about parts, their functions & wrong broken state sounds. BTW debuggers producing a different sound for each type of bug could come handy ;-) or even visualising code/stack_operations chain execution as a chain of ideograms. It would be super handy when trying to understand somebody else's code. Your idea of comments into code is close to telling machine data & it's type, type of algorithm, expected output & pushing "Go find a code doing it" button. I mean machine could teach us more itself if we find a way to ask right questions. I have a flashback of the second book of Ender's Gate series now.
Great
This is why I haven't found a reason to learn programming.
I haven't found something worth writing an algorithm to solve yet.
Make algorithm creating problems to solve.
Coming here after I learn to code to find out that I don't know how to code lol
9:29
C🎉
I hate programming
His Words are Catalyst for me as a 'begineer'.