As a side note, this is why I recommend also reading books. It's a great way to learn slow where you get more of the background than maybe you thought you wanted, but helps build better intuition than many realize, and a lot faster than trying to only discover it as you go. Someone has put in 5-40 years of knowledge into helping you not have to discover fire again.
It depends a lot on your current level and what your requirenents are. I quite like ”Hands-On Machine Learning with Scikit-Learn, Keras, and Tensorflow”. It has a mix of some data wrangling with dataframes, visualization and some analysis with a practical emphasis. Its at a relatively beginner friendly/internediate level. Its quite useful even if your goal is not doing ML. ”Matplotlib for Python Developers” is quite good for visualization. For more software, and less analysis focus, to develop your Python skills you may like: ”Python Design Patterns: A Step-by-Step Guide”.
I don't think reading books makes a difference. Information is Information. Using your critical thinking, testing and experimenting with what you've learned builds the intuition.
reminds me of an old memory.. when I was a kid learning to skateboard I really reaaaaally wanted to grow up to be a pro. beyond obsessed. an older skater told me once while I was learning "don't learn this trick to become pro.. learn this trick because it's fun.. pros are addicted to the fun of learning tricks.. that's all you need." oddly some of the best advice I've had. don't suck the fun out of what you do. being pro won't even be worth it lol.
Was a civil engineer in SF. I taught myself some basic and advanced DSA using Leetcode. Became really good at solving those problems and started interviewing. Got a job and learned building stuff on the job!
@nicholaskipchumba9189 I'm attempting the same transition right now. Was Leetcode all you used to start learning before you landed your first job? If there were other resources you used (or any general advice you could give), could you please share it with us?
I'm glad someone else has said what I've been thinking and doing throughout my entire journey in becoming a well rounded developer. I build things that I want to use. That really helped me get the foundation as from there, because of that process, I've naturally grown interests in other technical areas which acts as a positive feedback loop to further expand my skills.
Interestingly, I think this is the main value a formal software education provides. I went to college for four years to study computer science. In my case, I did it because I "was supposed to" (I had a very rigid upbringing and very fortunate financial circumstances), but looking back on it, it provided the environment needed to build skills _slowly_. That environment included explicit teaching of basic concepts, projects in which to apply those concepts, and scrutiny of those projects to correct mistakes. One critical aspect of this is that, while it required discipline to stay on track and make the grade, some amount of the "discipline" requirement was removed thanks to the curriculum and benchmarks being set externally. If you can get those things without a formal education, it can be much cheaper! But you will have to build your own curriculum and set your own benchmarks, which requires a mountain of discipline that a formal education would give you automatically. I don't know that I necessarily have a point here, only an observation that formed while I was watching this vid.
it depends dude, just coz ur experience with a formal background was a good one does not mean other share that same sentiment. its extremely variable & in my case, ive learnt more about programming thru my own self experimentation & grind, so much so the kids in my class call me a "genius" when i come up with a solution to a problem that even the lecturer did not think about. in reality i just grinded my ass off for years alone & it paid off.
I full agree. I was self-taught in high school through gamedev projects + motivation, but formal education was still very helpful. It exposed me to other programming paradigms (functional, declarative), and languages in general (gamedev was 100% C++). It exposed me to other programming problem spaces: XSLT, database, networking, and systems programming. While 85% of my core capability on the job for 14 years was self taught, that remaining 15% slowly picked up in college was very broad and is highly valuable because it's what allows me to pick up any programming industry job and know that I've probably already seen the core difficult problems. Only the surface level problems will be new, as they would to almost anybody who isn't directly knowledgable. When you're limited to looking at someone's value in one team, it can be hard to distinguish who learned slowly, and who learned and applied things "quickly." Those who applied knowledge quickly will quickly be unable to solve more difficult problems because they fail to learned and are barely able to identify the difficult problem at hand. Those who learned a lot of things slowly will comfortably move to different surface level frameworks, languages, or libraries as needed whereas those who don't really have the underlying knowledge will be far less comfortable with this.
For me, the community factor was extremely important. I wouldn't be able to study half as much had I not been in contact with other high performance students, and of course inspiring professors, every single day.
I agree with the statement "Tutorials aren't for learning"; you are literally copying with the extra perspective from the tutorial maker. An actual learning experience would be to modify the tutorial as you are following it, add extra features you would want; or after you complete the tutorial, use it as "boilerplate" for a personal project.
This. Following tutorials without modifying and building just leaves one feeling lost when they actually try to build something. And painter can only get better at painting by painting a lot. The same can be said about programming.
I use chatGPT and Phind. But there is a specific prompt you need to give it so as to not compromise your learning. You need to specifically tell it not to give you a snippet, full answer, or an example of it's use. Just give you the element or attribute that is related to what you want. For example; Bad prompt: How can I color this box red? This will have it give you the full prompt you need to copy and paste in there. But what do you learn? Nada. Good prompt: What attribute can be used to color a box red in HTML? Do not provide a snippet or example. It'll spit out a list of possible solutions to this problem, and you need to figure out which one is suitable, and how to use it.
Honsetly this at 10:20 has become clear to me after I built a chat client at work then watch prime build it on his other channel and it was so fun because i got to see how someone way more experienced build it and I think I learned more just by watching
That reminded me about reading physics books. Specifically for the rigorous books about theoretical physics, people always said that those books are not for learning the material as a noob. But when you already understand the material, you can read it and really appreciate how well written the book was lmao
Thank you for this video, I'm currently a student at 42, and I'm seeing too many people getting their way thtough with git copy. I'm glad that I'm taking the slow path to learn how to code, how to build something !
0. Find what problems you're passionate about solving 1. Learn the fundamentals 2. Solve problems while learning interesting things about the languages you're using to solve the problem 3. Find a way to show off your work in an appealing portfolio for the work you want to do 4. Network relentlessly 5. Repeat 1-4 until profit!
This is more or less exactly what I did. I spent 10 years on steps 0-2 because it never crossed my mind I could work as a developer. Then 5 years ago I started going to meetup events to get to know other programmers with the same interests. I showed off what I made to someone and they invited me to come work for them. It occurred to me later that those events were actually for networking.
My honest advice is: if you like software development / engineering, then come to this industry. After all, passion and professionalism are all the things which do actually matter.
Be smart is true, it is like you have said in the past, get hands-on. If one wanted to become an Olympic Gymnast, they would get on the beam and fall down and get back up and keep falling down. The only way forward is practice and working through docs however it is actually DOING by coding, using print debugging or actual debugging to understand primitives compared to more complex objects, etc...
I used to be a developer at some R&D department in the national postal service in Norway. When people asked me what I do, I would always get questions about lost packages and things way outside my scope. And especially at parties people would start pitching ideas or rant/banter about some bad experience they had with the service.
As a frontend/backend developer.. I’ve learned to disassemble other people’s code and have a good instinct to know when someone else’s answer to a problem is garbage and only makes things worse. I’ll do tutorials only to see or understand a part of it.. then I go build something different, if similar, try to build it in a unique way, change the ui, do it in another language .. or try to build a MVC in js, without a framework.
I am beginning developer. At a certain point I just wanted to improve so I started building the apps I wanted to build even if I had no idea what I was doing. I feel so much better when I find a solution rather than watching a whole completed tutorial.
It's a great advice in general, but for some people programming is a way to finally have some money to be able live their life. So for people struggling without money it's actually great to take shortcuts to land a job. And after this point this advice about learning programming deeply is really great, because that's how you advance your career and can provide for your family way better
I use chatgpt, but only to ask about the methods and quirks of the language itself. I still bang my head against the logic wall myself all the way through. And frankly, that's how I LOVE doing the learning. I have to say AI has been a blessing for someone like me, who has no attention span for tutorials and courses, and learns hands on.
its not about attention span or tutorials and courses, its about how much time chat GPT saves you. I could google my way through a problem, and yeah ill find it eventually... after checking 5-10 links that lead me down rabbit holes that dont do anything. OR i could go to GPT, describe my problem, and it will find a solution in a minute, and if its wrong, ask for another one. I think this is where people go wrong though, like in the video, dont take the steps at word value, you have an infinite source of knowledge that gave you these steps, if in any of them you have a question about what it used or something youve never seen before, literally just ask gpt and it will tell you. now not only are you going through rabbit holes, but now you are going through them with it actually being relevant to your problem, and now you've learned so much about stuff you didn't before. Another thing, NEVER copy paste anything gpt gives you, type it out. learn by doing, not seeing.
Ive learned this the past year or two with my programming career while studying for my CS degree. I thought I knew how to program because Ive used some javascript and python. Wasnt until I actually starting building projects for fun that I realized I learn when trying to solve problems I actually want to solve, not following tutorials.
just tried this website and its so much better then tutorials, it literally teaches you the concept and then gives you some code with errors and its on you to fix said errors. This is awesome.
I am new to development. Took a js bootcamp. In the middle of it life threw me a curveball and I got canned from a stupid sales job because the manager had it out for me… idk how I completed the bootcamp but I did and after that I was forced to take the a+ by my field it job… then they canned me lol.. seems tragic but every hurdle life throws at me I have kept faith in god, I have a work from home job now(not dev) but I am finally able to spend more time developing my apps… it’s amazing to learn new things and branch out. A+ may seem stupid but you can understand so much more about software when you keep it interesting and never let life get the best of you. No matter how many times you get canned 😂
I totally agree. Don't just fix the bug, fix the root-cause. Just to add to that, yes, sometimes you need to take shortcut and just fix the bug. But in that case I would say add tech-debt story to fix it later 🙂
Got my first “real” job because I did a project in django. Whatever people people say it’s not set in stone. Go around breaking and fixing stuff. You’ll find your way.
Documentation for learning. Lectures / courses for additional information. Talks / presentations for interesting information. Tutorials for telling people "I'm learning ".
Tutorial hell is the bane of my existence, but just having a goal/project that you want to do and going at it is also a terrible experience. You end up taking a chaotic path towards the goal, quite possibly learning very bad habits or patters in the way. Spoon fed instructions are not very useful, but you need some sort of mentoring to not only learn properly, but learn efficiently.
im from germany and its a little bit hard to follow but mannn - i love your tech talk. You have something from the "Great Teacher Onizuka" style in Software Engineering
Shortcuts lead to long delays - outstanding, premium thought. It hits the target.Brilliant! In technology shortcut sometime is a cause of short circuit. Jumping over the doc details can lead to serious issues in emergency situation. I enjoy Tolkien's books very much. Cheers!
all my friends who are doing internships tell me to watch tutorials to learn the swift language, i on the other hand only use books and chatgpt , becuase you can learn alot from those two than watching any tutorials, also i told my friends the exact same thing about tutorials leaving mostly 70 - 80 percent of the knowledge you can gain from books and chatgpt, also another thing i would like to add is that watching tutorials for a long time, you will start to look at it as entertainment instead of learning.
here are my takes from this video: find your interest (its linux, vim, android, and java) learn one language at the core leave (got a core java book, from today i will read it), and love what you do. i guess
This article is true but the thing I'm chock was I discover this was possible in Go to recover from a panic and so I search on internet and YES ! There is someone that use it to implement a try catch style library ! I'm chocked xD
Perfect sponsored content imo. Just reading articles like you always do, so being sponsored to do articles on a particular site is completely fine when the quality of the articles are up there to begin with.
Tutorials can be useful if they explain the why of things. Instead of going straight to how to do it, they can make pauses and tell you other ways you could consider and why they were not chosen. In the end nothing replaces practice but I think tutorials could be way better tbh
i'm confused. before i remember him saying you need to do 10k hours. which i didn't like cause it seemed dumb in the same way that saying do 999 leet code problems is dumb. spending too much time on an unknown variable . but the way he talked about leet code here seems more inline with what i believe about the 10k hours stuff. put in the hours and work hard because you do need that skill. but don't go full force into it. Cause you still don't know what it is exactly you need to know or do. Like if you know 100% that if you put 10k hours into learning software engineering it will guarantee you a job then by all means go a head and do it. but for most they won't know what they're doing and just end up wasting that time. instead just see if you can even do 100 hours or 50 hours of learning SE or really anything. just to see if you're capable of doing it. then just slowly keep going up from there. really consistency is key
I dont mean to sound like shill, but codeacademy or places like that are great. People, often stuck in tutorial hell are watching and copying youtube projects, can benefit from having a structured program that goes A to Z in fundamentals and then learning frameworks.
The irony of the Dunning-Kruger effect -- which suggests that people with poor knowledge of a topic overestimate how much they know about that topic -- is that people with poor knowledge of the Dunning-Kruger effect overestimate how much they know about the Dunning-Kruger effect.
Data structures, memory management, etc. Higher level languages are great for getting things done quickly, but imo they dont allow the programmer to dig deeper and uncover the inner workings of what the computer is actually doing.
You're missing a systematic, comprehensive knowledge and instead getting mythical thinking. If you don't know how things work and how everything is connected you're only capable of cargo cult programming.
Yeh, in my opinion/experience tutorial is the best way to get introduced to a subject and see how people organize code and files. Unless you have a mentor your code is gonna look messy otherwise and well you know some things exist. But then again, it is just an introduction, we gotta take it for ourselves to learn about why it works that way and try to edit the given code and experiment further by adding our own ideas
I started using neovim after watching you and now i am fucked... No productivity since last 3 4 months ... Every time i feel like it's working properly and then after some time something other get stops working... If tailwind language server works Emmet stoped if i try to fix Emmet everything other broked .... Jsut now i am frustrated cos i run more than 20 times sfc command .... 4 times reinstalled my wsl backup.... 4 -5 times reinstalled node and nvim and none works so i rolled bank mt window version and i am still stucked .... I literally have bo idea what should i do now ... If possible make some video of how exactly we should troubleshoot all this things ...
Hot take: People want to go fast because the industry romanticizes the demonstration of "quick learner". It's a case where the metric of who's a good hire turns into the goal or heavily affects the goal itself.
Does anyone have an honest answer as to how much more money one can make doing things ‘the slow way’ in the long run? ‘Not everything is about money’ is not an honest answer btw
1:00 Another time for that, if you ever go back to school, don't tell people you work as a developer in the computer science program. Outright lie say you're a dog walker.
Back then, when we started doing Java decades ago, the Java API documentation is perpetually opened in the browser. Nowadays, the new devs, it's StackOverflow, and now Chat Gippty. 🤣
10:30 suchs bullshit. Seeing one way to do it, is the first step to learning anything. I get what he is saying. But he isn't saying it. Which is kinda ironic. There's knowing A way, then The way, then the way for this project. That's often how it goes. And he is making the argument for the way. Or the way for this project. But that's a step too far for beginners. Imagine wanting to make your first burger as a kid and your dadPrimeTime comes in and says, google your way. Don't do the burger tutorial, search for how to cut onions. Talk about making things harder at the beginning than needed. Just relax. It's sort of like the difference between building something such that it works vs such that it doesn't break. This slow learning. Telling that to some sucker without a job. What are we smoking here?
Sounds good; will probably get this and start learning after i finish passing the CPA. I SWEAR, ACCOUNTING SOFTWARE IS GARBAGE - i swear. Accountants who can code would make bank. CCH, im looking at you...
wait why is jumping into nextjs bad? I’m in uni and i wanted to be able to build apps so i learned nextjs and now i’m a full stack dev at a startup using nextjs. tbh i don’t know anything about what else is out there beyond web dev but idt that makes me a bad engineer. there’s so much to learn and so many uses cases for code that you can’t necessarily compare people making different things. at least in my environment web dev is always required and most things are crud apps. am i missing out on something?
When I worked at NASA everybody asked me if aliens were real.😂
Well...?
R they?
And ..?
I became curious instead of laughing
Are they?
"Short cuts lead to long delays" love that. I like saying "the only way out is through; you cannot go around".
As a side note, this is why I recommend also reading books. It's a great way to learn slow where you get more of the background than maybe you thought you wanted, but helps build better intuition than many realize, and a lot faster than trying to only discover it as you go. Someone has put in 5-40 years of knowledge into helping you not have to discover fire again.
Absolutely correct 💯
what would be the essential books? especially as a Business Analyst such as using Python
It depends a lot on your current level and what your requirenents are. I quite like ”Hands-On Machine Learning with Scikit-Learn, Keras, and Tensorflow”. It has a mix of some data wrangling with dataframes, visualization and some analysis with a practical emphasis. Its at a relatively beginner friendly/internediate level. Its quite useful even if your goal is not doing ML. ”Matplotlib for Python Developers” is quite good for visualization. For more software, and less analysis focus, to develop your Python skills you may like: ”Python Design Patterns: A Step-by-Step Guide”.
especialy if you can find one in your own language that helps so much
I don't think reading books makes a difference. Information is Information. Using your critical thinking, testing and experimenting with what you've learned builds the intuition.
reminds me of an old memory.. when I was a kid learning to skateboard I really reaaaaally wanted to grow up to be a pro. beyond obsessed. an older skater told me once while I was learning "don't learn this trick to become pro.. learn this trick because it's fun.. pros are addicted to the fun of learning tricks.. that's all you need." oddly some of the best advice I've had. don't suck the fun out of what you do. being pro won't even be worth it lol.
Was a civil engineer in SF. I taught myself some basic and advanced DSA using Leetcode. Became really good at solving those problems and started interviewing. Got a job and learned building stuff on the job!
Always learn on the job.
I got the job before getting good at leetcode, need to practice for the next job
@nicholaskipchumba9189 I'm attempting the same transition right now. Was Leetcode all you used to start learning before you landed your first job? If there were other resources you used (or any general advice you could give), could you please share it with us?
I am a civil engineer looking for a transition how should I convince hr or company and what skills are required for transition.
I'm glad someone else has said what I've been thinking and doing throughout my entire journey in becoming a well rounded developer. I build things that I want to use. That really helped me get the foundation as from there, because of that process, I've naturally grown interests in other technical areas which acts as a positive feedback loop to further expand my skills.
Interestingly, I think this is the main value a formal software education provides. I went to college for four years to study computer science. In my case, I did it because I "was supposed to" (I had a very rigid upbringing and very fortunate financial circumstances), but looking back on it, it provided the environment needed to build skills _slowly_. That environment included explicit teaching of basic concepts, projects in which to apply those concepts, and scrutiny of those projects to correct mistakes. One critical aspect of this is that, while it required discipline to stay on track and make the grade, some amount of the "discipline" requirement was removed thanks to the curriculum and benchmarks being set externally.
If you can get those things without a formal education, it can be much cheaper! But you will have to build your own curriculum and set your own benchmarks, which requires a mountain of discipline that a formal education would give you automatically.
I don't know that I necessarily have a point here, only an observation that formed while I was watching this vid.
Word
it depends dude, just coz ur experience with a formal background was a good one does not mean other share that same sentiment. its extremely variable & in my case, ive learnt more about programming thru my own self experimentation & grind, so much so the kids in my class call me a "genius" when i come up with a solution to a problem that even the lecturer did not think about. in reality i just grinded my ass off for years alone & it paid off.
While the pacing was slow I bet there were many people as part of your class who were "damn, I already know that stuff, let me go faster please".
I full agree. I was self-taught in high school through gamedev projects + motivation, but formal education was still very helpful. It exposed me to other programming paradigms (functional, declarative), and languages in general (gamedev was 100% C++). It exposed me to other programming problem spaces: XSLT, database, networking, and systems programming. While 85% of my core capability on the job for 14 years was self taught, that remaining 15% slowly picked up in college was very broad and is highly valuable because it's what allows me to pick up any programming industry job and know that I've probably already seen the core difficult problems. Only the surface level problems will be new, as they would to almost anybody who isn't directly knowledgable.
When you're limited to looking at someone's value in one team, it can be hard to distinguish who learned slowly, and who learned and applied things "quickly." Those who applied knowledge quickly will quickly be unable to solve more difficult problems because they fail to learned and are barely able to identify the difficult problem at hand. Those who learned a lot of things slowly will comfortably move to different surface level frameworks, languages, or libraries as needed whereas those who don't really have the underlying knowledge will be far less comfortable with this.
For me, the community factor was extremely important. I wouldn't be able to study half as much had I not been in contact with other high performance students, and of course inspiring professors, every single day.
I agree with the statement "Tutorials aren't for learning"; you are literally copying with the extra perspective from the tutorial maker.
An actual learning experience would be to modify the tutorial as you are following it, add extra features you would want; or after you complete the tutorial, use it as "boilerplate" for a personal project.
This. Following tutorials without modifying and building just leaves one feeling lost when they actually try to build something. And painter can only get better at painting by painting a lot. The same can be said about programming.
I use chatGPT and Phind. But there is a specific prompt you need to give it so as to not compromise your learning. You need to specifically tell it not to give you a snippet, full answer, or an example of it's use. Just give you the element or attribute that is related to what you want.
For example;
Bad prompt:
How can I color this box red?
This will have it give you the full prompt you need to copy and paste in there. But what do you learn? Nada.
Good prompt:
What attribute can be used to color a box red in HTML? Do not provide a snippet or example.
It'll spit out a list of possible solutions to this problem, and you need to figure out which one is suitable, and how to use it.
Honsetly this at 10:20 has become clear to me after I built a chat client at work then watch prime build it on his other channel and it was so fun because i got to see how someone way more experienced build it and I think I learned more just by watching
Can you link me the video?
That reminded me about reading physics books. Specifically for the rigorous books about theoretical physics, people always said that those books are not for learning the material as a noob. But when you already understand the material, you can read it and really appreciate how well written the book was lmao
do you have a link of that video?
Thank you for this video, I'm currently a student at 42, and I'm seeing too many people getting their way thtough with git copy. I'm glad that I'm taking the slow path to learn how to code, how to build something !
As someone who has been through tutorial hell many times, this is so 100% true. Learn the fundamentals, it's majorly important.
i can't understand the tutorial hell thing, i just installed linux and automated my way to do things
0. Find what problems you're passionate about solving
1. Learn the fundamentals
2. Solve problems while learning interesting things about the languages you're using to solve the problem
3. Find a way to show off your work in an appealing portfolio for the work you want to do
4. Network relentlessly
5. Repeat 1-4 until profit!
saved me 12:44 minutes, thanks
i DON'T EVEN KNOW what i'm passionate about to check whether they have A TECH PROBLEM
This is more or less exactly what I did. I spent 10 years on steps 0-2 because it never crossed my mind I could work as a developer. Then 5 years ago I started going to meetup events to get to know other programmers with the same interests. I showed off what I made to someone and they invited me to come work for them. It occurred to me later that those events were actually for networking.
this
@@astrolemonade349 You could've just googled the article...
My honest advice is: if you like software development / engineering, then come to this industry.
After all, passion and professionalism are all the things which do actually matter.
Be smart is true, it is like you have said in the past, get hands-on. If one wanted to become an Olympic Gymnast, they would get on the beam and fall down and get back up and keep falling down. The only way forward is practice and working through docs however it is actually DOING by coding, using print debugging or actual debugging to understand primitives compared to more complex objects, etc...
God I love the honesty up front for being sponsored, thank you!
This channel is one of the best on RUclips, it has the best quality advice to time ratio too
I used to be a developer at some R&D department in the national postal service in Norway. When people asked me what I do, I would always get questions about lost packages and things way outside my scope. And especially at parties people would start pitching ideas or rant/banter about some bad experience they had with the service.
As a frontend/backend developer.. I’ve learned to disassemble other people’s code and have a good instinct to know when someone else’s answer to a problem is garbage and only makes things worse.
I’ll do tutorials only to see or understand a part of it.. then I go build something different, if similar, try to build it in a unique way, change the ui, do it in another language .. or try to build a MVC in js, without a framework.
I am beginning developer. At a certain point I just wanted to improve so I started building the apps I wanted to build even if I had no idea what I was doing. I feel so much better when I find a solution rather than watching a whole completed tutorial.
I need to do this lol
It's a great advice in general, but for some people programming is a way to finally have some money to be able live their life. So for people struggling without money it's actually great to take shortcuts to land a job. And after this point this advice about learning programming deeply is really great, because that's how you advance your career and can provide for your family way better
I use chatgpt, but only to ask about the methods and quirks of the language itself. I still bang my head against the logic wall myself all the way through. And frankly, that's how I LOVE doing the learning.
I have to say AI has been a blessing for someone like me, who has no attention span for tutorials and courses, and learns hands on.
its not about attention span or tutorials and courses, its about how much time chat GPT saves you. I could google my way through a problem, and yeah ill find it eventually... after checking 5-10 links that lead me down rabbit holes that dont do anything. OR i could go to GPT, describe my problem, and it will find a solution in a minute, and if its wrong, ask for another one. I think this is where people go wrong though, like in the video, dont take the steps at word value, you have an infinite source of knowledge that gave you these steps, if in any of them you have a question about what it used or something youve never seen before, literally just ask gpt and it will tell you. now not only are you going through rabbit holes, but now you are going through them with it actually being relevant to your problem, and now you've learned so much about stuff you didn't before. Another thing, NEVER copy paste anything gpt gives you, type it out. learn by doing, not seeing.
can you give an example ?
Ive learned this the past year or two with my programming career while studying for my CS degree. I thought I knew how to program because Ive used some javascript and python. Wasnt until I actually starting building projects for fun that I realized I learn when trying to solve problems I actually want to solve, not following tutorials.
Honestly, what if there are no problems you are interested in/have a passion for?
Ever since I left college, I've found to be in that spot.
just tried this website and its so much better then tutorials, it literally teaches you the concept and then gives you some code with errors and its on you to fix said errors.
This is awesome.
@ 7:30, The Seven Levels of Tutorial Hell makes so much sense for the things that were listed 😂
Loved this video and loved the article, thanks dude!
Was recommended your channel by the algo. Loving the contents so far. Thanks for sharing this video!
I am new to development. Took a js bootcamp. In the middle of it life threw me a curveball and I got canned from a stupid sales job because the manager had it out for me… idk how I completed the bootcamp but I did and after that I was forced to take the a+ by my field it job… then they canned me lol.. seems tragic but every hurdle life throws at me I have kept faith in god, I have a work from home job now(not dev) but I am finally able to spend more time developing my apps… it’s amazing to learn new things and branch out. A+ may seem stupid but you can understand so much more about software when you keep it interesting and never let life get the best of you. No matter how many times you get canned 😂
I totally agree. Don't just fix the bug, fix the root-cause. Just to add to that, yes, sometimes you need to take shortcut and just fix the bug. But in that case I would say add tech-debt story to fix it later 🙂
Got my first “real” job because I did a project in django.
Whatever people people say it’s not set in stone.
Go around breaking and fixing stuff. You’ll find your way.
Documentation for learning.
Lectures / courses for additional information.
Talks / presentations for interesting information.
Tutorials for telling people "I'm learning ".
Tutorial hell is the bane of my existence, but just having a goal/project that you want to do and going at it is also a terrible experience. You end up taking a chaotic path towards the goal, quite possibly learning very bad habits or patters in the way.
Spoon fed instructions are not very useful, but you need some sort of mentoring to not only learn properly, but learn efficiently.
yeah I feel you… how do we actually get some sort of mentoring along the way of building our projects is a great question
Lane is 100% right. His site is great too. I did the trial and am seriously thinking about subscribing. It's legit a fun way to learn coding.
im from germany and its a little bit hard to follow but mannn - i love your tech talk. You have something from the "Great Teacher Onizuka" style in Software Engineering
Shortcuts lead to long delays - outstanding, premium thought.
It hits the target.Brilliant!
In technology shortcut sometime is a cause of short circuit.
Jumping over the doc details can lead to serious issues in emergency situation.
I enjoy Tolkien's books very much. Cheers!
the title of the video: "The BEST Way To Become A Software Engineer"
the content of the video: "Can't Determine"
all my friends who are doing internships tell me to watch tutorials to learn the swift language, i on the other hand only use books and chatgpt , becuase you can learn alot from those two than watching any tutorials, also i told my friends the exact same thing about tutorials leaving mostly 70 - 80 percent of the knowledge you can gain from books and chatgpt, also another thing i would like to add is that watching tutorials for a long time, you will start to look at it as entertainment instead of learning.
Netflix business plan for 2025: Remove auto playing trailers
I spat my coffee out laughing when you attempted to say, "clusterf*ck asterisk". Pure comedic gold.
As someone learning frontend this was great. Thanks for the ad lol😅😂
The best way?
Be an 11 year old. A neckbeard busts down your door and says "You're an SE, Harry."
here are my takes from this video: find your interest (its linux, vim, android, and java) learn one language at the core leave (got a core java book, from today i will read it), and love what you do. i guess
Can't like this video (and the article) enough.
I love that you quoted "Tolkien"!!!
Could you help to navigate my thoughts towards the aswer on "How to find what I'm interested in as a project to build?"
This article is true but the thing I'm chock was I discover this was possible in Go to recover from a panic and so I search on internet and YES ! There is someone that use it to implement a try catch style library !
I'm chocked xD
1:13 I wonder how this conversation would go with an engineer at prnhb!
..could lead to some interessting questions!
Ive found that i learn the best when im solving my own problems
Perfect sponsored content imo. Just reading articles like you always do, so being sponsored to do articles on a particular site is completely fine when the quality of the articles are up there to begin with.
Dang, this is golden. Shaaaariiiiing
"Google your way into the building:" sounds like pentesting ^^
What extension is he using to get that dark mode? Doesn’t look like dark reader
When I worked for Tesla people wanted discounts on cars
be the tutorial you want to see in the world
Tutorials can be useful if they explain the why of things. Instead of going straight to how to do it, they can make pauses and tell you other ways you could consider and why they were not chosen. In the end nothing replaces practice but I think tutorials could be way better tbh
I’m 27 and I have built many PCs and have basic knowledge over computers would it be considered to late to pursue a cybersecurity career
Me when i found my passion for computer graphics 5 years into college
i'm confused. before i remember him saying you need to do 10k hours. which i didn't like cause it seemed dumb in the same way that saying do 999 leet code problems is dumb. spending too much time on an unknown variable . but the way he talked about leet code here seems more inline with what i believe about the 10k hours stuff. put in the hours and work hard because you do need that skill. but don't go full force into it. Cause you still don't know what it is exactly you need to know or do. Like if you know 100% that if you put 10k hours into learning software engineering it will guarantee you a job then by all means go a head and do it. but for most they won't know what they're doing and just end up wasting that time. instead just see if you can even do 100 hours or 50 hours of learning SE or really anything. just to see if you're capable of doing it. then just slowly keep going up from there.
really consistency is key
The 10k hours was some bullshit malcolm gladwell spewed out in a biook
I dont mean to sound like shill, but codeacademy or places like that are great. People, often stuck in tutorial hell are watching and copying youtube projects, can benefit from having a structured program that goes A to Z in fundamentals and then learning frameworks.
don't get a tutorial, become the tutorial!
The irony of the Dunning-Kruger effect -- which suggests that people with poor knowledge of a topic overestimate how much they know about that topic -- is that people with poor knowledge of the Dunning-Kruger effect overestimate how much they know about the Dunning-Kruger effect.
What I don’t understand is what are you missing if you go with higher level languages? What are those fundamentals that is very important to have?
Data structures, memory management, etc. Higher level languages are great for getting things done quickly, but imo they dont allow the programmer to dig deeper and uncover the inner workings of what the computer is actually doing.
You're missing a systematic, comprehensive knowledge and instead getting mythical thinking. If you don't know how things work and how everything is connected you're only capable of cargo cult programming.
Not missing anything. Dont listen to the malloc bros
You know what.. Someone once gave an advice for developers, he said "get out from your confort zone and start something in Ai"
Hey! Tutorial IS for learning! I never learned as much about assembly programming than writing a tutor :D
Yeh, in my opinion/experience tutorial is the best way to get introduced to a subject and see how people organize code and files. Unless you have a mentor your code is gonna look messy otherwise and well you know some things exist. But then again, it is just an introduction, we gotta take it for ourselves to learn about why it works that way and try to edit the given code and experiment further by adding our own ideas
I started using neovim after watching you and now i am fucked... No productivity since last 3 4 months ... Every time i feel like it's working properly and then after some time something other get stops working... If tailwind language server works Emmet stoped if i try to fix Emmet everything other broked .... Jsut now i am frustrated cos i run more than 20 times sfc command .... 4 times reinstalled my wsl backup.... 4 -5 times reinstalled node and nvim and none works so i rolled bank mt window version and i am still stucked .... I literally have bo idea what should i do now ... If possible make some video of how exactly we should troubleshoot all this things ...
Hot take: People want to go fast because the industry romanticizes the demonstration of "quick learner". It's a case where the metric of who's a good hire turns into the goal or heavily affects the goal itself.
i don't care i am going to master C and only then move on 😿 to cpp or rust (tho i am doing go too hehe) (electronics major)
Yes. to all of this, yes
Does anyone have an honest answer as to how much more money one can make doing things ‘the slow way’ in the long run?
‘Not everything is about money’ is not an honest answer btw
thumbs up for the LOTR quote 👍
Like Pimpin says, "short cuts lead to long delays" 😎
Holy shit this one was good!!! 💯👊
I'm baller at chat got 😂 I'm decent at programming too but I love that chat got allows me to learn and adapt faster
**** stack overflow
yeah i wanna become an employee!
1:00 Another time for that, if you ever go back to school, don't tell people you work as a developer in the computer science program. Outright lie say you're a dog walker.
we got Hitler streaming before GTA VI
Most practical advice, kudos prim 🎉
Back then, when we started doing Java decades ago, the Java API documentation is perpetually opened in the browser. Nowadays, the new devs, it's StackOverflow, and now Chat Gippty. 🤣
That is way I started with rust :)
That's the way I've not started Rust yet. The language looks fun, but the hype was too high.
skill issue
8:53 👀🫡
Wait next js is a fs libary kekw
10:30 suchs bullshit. Seeing one way to do it, is the first step to learning anything. I get what he is saying. But he isn't saying it. Which is kinda ironic. There's knowing A way, then The way, then the way for this project. That's often how it goes. And he is making the argument for the way. Or the way for this project. But that's a step too far for beginners. Imagine wanting to make your first burger as a kid and your dadPrimeTime comes in and says, google your way. Don't do the burger tutorial, search for how to cut onions. Talk about making things harder at the beginning than needed. Just relax. It's sort of like the difference between building something such that it works vs such that it doesn't break.
This slow learning. Telling that to some sucker without a job. What are we smoking here?
thats mean we should to figure out by ourselve. Bro this truly tormenting.
I like this!
My Php framework use file system for routing😂
Rust is the best language if you are looking at EE research jobs and already have at least an MSEE lol.
Sounds good; will probably get this and start learning after i finish passing the CPA. I SWEAR, ACCOUNTING SOFTWARE IS GARBAGE - i swear. Accountants who can code would make bank. CCH, im looking at you...
did you sign up for it? how's the course going?
so asking for help apparently got my comment deleted. thanks :(.
No joke, is this video for absolute beginners?
13:12 - sounds like copium prime....
take shortcuts, get cut short...
Number one take away, after the first few months do not use tutorials anymore! Tutorials are good for reference but ironically not for learning...
Yes, shortcuts lead to Very long delays...
got forced to learn python for my degree. now i cant move away from it.
wait why is jumping into nextjs bad? I’m in uni and i wanted to be able to build apps so i learned nextjs and now i’m a full stack dev at a startup using nextjs. tbh i don’t know anything about what else is out there beyond web dev but idt that makes me a bad engineer. there’s so much to learn and so many uses cases for code that you can’t necessarily compare people making different things. at least in my environment web dev is always required and most things are crud apps. am i missing out on something?
Did you write this article yourself there Prime? 😏
Why people create blogs on such simple topics ? because they don't have to code
People have massively underrated a college / university education. A breadth of knowledge has so many transferable skills that you will never foresee.
Hello from hell 👋
Spring io and React