Umm, usually true, that's what I thought when I saw the word in 1st paragraph too. But u know, not every motivational story including a gf is fake. But wait, don't, don't say it, I know it, I know what u r gonna say
After serious consideration, we have decided to send this automated response to all the unfortunate people who actually sent an application expecting to have a chance, even though we already had Bob's son in mind for this job when we listed it. We never even read your CVs, but should you want to apply again, be our guest, your numbers will provide valuable statistics for our HR department. Best Regards, A bot.
Your reaction to the bug, holding your breath in a stressful manner out of frustration and anger, made me feel like a baby kicked me in my gut, because that's the feeling I used to get when I started programming lmao. Great video, keep it up!
@@hungry_khid1007 Learn to effectively read documentation, learn when to ask for help, and to efficiently use Google, it's your friend. That's going to help you get through most of your programming issues!
@@dehman6836 i just started im 2 weeks in, im not sure what documentation is and why i always see CS guys talk about it negatively, can u explain what it is and why people hate using it and also the debugger
@@hungry_khid1007 No, documentation is your friend. That’s why this is funny. The joke is that this is the opposite of what you should do when programming (especially when you’re new). Basically: Errors are good, they tell you what went wrong (and where to fix it). Debuggers are good, they help you when you don’t understand what went wrong with your code (good debuggers literally let you see inside your code while it runs). Documentation is good, it tells you how things work, without it, you’ll need to try random things until it works (this is not a good idea). These are all crucial things which help bad programmers (most people lol) write good code without going insane. The worst thing ever is when your code doesn’t work and you have no idea why. These are all things that help with that.
@@hungry_khid1007 For reference, Documentation is any written words that explain how some programming tool/api works and how to use it. The Python 3 documentation (the one in the video) is quite good for new users actually. I know because I used it to learn python myself.
@@KopieOG Regardless, it's a trivial error to find. In fact I'd say 99% of *compiler* errors are trivial to find. Maybe in the old days it could be a bit of headache if you forgot a semicolon in a .h file and did a bunch of code afterwards.
The print debugging sent me. I do that shit constantly, though I usually end up using some more colorful language to differentiate where the code broke
This is so dissatisfying as an experienced coder. “No reading the documentation” 😂 “I’ll just use print statements” 😂 “I don’t need a debugger” All the opposite to what I do coding, but I do have to admit, I don’t use the debugger often.
If I ever become a CS professor I'll make like 10 GitHub accounts that all have like all my assignments "solved" but wrong. (Each one wrong in a different way) But the automatic testing software will accept these submissions. And only after the due date is over will you be flagged as wrong/plagiarized. Or I'll just change the assignments each year slightly.
Okay to be fair sometimes reading documentation does not always help out for solutions. But... going on forums and wikis about certain concepts along with reading docs does definitely help. CS is more like a group effort thing than 1 on 1 thing which I feel like way to many people and universities treat it like. Like in the end we all are gonna work on a team together so why cant we?
I love this. It's on point and makes me feel good for actually sticking to specifications and grinding to read everything and not feel like a lost soul. I always try to avoid comparing myself to others, but I can't help it sometimes...
My first computer when I started the CS career was so close to being e-waste that it couldn't reliably run the IDE and the debugger at the same time. Add the fact that the only internet we had was a 56K modem that cost a fortune per minute, and the fact that I lived several dozen miles away from college, and you can bet I was an absolute flunk in programming
Internship? Don't. Find yourself a project-based contract instead (the one that only hire you for a project). You'll learn more in that than internship, and it is better for your CV. Debugging? Yeah, don't. Just print_r or console.log it. Documentation? Just read it when you hit a wall, don't read it from the start.
For any students here: that last bit is called "plagiarisation" and Is a serious offense in any university. Just making sure you're not fucking yourself over because the UA-cam man made a funny :)
Spoiler: I know because my team plagiarized, lol. It was the last evening before we were supposed to deliver a document. One of my team-mates copied someone else's work with the intention to use that as inspiration. He gave it to me to double check, but I didn't know he copied it. I thought it looked good and gave an OK. My teacher was VERY lenient and didn't inform the board. We redid the whole-ass document in record time and got a good score - no plagiarisation this time, lol. That moment was a "coming to Jesus" moment, but in the end we got off scott-free, while learning a valuable lesson: don't copy others' stuff.
Curently in college for Software developer. I came there with experience and I am glad to say that everyone but me (and 1 other person) is exactly like this video. I have to keep telling people on a project to not rip things off, do half works etc. Annoying asf
"Software engineering" and "Computer Science" are 2 drastically different things. If I could go back, I'd learn to code (properly) before doing CS. Testing Tooling Documentation Source control etc. It makes the academia part of CS so much easier.
There's so many different kinds of CS students. "The Overachiever" - While everyone else is busy trying to wrap their head around how pointers work and what a stack is, the overachiever has written the solution in AMD64 assembler, just to show off. His solutions often don't involve the techniques asked by the professor, rarely cover the course material and instead go on huge tangents. Professors hate them, because the feel the constant need to announce to everyone else how much better they (think they) are than the rest of the class - while at the same time, their solutions don't work within the required parameters. "The guy who thought he was just going to play videogames all day" - Just what it says on the tin. He has somewhat decent understanding of how computers work, at least on the surface. He understands things like networks, filesystem caching, etc... just because he needs that for video games, but he has little interest in learning anything theoretical. These guys usually drop out and go for something more practical, like systems administration. "The asshole" - He was either asleep or high during all of the lessons, and a day before the submission is due he contacts you and asks you for help. Initially, you think his solution is like 95% working and he just has this bug he can't figure out, but when you actually ask him to show you his work, he either shows you a barebones "new project" template or just straight up tells you he hasn't done anything yet. If you agree to help him, he zones out and basically asks you to write it for him. if you refuse, he calls you an asshole and insinuates towards others that you think you're better than everyone else and don't want others to succeed. If this guy calls, don't answer. "The guy who just doesn't get it" - He is similarly helpless as the previous guy, but with the main difference that he is trying. Like, genuinely trying. But he just doesn't get it. You explain to him what an integer is, and he seems to get it. And like 2 seconds later he asks why he can't store "fifteen" in an int. No matter how much you explain, it just never *clicks* for him. You really want him to succeed, but deep down you know he's much happier studying something else - teaching fish how to climb a tree and all. "The bare minimum guy" - He learns the course material, writes his own code and studies for the exam...exactly as much as he has to. He'll never move any muscle more than he has to. Deeper understanding of the subject? Recommended books? You might as well speak a foreign language he has not bothered learning. However, the bare minimum guy is actually an expert on working efficiently. So while he definitely won't score high, he knows how to get stuff done and that will ultimately be a valuable skill in real life. "The open-source nut" - This guy is similar to the overachiever in the sense that he's way too deep into the rabbit hole already, but instead of broadcasting to the world he is superior to everyone, he broadcasts that he uses Linux or FreeBSD. Not just any distro either, not like Debian or Gentoo or such. He uses a distro you have NEVER heard of before, like Exherbo, Wailnix or Feren OO (only one of these is made-up), and will go on endless rants about how the LGPL is the worst thing ever, how Intel and nVidia are the literal devil and how his entire boot chain is completely open source. Coincidentally, and completely unrelated, he often can't turn his course work in because his wi-fi isn't working at the moment. Be careful when two of these come in contact. "You" - You, of course, don't fall into any of these categories. You do your work with due diligence, but don't overdo it. You read and understand the material, occasionally even go a bit beyond that, but you are definitely not obsessed with it. Your assignments are mostly working, except the harder ones, that have strange bug in weird edge cases. Yes, you could have spent a couple of hours working that out and you have a pretty good idea on how to do it, but why bother for just a few points more?
I noticed it's usually easier to pass a technical interview for a junior position than it is to get accepted into an internship. (Whether your resume gets in, that's another story)
you dont, but in todays world where everyones getting internships when being like a freshman in high school, its pretty much "required" now for something like a FAANG job (obviously it isnt the only thing im just saying that even if its a small part it might be an influential one)
Good luck. Having an internship makes entry level much much easier. I got 2 paid internships under my belt and I didn't struggle finding junior/entry level position unlike most graduates. If you mean unpaid internships on the other hand, yeah, I agree, you don't need those. Companies that do unpaid internships are just downright scummy looking for free labour.
I know about the debugger, and I like the debugger, but sometimes good'ol {print("1"); for [...]{ print("2"); } print("3"); function_call(a, b, &c); print("4");} is a hard habit to break.
"It's just a rejection, you will be fine" When this happened to me: "you know what, I'll work for the government. They pay better and I don't need fake friends (networking) to be there, it's just a matter of passing the application"
I’m in my 4th week of my first comp sci and I have absolutely no idea what I’m doing. I still don’t know what a damn constructor is or how to instantiate an object
The debugger thing - I think a lot of them missed the memo that their prof told them to use vim and gdb as a learning exercise, not to do that forever.
Dude the first one I saw on the title screen holly cow you have no idea how many people have no clue what a debugger is. I once helped my friend try to debug a python assignment and I first asked him: 'dude I havent looked at this in a while so use your debugger and I can try to point out the logic error'. Then he said: 'what is a debugger?' and I gave him a look and was like: '... do your teachers enjoy putting yall through hell and they never taught you what a debugger is...' safe to say lol he didnt forget what it was since or at least I hope he didnt.
You could actually tell that the motivational story was fake when it mentioned a girlfriend
damn nice attention to detail
Umm, usually true, that's what I thought when I saw the word in 1st paragraph too.
But u know, not every motivational story including a gf is fake.
But wait, don't, don't say it, I know it, I know what u r gonna say
@@akaidi1270 too late, r/wooosh
😂😂😂😂😔
@@boyalgo 😂😂😂
After serious consideration, we have decided to send this automated response to all the unfortunate people who actually sent an application expecting to have a chance, even though we already had Bob's son in mind for this job when we listed it.
We never even read your CVs, but should you want to apply again, be our guest, your numbers will provide valuable statistics for our HR department.
Best Regards,
A bot.
Not a good view, not reality.
@@montyhandal7219 cope
Your reaction to the bug, holding your breath in a stressful manner out of frustration and anger, made me feel like a baby kicked me in my gut, because that's the feeling I used to get when I started programming lmao. Great video, keep it up!
Tips please
@@hungry_khid1007 Learn to effectively read documentation, learn when to ask for help, and to efficiently use Google, it's your friend. That's going to help you get through most of your programming issues!
@@dehman6836 i just started im 2 weeks in, im not sure what documentation is and why i always see CS guys talk about it negatively, can u explain what it is and why people hate using it and also the debugger
@@hungry_khid1007 No, documentation is your friend. That’s why this is funny. The joke is that this is the opposite of what you should do when programming (especially when you’re new).
Basically:
Errors are good, they tell you what went wrong (and where to fix it).
Debuggers are good, they help you when you don’t understand what went wrong with your code (good debuggers literally let you see inside your code while it runs).
Documentation is good, it tells you how things work, without it, you’ll need to try random things until it works (this is not a good idea).
These are all crucial things which help bad programmers (most people lol) write good code without going insane. The worst thing ever is when your code doesn’t work and you have no idea why. These are all things that help with that.
@@hungry_khid1007 For reference, Documentation is any written words that explain how some programming tool/api works and how to use it. The Python 3 documentation (the one in the video) is quite good for new users actually. I know because I used it to learn python myself.
Programming rule No.69:
"If it works, Don't touch it."
If it works, just make it better. It’s not like it will stop working, right?
@@QueenElizabeth1sth heh
@@QueenElizabeth1sth Now see you'd think that.
@@kozukiyamato7388 Honestly if something goes wrong use version control.
"Refactor refactoring refactor refactor refactor refactor repeat"
The beginning where you slammed your table was literally me the other day on C++ when it kept giving me an uninitialized variable error lol
THE STRUGGLE MAN 😆😆😆
just initialize the variable????
Its not even an error in most compilers
@@KopieOG maybe he thought that warnings are errors or he had the flag to treat warnings as errors enabled
@@KopieOG Regardless, it's a trivial error to find. In fact I'd say 99% of *compiler* errors are trivial to find. Maybe in the old days it could be a bit of headache if you forgot a semicolon in a .h file and did a bunch of code afterwards.
As a computer science student, I got the job first and went to college after so I could afford the therapy after college
Mind if i ask, how did you get a CS job without a degree? its seems almost impossible
The print debugging sent me. I do that shit constantly, though I usually end up using some more colorful language to differentiate where the code broke
it has helped me soo many times!
Nah that print statements/console logs is god tier helpful still. Even with breakpoints I still need console logs to help multi task
its so helpful
I present to you the power of properly implementing a stderr logger. All hail stderr!
so much spite in the " I still wont read the documentation"
i will never read it!! never!'
This is so dissatisfying as an experienced coder. “No reading the documentation” 😂 “I’ll just use print statements” 😂 “I don’t need a debugger” All the opposite to what I do coding, but I do have to admit, I don’t use the debugger often.
If I ever become a CS professor I'll make like 10 GitHub accounts that all have like all my assignments "solved" but wrong. (Each one wrong in a different way)
But the automatic testing software will accept these submissions. And only after the due date is over will you be flagged as wrong/plagiarized.
Or I'll just change the assignments each year slightly.
Do the first. It'll be hilarious
Damn that's some new level of evil, I love it
stfu don't give em ideas
1st one is funnier but the 2nd one is easier. You should only need like 1-2 accounts to pull it off however.
the "i'll just use print statements" really hit home for me
Okay to be fair sometimes reading documentation does not always help out for solutions. But... going on forums and wikis about certain concepts along with reading docs does definitely help. CS is more like a group effort thing than 1 on 1 thing which I feel like way to many people and universities treat it like. Like in the end we all are gonna work on a team together so why cant we?
I love this. It's on point and makes me feel good for actually sticking to specifications and grinding to read everything and not feel like a lost soul.
I always try to avoid comparing myself to others, but I can't help it sometimes...
I like how you click the google search bottom instead of pressing enter
I know that Amazon rejection letter is real because I got that same one, triggered my ptsd 😂
You continue being you, please
That’s what the world needs, audacity and authenticity
My first computer when I started the CS career was so close to being e-waste that it couldn't reliably run the IDE and the debugger at the same time. Add the fact that the only internet we had was a 56K modem that cost a fortune per minute, and the fact that I lived several dozen miles away from college, and you can bet I was an absolute flunk in programming
Yeah i hate debugging and reading documentation 😂
ngmi
I love reading documentation now, you haven't seen bad documentation, no documentation or code as documentation
I actually did take a solution from Github. Only to completely restructure the code bc it was slow, hard to read, and prone to errors.
The Documentation bro😭😭😂
closes video, proceeds to never open docs or use debugger
"I don't need a debugger, I'll just use print statements"
ME_IRL
I feel personally attacked
debugger? I prefer 1000 print statements
The debugger rocks
As someone who paid 20 bucks for a debugger this hurts on a primal level
the pain of someone writing so much code just to realize to get a error but too lazy to look for it..🍝
couldnt be me (:
1:20 A fwe hours of debugging can save you minutes of looking at the documentation
suddenly thought on my mind. I love you!
This hurts
So glad I'm taking a computer science class in high school instead
5 hours of keystrokes and smart-faced frantic wandering around the forums will save you 20 minutes of reading documentation, lol.
The debugger is great and all until
fork()
You don't have to expose me like that :D
I am here before this channel blows up.
thank you homie i hope i blow up 😆
@@boyalgo It will. And Indians will be responsible.
It's happening. I've got it in my recommendations despite not having looked for this stuff recently 😂👍
Literally me unironically
Waaaiittt 2:55 I do the same thing because it's def a waste of my time to solve it than doing my personal projects
I feel attacked
👹👹👹
reading???? whats that
As I like to say I have a degree in CS and a master's in API Interpretation.
Who uses IntelliJ for python
I just quit being a CS student and became an CIS student.
Reading documentation is better than watching a UA-cam video
Who was you talking to?🤔
Internship? Don't. Find yourself a project-based contract instead (the one that only hire you for a project). You'll learn more in that than internship, and it is better for your CV.
Debugging? Yeah, don't. Just print_r or console.log it.
Documentation? Just read it when you hit a wall, don't read it from the start.
For any students here: that last bit is called "plagiarisation" and Is a serious offense in any university. Just making sure you're not fucking yourself over because the UA-cam man made a funny :)
Spoiler: I know because my team plagiarized, lol.
It was the last evening before we were supposed to deliver a document. One of my team-mates copied someone else's work with the intention to use that as inspiration. He gave it to me to double check, but I didn't know he copied it. I thought it looked good and gave an OK.
My teacher was VERY lenient and didn't inform the board. We redid the whole-ass document in record time and got a good score - no plagiarisation this time, lol.
That moment was a "coming to Jesus" moment, but in the end we got off scott-free, while learning a valuable lesson: don't copy others' stuff.
@@NostraDavid2 Don't copy others and coding in the same sentence doesn't make sense
Nice vid
Felt this
Lmao
rofl
Relatable
3-4 hrs is actually a better outcome than browsing through Python docs.
So true
wtf its me
LOL
Haters gonna say the motivational story was fake
print > debugger
Curently in college for Software developer. I came there with experience and I am glad to say that everyone but me (and 1 other person) is exactly like this video. I have to keep telling people on a project to not rip things off, do half works etc. Annoying asf
Noice
tanks :)
Lol
"Software engineering" and "Computer Science" are 2 drastically different things. If I could go back, I'd learn to code (properly) before doing CS.
Testing
Tooling
Documentation
Source control
etc.
It makes the academia part of CS so much easier.
Lmaooooooo
Wt frick, that jaff doing as GF
hey man surprised me too 👀👀
@@boyalgo 👀
This is slander
more like: amateur programmer be like:
Your Chinese accent
Hey, what's that? Permission error? Why don't I own everything? Let me just...
sudo chown $USER:$USER -r /
Oh fuck
There's so many different kinds of CS students.
"The Overachiever" - While everyone else is busy trying to wrap their head around how pointers work and what a stack is, the overachiever has written the solution in AMD64 assembler, just to show off. His solutions often don't involve the techniques asked by the professor, rarely cover the course material and instead go on huge tangents. Professors hate them, because the feel the constant need to announce to everyone else how much better they (think they) are than the rest of the class - while at the same time, their solutions don't work within the required parameters.
"The guy who thought he was just going to play videogames all day" - Just what it says on the tin. He has somewhat decent understanding of how computers work, at least on the surface. He understands things like networks, filesystem caching, etc... just because he needs that for video games, but he has little interest in learning anything theoretical. These guys usually drop out and go for something more practical, like systems administration.
"The asshole" - He was either asleep or high during all of the lessons, and a day before the submission is due he contacts you and asks you for help. Initially, you think his solution is like 95% working and he just has this bug he can't figure out, but when you actually ask him to show you his work, he either shows you a barebones "new project" template or just straight up tells you he hasn't done anything yet. If you agree to help him, he zones out and basically asks you to write it for him. if you refuse, he calls you an asshole and insinuates towards others that you think you're better than everyone else and don't want others to succeed. If this guy calls, don't answer.
"The guy who just doesn't get it" - He is similarly helpless as the previous guy, but with the main difference that he is trying. Like, genuinely trying. But he just doesn't get it. You explain to him what an integer is, and he seems to get it. And like 2 seconds later he asks why he can't store "fifteen" in an int. No matter how much you explain, it just never *clicks* for him. You really want him to succeed, but deep down you know he's much happier studying something else - teaching fish how to climb a tree and all.
"The bare minimum guy" - He learns the course material, writes his own code and studies for the exam...exactly as much as he has to. He'll never move any muscle more than he has to. Deeper understanding of the subject? Recommended books? You might as well speak a foreign language he has not bothered learning. However, the bare minimum guy is actually an expert on working efficiently. So while he definitely won't score high, he knows how to get stuff done and that will ultimately be a valuable skill in real life.
"The open-source nut" - This guy is similar to the overachiever in the sense that he's way too deep into the rabbit hole already, but instead of broadcasting to the world he is superior to everyone, he broadcasts that he uses Linux or FreeBSD. Not just any distro either, not like Debian or Gentoo or such. He uses a distro you have NEVER heard of before, like Exherbo, Wailnix or Feren OO (only one of these is made-up), and will go on endless rants about how the LGPL is the worst thing ever, how Intel and nVidia are the literal devil and how his entire boot chain is completely open source. Coincidentally, and completely unrelated, he often can't turn his course work in because his wi-fi isn't working at the moment. Be careful when two of these come in contact.
"You" - You, of course, don't fall into any of these categories. You do your work with due diligence, but don't overdo it. You read and understand the material, occasionally even go a bit beyond that, but you are definitely not obsessed with it. Your assignments are mostly working, except the harder ones, that have strange bug in weird edge cases. Yes, you could have spent a couple of hours working that out and you have a pretty good idea on how to do it, but why bother for just a few points more?
It's kinda problem that multiple of these fit me. Not the achiever kinds
I'm between 4 and 5 lol
This comment is literal gold. I wish YT had a points systems to reward comments like on reddit. Thank you for the trip down the memory lane.
@@earthling_parth or any feature like favoriting or donating to comments. FFS commenters are always 2nd grade on this platform.
Nice one, can definitely notice some of these traits among my fellow students. Definitely think i hover around the "minimum effort guy" myself
3 or 4 hours to solve the problem is pretty optimistic
Me: "My debugger is called fprintf"
The teacher: "Don't change anything"
@@Oikonny _That guy_ probably has no idea what stderr is.
The debugging and documentation ones hit me on spiritual level lol
Internship? You can apply for a full time entry level job after getting your CS degree. You don't need internship.
Good luck
I noticed it's usually easier to pass a technical interview for a junior position than it is to get accepted into an internship. (Whether your resume gets in, that's another story)
exactly
you dont, but in todays world where everyones getting internships when being like a freshman in high school, its pretty much "required" now for something like a FAANG job (obviously it isnt the only thing im just saying that even if its a small part it might be an influential one)
Good luck. Having an internship makes entry level much much easier. I got 2 paid internships under my belt and I didn't struggle finding junior/entry level position unlike most graduates.
If you mean unpaid internships on the other hand, yeah, I agree, you don't need those. Companies that do unpaid internships are just downright scummy looking for free labour.
"I don't need to use the debugger. I'll just use print statements."
Okay okay okay okay okay okay
that one hit me like a fucking truck
Don’t sleep on chick fil a. They rejected me the same summer I got into Google lmao.
This is literally every internet-savvy student I ever tutored. 😨
1:37 I felt that
I know about the debugger, and I like the debugger, but sometimes good'ol {print("1"); for [...]{ print("2"); } print("3"); function_call(a, b, &c); print("4");} is a hard habit to break.
did it break here? 1
did it break here? 2
did it break here? 3
😂😂😂
Why spend 15 minutes reading documentation when you can spend 4 hours debugging the code on your own.
I prefer to let stack overflow point me to the essential reading of the documentation...
I've never used the debugger in my life except that one bachelor cs class that made us do it.
too relatable
*anything* “whaz that”
"It's just a rejection, you will be fine"
When this happened to me: "you know what, I'll work for the government. They pay better and I don't need fake friends (networking) to be there, it's just a matter of passing the application"
ohh man he is literally me , i never read documentation of python modules instead i watch youtube videos LOL😅🤣
I’m in my 4th week of my first comp sci and I have absolutely no idea what I’m doing. I still don’t know what a damn constructor is or how to instantiate an object
If this isn't a joke, then the internet is here to help :)
A constructor is a man, often standing in an uncompleted building, putting bricks to complete it. You're welcome
youll learn on the way! i felt clueless while starting school and i feel just as clueless on the job l. it just takes time!
i didnt even code until my 3rd year in uni and yet im a software engineer now lol
Look up TheCherno for concepts, taught in c++ but quick and well thought out, his constructor video might help
lmaooo, you're the best boyalgo
youre the best buddy :)
He's the best boyalgo, because he's the only boyalgo.
The debugger thing - I think a lot of them missed the memo that their prof told them to use vim and gdb as a learning exercise, not to do that forever.
the debugger one is so good
Debugger? You mean print in every line yes?
Dude the first one I saw on the title screen holly cow you have no idea how many people have no clue what a debugger is. I once helped my friend try to debug a python assignment and I first asked him: 'dude I havent looked at this in a while so use your debugger and I can try to point out the logic error'. Then he said: 'what is a debugger?' and I gave him a look and was like: '... do your teachers enjoy putting yall through hell and they never taught you what a debugger is...' safe to say lol he didnt forget what it was since or at least I hope he didnt.
Dude I swear to god I just realized from this video of what debugger does after doing multiple website creating assignments..
This is true only for students who actually don't want to learn and resign after their first year.
I think I need a debugger for my debugger because it isn’t showing me the variables
The first 10 seconds is the best descriptive utube video intro I've ever seen on a coding channel
whats wrong with print statements??
I like programming
😂😂😂😭
👹👹👹👹
Yes
😂😂😂😂
👺👺👺