You are wrong. I've done 5 years masters degree and also bootcamps, courses, and YT videos. CS degree gives you the basics and the theoretical knowledge you need for learning to code on your own. It os after all "Computer Science" degree, mot "Coder Degree". And everything "new and shiny" is the samw thing, just in different colors. I did a Google Project Management for 6 months and it is 90% the same thing I got taught at the "old and outdated university courses".
@manishchandola64689 күн бұрын
Someone I know - I don't have trouble going up the levels, or down, ok sometimes I never want to go below level 3 because the lower 3 levels are hells. (I don't have any EC I just have PTSD)
@timilehineluma160610 күн бұрын
W man 3:08
@studybruh11 күн бұрын
your videos are great! how do you write your scripts???
@MatiasCandia12312 күн бұрын
every level comes with an even bigger existential crisis
@The_Omega12 күн бұрын
Some days i feel like I'm a 2 some days i feel like I'm hitting 4
@mashroom292716 күн бұрын
this is the best lecture Viktor had ever taught me
@dakilla322822 күн бұрын
How relevant are these with the advent of LLMs that can write the best codes?
@oppaedits981922 күн бұрын
Every company chief person in tech should prioritize this stuff in resumes instead of trendy thing, they should pass down this idea to the people who are hiring at the low level this way we won't have to jump from one framework to another just because we want our resume to be shortlisted by ats tool, this way it will reach to us and we will start valuing these things instead of frameworks or the next trendy stuff
@asitmaurya9923 күн бұрын
Berkshire Hathaway Website
@roz124 күн бұрын
Believe me these words are so true that most devs and companies don't understand
@abrarmasumabir380924 күн бұрын
great vid bruh love from BD.
@a.v799825 күн бұрын
This is the video I was looking for. Learning The skills That are Timeless!
@da40au4026 күн бұрын
I learning go and zig simultaneously, go for my production based softwares and zig for fun and low level coding. Since im already good at networking stuffs am just busy here playing with low level code and using zig to build stuffs using the Linux syscalls. Because i know the core fundamentals, i don't suffer when building. If company focuses on the dev technical knowledge, excluding the stack, we would have had god level programmers wherever u go
@KeganVanSickle26 күн бұрын
I think the problem for most developers, is the fact that EMPLOYERS expect you to know their stack, and they are alllllll over the place. HR managers, and AI resume scanners don't understand that a developer who knows the core fundamentals, logic, theories and functionality can learn their stack too. They just see, "oh you don't have the right version of Vue on your resume". Now obviously, this applies only to some employers.
@manishchandola646826 күн бұрын
It applies to a lot more employers. Just see for yourself.
@oscarhagman824726 күн бұрын
in my experience they are the majority
@christianm490624 күн бұрын
They are idiots.
@sevicenowblog24 күн бұрын
Correct.
@havocblastАй бұрын
You know your videos are great when channels like this ripoff the style of your thumbnails lol
@cipherosxАй бұрын
03:00 takes all the even numbers of the array (?) But that shouldn't work as the lambda's parameter is x no y
@br3ntoАй бұрын
Apps which separate back-end from front-end are inherently more complex than apps designed to be developed full stack. That’s not a good thing. It’s completely unnecessary. Plus I suspect that a whole bunch of security vulnerabilities are hidden when you do that. Apps today don’t need to be as complex as they are. I’m often doing refactors on existing codebases that remove up to two-thirds of the code - from the front-end and back-end code. I suspect the frameworks being used and possibly the methodologies encourage the excess code. It’s unnecessary to specialise into a front-end or back-end developer. It’s 100% better to be both.
@raymondmichael4987Ай бұрын
That's awesome, man. Thanks
@alexmylonakis8527Ай бұрын
super high quality video!!! i hope you blow up and get many more views!!!
@nikhils7583Ай бұрын
Nice one
@drittahversАй бұрын
i mean, not a life changing video, but under 1k views in two days, brother u deserve more, this was a fine video with good quality, nice topic and imo good script, hoping ur channel gets to blow up, thats why i leave a comment for the algorithm bcs here it will have more of an impact, altough i rarely leave comments. (fun fact this video was recommended for me through exploring, not by subscription so hoping u got channel growth) good luck and keep it going.
@AbdullahAbdeen-u4zАй бұрын
Very interesting video! Keep it up bro!
@iqdziksilver3884Ай бұрын
Why is Hindi guy reading
@marcoagostinello9735Ай бұрын
One of the most important KZbin videos I have ever seen. thanks
@SolidWorksMastery-hr4sgАй бұрын
i love doing everything , i can't see my self stuck with one role or one task it's boring ....beside being a junior full stack , i find my self reading and learning about design ui ux math physics mechanics 3d modeling woodworking writing drawing and video games and much much more ..... me and people who are like me we are built like this , i know i can provide a living ..... i know i'm good at what i'm doing and i enjoy it that's it ......i don't care about companies that want to run their api in a a potato (despite i would want to learn the technique to do that XD ) ...... generalist will know 9 topics better than a specialist specialist will know 1 topic better than a generalist
@west221bАй бұрын
"Build simplicity, then add lightness." --Colin Chapman, founder of Lotus
@krishnabishtubeАй бұрын
I think the future of programming is potentially all copypasta
@What_do_I_ThinkАй бұрын
Complete out of date. Copy and paste is already dead. Instead we now have AI tools, which in turn make us EVEN MORE stupid. And the good thing: It comes directly in your IDE, so more reason to be lazy and deliver even more crappy code!
@just4fun277Ай бұрын
doesn't matter if it's Stackoverflow or AI chatbots you still copy pasting.
@What_do_I_ThinkАй бұрын
@@just4fun277 Basically yes, but it is worse, since KI suggests that some powerful mind has elaborated the details -- which is not so. You do not only search for an answer, but fill in your complete problem. When you search, you know that you must adapt it. A KI chatbot does that for you -- so the tendency is even more to just take it as it is.
@GermanZindroАй бұрын
All of this also applies to CoPilot suggestions. Never accept a suggestion without reading and understanding it. And even then, it can introduce bugs into your code.
@Egon3kАй бұрын
1:50 no one EVER copy/pasted like this before :D
@Epic_coding200Ай бұрын
i think manually typing the code you are about to paste is still better, and helps us to know what exactly it is
@IvanToshkovАй бұрын
I do that too. Typing it is not mindless, it makes you think "why is this code here?", "what does it do?". Another thing that I do is to refactor the new code. First, the outside code will not match the coding style of my project. Refactoring will help with that. But more importantly, it allows me to understand the new code even better.
@GuRuGeorge03Ай бұрын
yep! unfortunately i've even seen "seniors" doing this. especially now with LLMs being so powerful. Nowadays I see extremely overcomplicated code to achieve a very simple thing and when I ask the dev about it, it often becomes clear that they just asked chat gpt and then iterated on chat gpt's suggestion until it worked instead of really trying to understand the problem to find the simple solution. Example: instead of just applying an index on a database, a "senior" dev recently opened a PR that checked uniqueness on the database using a stored procedure, which is absolutely nuts. Not only that. the code had nearly 100 lines. w t f
@iCookieScriptАй бұрын
Sadly, I am using hyprland, and I messed up something, and now copy paste is not working in my VS code :(
@しめい-l4mАй бұрын
time to move to (neo)?vim, I guess
@iCookieScriptАй бұрын
@@しめい-l4m I guess I have to learn quitting vim
@AndersBregАй бұрын
Did this video mean nothing to you?! 😮 But in seriousness, you could take this as an opportunity to rewrite whatever code you want to copy, and maybe understand it better. Or just fix the error, and keep copying I guess. 😂
@iCookieScriptАй бұрын
@@AndersBreg I believe I still need to improve my understanding of code.
@しめい-l4mАй бұрын
the one I like the best is KISS. just keep it simple, we're all stupid.
@GordonRolandАй бұрын
My experience almost exactly! Only quibble: Comments should only be used where code is not immediately discernible.
@basedest44512 ай бұрын
Bro!!! Shit’s not so complicated 😭🙏 Surely you can’t be a super expert in multiple fields but being just a good specialist in both frontend and backend is not a big of a deal. After all, it’s both software engineering. Yeah, there’s a context switch problem, but it could be much more severe if you’re working only as backend engineer but on 5 different projects in 3 different languages, comparing to working on just one fullstack TypeScript project.
@xtraszone2 ай бұрын
* Prefer guard clause over nested if-else * Use comments if required * At the same time dont add too much comments and bloat your code with coments * Prefer static type languages over dynamic types
@PixelOutlaw2 ай бұрын
The problem with DRY as a phrase is it's not really about repeating yourself. It's about defining and naming process such that you can easily make changes in one place across your code. The opposite of this is copy/paste programming.
@mjcubelo2 ай бұрын
I'm a relatively noob coder and I tend to forget a lot so I flood my codes with comments 😂
@genechristiansomoza49312 ай бұрын
Write a meaningful variable name and method name instead. Don't be afraid even if it's long name. Put comment only to state the reason why you added that code or if the logic is really hard to understand like those of algorithms.
@mjcubeloАй бұрын
@genechristiansomoza4931 this is noted
@user-td5gy2fh3p2 ай бұрын
Cringe. Don't blindingly follow these tips. Without knowing it, you are sending a bunch of new developers down a path that will just lead to inefficiencies, slow performance, bloat to the nth degree, and layers, upon layers, upon layers of useless abstractions. DO NOT BLINDLY FOLLOW what is said in this video. Go watch some Jonathan Blow or Molly Rocket's videos on this sort of thing.
@CW912 ай бұрын
Code comments should not explain what the code does, but why it does it. Don't need to write the obvious, instead write what is implied.
@GordonRolandАй бұрын
My search for the perfect explanation of how to comment is finally over!😀
@dennisdegraphicsdynamo_9992 ай бұрын
Where do you get you memes, gifs, and videos
@Benox-Dev2 ай бұрын
Ohhh This is so good !!
@CharlesHarris-e8l2 ай бұрын
Thanks for sharing such valuable information! I need some advice: My OKX wallet holds some USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). Could you explain how to move them to Binance?
@fabricehategekimana53502 ай бұрын
Dry can be dangerous if badly implemented. For instance the madness of inheritance
@PixelOutlaw2 ай бұрын
Inheritance is very good in CLOS. Now if you're using a language like C++ and its class system, inheritance can be very bad. CLOS even provides a mitigation for inheritance diamonds. This works in part because CLOS shares symbolic slots not duplicating instance members in the inheritance chain.
@fabricehategekimana53502 ай бұрын
@@PixelOutlaw Wow I didn't kknow about CLOS. I have heard about, mixins, traits and type embedding to mitigate the problem of inheritance but I didn't know about CLOS. Thanks
@Schoko-ii6ly2 ай бұрын
Dry is overrated, become a follower of WET: "We enjoy typing"
@D4no00Ай бұрын
@@PixelOutlaw you speak about implementation details of c++ that most of other languages on the market don't suffer from. Inheritance is not a good architectural abstraction to begin with, nobody said it doesn't have its place in specific codebases, but it was always taught as a must-have abstraction. Composition is the correct default in 99% of cases where inheritance was used, it was and is being proved time and time again in many codebases, be they legacy or new ones.
@PixelOutlawАй бұрын
Inheritance (and multiple inheritance) is perfectly foundational for light mixin classes with no side effects. But in a lot of languages you're going to slam directly into diamond inheritance doing that so people will write it off as an anti pattern. Don't use languages that can't handle that diamond inheritance issue.
@asagiai49652 ай бұрын
The first two codes doesn't even do the same thing. Also you don't have to put a long comment if the function is already understandable. Else yeah, your code should be understandable by fellow human especially programmers.
@tristarnoah55602 ай бұрын
i love your content so must
@apilsigdel26762 ай бұрын
Keep pushing those content commits! Enjoying them😀
@da39vinci2 ай бұрын
Definitely agree with point 1 and point 2 but dry should be use with caution. Of course the last rule rings true and one of the reason why i am coding still.