Perhaps when doing it the hard way was part of our training that does not mean we were locked into that hard way but that what we know makes a very solid foundation for all we have done since.
That is the concept I was trying to say, foundation. Thanks!
Yes I was pulling your leg.
Although I know really solid programmers with no assembly code exposure and doing great stuff.. so YMMV
I am sure that is true, but I was probaby better known as a bug finder and system performance guru. I once held the record for fastest transaction processor. Where my foundation in hardware, machine code, assembler served me was when we transferred some programs from Toronto to New Jersey using tape drives at each end and some sort of telecoms in between. The program running in New Jersey was producing different results than the one in Toronto (stock market ticker system for Dow Jones) When I looked at the differences I noticed NC (no change) trades were unaffected but up tick and down tick were inverted. I figured that one instruction being different might explain it so I did a very slow comparison of the two tapes (over telecom that was at best 9600 baud) and found a one bit difference. Long story short I was able to pin point the difference to a single branch instruction as I could read tape blocks and machine language etc. Once I was sure, the boss wanted proof so we walked through a few of the 'funny' trades with the bit on and with it off which was BH and BL (Branch if High and Branch if Low). We very quickly were able to patch the program but nobody I have ever told the story to could tell me how a 1 bit error got through all the checks, it should have been impossible.
If I did not have the background of assembler/machine code and even hardware I may not have known that the BH and BL op-code differed by a single bit. At the very least I am positive it would have taken me a lot longer.
I know that in 1980 and on I had better tools to do my work than those who coded before, including myself. Editors, compilers, access, hardware all got better and better. It was easier to out-do the past. Change meant for me to not get stuck in details yet, some things never really changed.
AVR-duinos have been a blast from the past on steroids and speed with a mix of old and new. It makes getting old and lacking the energy of being new suck even more!
It doesn't seem that long ago that getting two compiles in a day was a 100% increase in productivity. I don't know how, but we even survived the van taking all the card decks from head office to the computer centre, getting in an accident, spilling the cards all over Don Mills and Eglinton in the middle of winter. I also remember chastizing an intern shortly after getting terminals for doing 100 compiles in a few hours or less. Resources were scarce then and up times short. Now I seem to have infinite cycles, RAM, disk space. Who remembers 5.25: HDD 5 MEGABYTES for $5,000.
But what has not changed is the humans in the system. No further comment on that less I get banned.
That's why they use chatGPT now 
One test of being a working programmer is how many times you can take being wrong before lunch. The compiler is a harsh mistress.
It's like Red Green said about being a handyman. If you don't make mistakes, you're not really trying!
i'm just busy in this last week of our academic year, we have another defense on our business in our economics and also im not feeling well rn
base on my learning capabilities, i prefer watching/listening a lesson video rather than self-learning, what do i mean by self-learning is teaching yourself independently. listening to a video makes me to better understand the code just like the series
you'll need to watch and listen to a lot of videos or attend a lot of classes. This will limit your understanding
I'd spend more time to understand better, because it fully explains the program. unlike reading, it doesn't explain the program i mean it does but not the way that i understand it that's why my previous forum reached 300+ i believe
college teaches you how to learn (on your own)
TopTechBoy is a video series found here
As long as you have the components to follow along the video lesson, it doesn't matter where you bought them
Until you spend time planning and writing and seeing what it does, you won't learn at the do level. Until you explore beyond what you were shown, all you'll do is copy.
I went to a public school where that is what they taught starting in middle school, at least to the exceptional track.
There was a motto: learn to listen, listen to learn.