As a 40 year long programmer (his I feel old) I can only say: “so true”!!! Videos are great, I watch them and make them, to see a concept in action. But in order to comprehend that concept you need the foundation. And there’s no shortcut to learning the foundations. You’ll need to read books and apply those concept in “home work assignments” until you comprehend them. You don’t even need to memorize the syntax, I don’t anymore. I often google how to do “whatever” In “whatever” but I know what to do and why to do it.
I agree with you and the video. But I feel like programming is just not for everyone. I am 27. I first came across programming when I was a kid, seeing one of my family members typing some weird stuff, I had no idea what was that. When I was around 14-15 years old I first realised that it was some programming language. I dug into the topic and tried to learn PASCAL at first (idk why). I followed some youtube/website tutorials and learnt all the basics. Like IFs, loops, variables, arrays, and so on. But I couldn't bring these pieces together. I felt like I got stuck. Not long time after it, I tried to learn C++. I once again learned all the basics. I could do some very basic console programs. But then when I tried to make my own project, I just got so frustrated. Even though I googled for specific things, I just got depressed more. I didn't understand it. It was like a non ending rabbit hole for me. The more I tried to understand and search, the more confused I got in many cases. For example, I remember that I wanted to write JPG to ASCII converter, which would change image file into text file. In theory it's not hard, right? Just take every pixel RGB values, change them to grayscale, store these values in some 2D array, then print 2D array only using letters and store it in a notepad. Very easy, right? No. It turned out it just was so hard and it wasn't as easy as I thought. Just taking the pixel values wasn't as straight forward as I thought. I tried to search how to do it, but I just didn't understand this. Yeah I could copy it, but when, we end up in just copying someone else's code. There's no way I could figure it on my own. In the end, after some failures and frustrations i stopped programming. I probably did some very small projects over time. But nothing much. As a kid I dreamt of making online games, but if I couldn't do a simple JPG to ASCII, my motivation was lost. Last time with the programming was when I was around 19-21 years old. I had some programming lessons in my college. We started from zero, so yeah, once again I could understand the basics. But suddenly we had to make some complicated programs as our end semester work. And I once again felt so dumb. I remember getting some help on forums. Reading all these tips just made me more depressed as I couldn't understand much, and googling for these things again put me into rabbit hole, which didnt make my code work. I remember programming til 6 am, trying to make some simple things work. Did it finally work? Yes. Do I remember it with a smile? No. I remember feeling like a shit, crying cause of it. Don't get me wrong - I truly believe that by practice everyone can eventually learn. But in my case, there was A LOT of frustration. Usually I am a patient person, but in programming, it looks like I wasn't. When I had an idea I wanted to program it and see the results, and all the mistakes and problems along the way just made me feel like a shit. I often regret that I didn't learn regularly since I started at 15. But then I remember what issues I had and I try not to blame myself. For me the biggest issue was to jump from basics to making something actually cool. But often these cool things were just too hard for me. Sorry for a long post, but I just wanted to add this. TL;DR: I agree practice makes perfect. But practice needs patience and some motivation, which not all people have. And also passion. I feel like I wish I knew how to program, but I also don't want to go through the frustration of not being able to do something. Which is probably not possible when it comes to programming - there's always some kind of trial, error and frustration.
@@PinkeySuavo well I think your proved my point of not having the whole foundation of JPGs. I actually have a video of here I turn video into ascii art. The problem here is that you took a complex format like JPG that is highly compressed and you didn’t understand enough of it as to how to decompress it to its individual pixels or you didn’t know enough as to how screen buffers work to get to the screen data where you could’ve taken the pixels from a decoded jpeg image showing on the screen. If you knew about OpenCV or Qt frameworks that simply take any image format and turn them into basically a 2D array you’d be there, because the rest you understood to a T. Or even if you took BMP scan past the header and you have raw pixel data per colour. Also desaturation is something you’d need to understand because you need a luminance value not a colour but that’s rather trivial. A google search for a a framework would’ve yielded result for you because you knew the steps of the algorithm. And yes I know engineering is a special mindset that most people do not posses. Because they can’t chunk down a problem to its smallest part, or are impatient to gather the knowledge to do that. Or they simply don’t have that creative thinking as to find different solutions than the one they initially see. You need to be able to have more than a single solution that when you get stuck (and you will), you can change solutions. This is also why I always ask a recruiter looking for a programmer: “what is it that we develop?” I am only great in systems software (so interfacing with electronics or lowlevel bit shifting), backend database crap or graphics/video. Don’t let me do for example traffic flow simulations because I simply don’t know enough of those to turn it into a solution. If you want to control a telescope or medical imaging system or trade energy then I’m your man.
reading is much more effective in learning than tutorials i agree, i recently wrote a compiler and had tons of issues at first so i decided to read books on them. helped me out a lot
@@Omlet221 Hey, writing interpreters in Go is a good start. I'd recommend you to follow by writing your code in another language other than Go just sort of to challenge you and not merely copying what is written in the book. Bless you.
So logical thinking is the most important. It is like designing a house, you know beforehand what you want. Building the house is another topic, it comes with unexpected challenges but at least you have a goal. Coding is like building and programming is like designing. Both are challenging in their own ways.
I remember that "The Hand Holding honeymoon" then the "cliff of confusion" article from TOP for Web development. It explained Dunning Kruger Effect so good! I will never ever rely on spoonfed tutorials!
I agree with most of the points made in this video but one or two tutorials to get the basis of the language to know how to search for key functions is also important
I watch tutorial for webmasters, and at some point I get stuck with XAMPP. I didn't know why Apache doesn't work, and after an hour of changing ports, reinstalling XAMPP etc. I found out that it hadn't worked because I'd changed XAMPP's folder name. It was stupid mistake but I've felt great I fixed that issue, even if it was something obvious, and I felt that problems like this one and lessons from them are necessary to learn programming
kurwa idk what you talking about , I only watch Indian guys programing tutorials and I learn everything, just need to wait 2 weeks for next video to show me how to fix all errors we created in this weeks lesson ! 😁😁😁🤣😂😅😅🤣😂
Czesc widze po komentarzach ze jestes polakiem i mam pytanie czy moglbys mi pomoc z rozpoczeciem programowania. jezeli tak to skontaktujesz sie ze mna np. przez discord?
Dokładnie powiedziane. Ciągle mnie wkurza w tych tutorialach ,że nie potrafią wytłumaczyć dokładnie o co chodzi. Takie coś na zasadzie "i tu wciśnij i tu napisz tak to powinno wtedy być dobrze" Mało tego, zmiany we frameworkach są tak szybkie ,że tutorial sprzed 3-4 miesięcy nawet przepisując kod bezmyślnie kropka w kropkę co autor pisze, to już u Ciebie nie zadziała i wywali błędy. Obejrzałem już chyba wszystkie tutoriale z Blazora na całym YT śmiem twierdzić że mieć wiedzę to jedno ale umieć ja przekazać to drugie. Przestałem już je oglądać bo są prowadzone w sposób jakby ich prowadzący mieli jakieś tajne sekrety, mówią ogólnikowo i ciągle promują swoje kursy za kosmiczne pieniądze. Kupiłem kilka książek i w zasadzie już z pierwszych 2 pozycji+oficjalna dokumentacja internetowa dowiedziałem się więcej niż na całym YT ze wszystkich tutoriali. Pozdrawiam
As a 40 year long programmer (his I feel old) I can only say: “so true”!!! Videos are great, I watch them and make them, to see a concept in action. But in order to comprehend that concept you need the foundation. And there’s no shortcut to learning the foundations. You’ll need to read books and apply those concept in “home work assignments” until you comprehend them. You don’t even need to memorize the syntax, I don’t anymore. I often google how to do “whatever”
In “whatever” but I know what to do and why to do it.
I agree with you and the video. But I feel like programming is just not for everyone.
I am 27. I first came across programming when I was a kid, seeing one of my family members typing some weird stuff, I had no idea what was that.
When I was around 14-15 years old I first realised that it was some programming language. I dug into the topic and tried to learn PASCAL at first (idk why). I followed some youtube/website tutorials and learnt all the basics. Like IFs, loops, variables, arrays, and so on. But I couldn't bring these pieces together. I felt like I got stuck.
Not long time after it, I tried to learn C++. I once again learned all the basics. I could do some very basic console programs. But then when I tried to make my own project, I just got so frustrated. Even though I googled for specific things, I just got depressed more. I didn't understand it. It was like a non ending rabbit hole for me. The more I tried to understand and search, the more confused I got in many cases.
For example, I remember that I wanted to write JPG to ASCII converter, which would change image file into text file. In theory it's not hard, right? Just take every pixel RGB values, change them to grayscale, store these values in some 2D array, then print 2D array only using letters and store it in a notepad. Very easy, right? No. It turned out it just was so hard and it wasn't as easy as I thought. Just taking the pixel values wasn't as straight forward as I thought. I tried to search how to do it, but I just didn't understand this. Yeah I could copy it, but when, we end up in just copying someone else's code. There's no way I could figure it on my own.
In the end, after some failures and frustrations i stopped programming. I probably did some very small projects over time. But nothing much. As a kid I dreamt of making online games, but if I couldn't do a simple JPG to ASCII, my motivation was lost.
Last time with the programming was when I was around 19-21 years old. I had some programming lessons in my college. We started from zero, so yeah, once again I could understand the basics. But suddenly we had to make some complicated programs as our end semester work. And I once again felt so dumb. I remember getting some help on forums. Reading all these tips just made me more depressed as I couldn't understand much, and googling for these things again put me into rabbit hole, which didnt make my code work. I remember programming til 6 am, trying to make some simple things work. Did it finally work? Yes. Do I remember it with a smile? No. I remember feeling like a shit, crying cause of it.
Don't get me wrong - I truly believe that by practice everyone can eventually learn. But in my case, there was A LOT of frustration. Usually I am a patient person, but in programming, it looks like I wasn't. When I had an idea I wanted to program it and see the results, and all the mistakes and problems along the way just made me feel like a shit.
I often regret that I didn't learn regularly since I started at 15. But then I remember what issues I had and I try not to blame myself. For me the biggest issue was to jump from basics to making something actually cool. But often these cool things were just too hard for me.
Sorry for a long post, but I just wanted to add this.
TL;DR: I agree practice makes perfect. But practice needs patience and some motivation, which not all people have. And also passion. I feel like I wish I knew how to program, but I also don't want to go through the frustration of not being able to do something. Which is probably not possible when it comes to programming - there's always some kind of trial, error and frustration.
@@PinkeySuavo well I think your proved my point of not having the whole foundation of JPGs. I actually have a video of here I turn video into ascii art.
The problem here is that you took a complex format like JPG that is highly compressed and you didn’t understand enough of it as to how to decompress it to its individual pixels or you didn’t know enough as to how screen buffers work to get to the screen data where you could’ve taken the pixels from a decoded jpeg image showing on the screen.
If you knew about OpenCV or Qt frameworks that simply take any image format and turn them into basically a 2D array you’d be there, because the rest you understood to a T.
Or even if you took BMP scan past the header and you have raw pixel data per colour.
Also desaturation is something you’d need to understand because you need a luminance value not a colour but that’s rather trivial.
A google search for a a framework would’ve yielded result for you because you knew the steps of the algorithm.
And yes I know engineering is a special mindset that most people do not posses. Because they can’t chunk down a problem to its smallest part, or are impatient to gather the knowledge to do that. Or they simply don’t have that creative thinking as to find different solutions than the one they initially see. You need to be able to have more than a single solution that when you get stuck (and you will), you can change solutions.
This is also why I always ask a recruiter looking for a programmer: “what is it that we develop?” I am only great in systems software (so interfacing with electronics or lowlevel bit shifting), backend database crap or graphics/video. Don’t let me do for example traffic flow simulations because I simply don’t know enough of those to turn it into a solution. If you want to control a telescope or medical imaging system or trade energy then I’m your man.
reading is much more effective in learning than tutorials i agree,
i recently wrote a compiler and had tons of issues at first so i decided to read books on them. helped me out a lot
I am interested in learning about compilers, what books were the most helpful for you?
@@Omlet221 Hey, writing interpreters in Go is a good start. I'd recommend you to follow by writing your code in another language other than Go just sort of to challenge you and not merely copying what is written in the book.
Bless you.
@@Omlet221
Look the "Mathspp Blog" it has a building Python Compiler series under blog/tag:bpci
So logical thinking is the most important. It is like designing a house, you know beforehand what you want. Building the house is another topic, it comes with unexpected challenges but at least you have a goal. Coding is like building and programming is like designing. Both are challenging in their own ways.
I remember that "The Hand Holding honeymoon" then the "cliff of confusion" article from TOP for Web development. It explained Dunning Kruger Effect so good! I will never ever rely on spoonfed tutorials!
so true! i have only watched two python tutorials when i was 10, and ever since then i just read the documentation and try to work it out myself.
I agree with most of the points made in this video but one or two tutorials to get the basis of the language to know how to search for key functions is also important
I said this in video, tutorials can teach us most basic things, but if we want to learn more we must learn by ourselves
I feel ashamed that I never considered looking the documentation instead of looking up Stack Overflow.
Never it's too late for trying new solutions!
I watch tutorial for webmasters, and at some point I get stuck with XAMPP. I didn't know why Apache doesn't work, and after an hour of changing ports, reinstalling XAMPP etc. I found out that it hadn't worked because I'd changed XAMPP's folder name. It was stupid mistake but I've felt great I fixed that issue, even if it was something obvious, and I felt that problems like this one and lessons from them are necessary to learn programming
life is the best teacher
Damn bro, i spent the whole day figuring our why my xampp for smtp mail couldn’t work?guess what it was my antivirus that was blocking the service
cant agree more!
i can't read documentation. I watch it instead as video form.
Lesson learned, tutorial makers need to stop just showing the answer and start showing how they arrived at the answer.
Good video man
Thanks!
kurwa idk what you talking about , I only watch Indian guys programing tutorials and I learn everything, just need to wait 2 weeks for next video to show me how to fix all errors we created in this weeks lesson ! 😁😁😁🤣😂😅😅🤣😂
Czesc widze po komentarzach ze jestes polakiem i mam pytanie czy moglbys mi pomoc z rozpoczeciem programowania. jezeli tak to skontaktujesz sie ze mna np. przez discord?
napisz na instagram @practical_codin
POLSKA GUROM
Dobrze wiedzieć
polska gurom 🗣🔥🔥
polska!!!
Dokładnie powiedziane. Ciągle mnie wkurza w tych tutorialach ,że nie potrafią wytłumaczyć dokładnie o co chodzi. Takie coś na zasadzie "i tu wciśnij i tu napisz tak to powinno wtedy być dobrze" Mało tego, zmiany we frameworkach są tak szybkie ,że tutorial sprzed 3-4 miesięcy nawet przepisując kod bezmyślnie kropka w kropkę co autor pisze, to już u Ciebie nie zadziała i wywali błędy. Obejrzałem już chyba wszystkie tutoriale z Blazora na całym YT śmiem twierdzić że mieć wiedzę to jedno ale umieć ja przekazać to drugie. Przestałem już je oglądać bo są prowadzone w sposób jakby ich prowadzący mieli jakieś tajne sekrety, mówią ogólnikowo i ciągle promują swoje kursy za kosmiczne pieniądze. Kupiłem kilka książek i w zasadzie już z pierwszych 2 pozycji+oficjalna dokumentacja internetowa dowiedziałem się więcej niż na całym YT ze wszystkich tutoriali. Pozdrawiam
Is this an AI voice or your actual voice?
Unfortunately this is ai voice from veed io, I don't speak english so well
I'm grateful you are confident to say that. If you really want to improve your English, my humble advice is do not rely heavily on Voice AI. 🎉
rrfm