As a level 100XX developer, I stopped using external dependencies because I realized I was copying and pasting other people's code into my projects. Now I write everything from scratch and I am unemployed.
I write my own compiler before using my code, i also write my OS for every project and create my own pc with breadboards and shit to run the OS on. Not only am i not employed, im not even a real programmer, im a hobby-ist/idiot
That's not really my approach. I think it's much more helpfull to actually consider a logical problem and then try to solve it, preferably without libraries if that's possible. Not because you want to reinvent the wheel or because you want to show off, but because you want to improve your skills. Just like how children learn how to add and multiply numbers mentally and then using paper. Sure you can use a calculator, but to start internalising a concept it's best not to use it. But when simple arithmetic becomes trivial, then use a calculator, otherwise you're wasting your time.
Here's my two cents: there's no point in re-inventing the wheel. Good design patterns that extract and abstract common functionality is the ultimate goal though. HOWEVER, if you copy paste engineer and you don't know how the code works, it's not going to be fun later down the line when you have no clue how to fix it!
This is what functional programming solves. Each function stays focused on one task, and you can compose them in various ways to get the desired result. Most functions are too large and tightly coupled to be shared between two different use-cases.
I'm hitting the DRY wall all the time with React. I try starting with a 'reusable' component that supposed to do something. Then I reuse it somewhere else. Then I need to solve an edge case only on one place with the reused component but not bring any breaking changes to it. And I end up with like this magical component that holds so many logic and it's big and bulky...and I hate it. I actually start to prefer to copy-paste code if it's in like 2-3 places since it's not that big of an issue to change it in 2-3 places.
Yeah *“reusing code, to save time”* is a thing! I can't imagine writing from scratch every time, that's a good way of decreasing productivity while lowering your average income 😂
Agree. The guy off camera is off camera for a reason (and doesn't give his name). There's no way I'm hiring a snob who's going to take way too long to do a project.
Program suppose to make our work easy not hard... You damn right I'm gonna copy paste my code but at the same time develop the skill to know when to do it and what to change according to situation.
Copy paste saves gou time, and tge most important is that when you copy paste you bring the function and keep concentration on the step you was working on, if you dont copy paste, you need to pause the idea you was working on it and start writing that function you needed then when you're done you go back where paused, and thats not good fo production
I copy paste my own code from different projects all the time. Like I made project in 9 different programming language, but as of now, i can only write codes in my latest language. I never really memorised commands syntax. So my paper plan for functions is a mix mash of these 9 prog language.
I copy paste similar enough components, like the Footer from the Header with just some different labels and values. I write CSS "from scratch". It makes total sense to copy paste components, and to me, to build style more or less from the ground up, especially in a framework where your global and Layout styles already style the child components to some degree. Emmets are just informal copy pastes anyway, so not a big deal at all to do it.
I am here 5 years later third day into my coding journey. I quickly learn that you can learn the basics then from there you can get so much information online. Furtmore, when you know the basics you don't need to reinvent the wheel: Copy and paste! lol
i copy paste inside jupyter notebooks all the time, for example if i want to change preds=model.predict(test) to preds=model.predict(validation), i just copy paste both versions and comment out one i dont need in this particular case. Maybe i should put them in function taking parameter, but why should i refactor if even my model does not work correctly yet? In my experience jupyter notebooks very quickly dissolves into spaghetti code
@@boot-strapper Well I think you're entitled to that view to be honest man. I just think it makes it easier to abstract stuff for developers; it works really well along side any kind of complex DB, and honestly, whatever you think it's going to be present in a lot of legacy code that's too much of a company overhead to replace...
RoboChicken | 100% Organic yeah, true. That’s why I only work at companies that are building new things. Legacy code is gross. But let’s be honest, functional is easier to think about. Why do you need to abstract anything? Keep it real. Make it less about magic behind the scenes.
@@boot-strapper Legacy code is gross but someone has to do it. I think you're misunderstanding what I meant by abstraction. I don't have a personal issue with any particular methodology. I just know OOP better and i'm used to it that's all... Each to their own brother...
0:30 I copy paste my code ( I just remember the episode of FUTURAMA where the visit the Slurm factory 🏭) : Leela: How can you trick someone into eating something that comes from your behind? It's disgusting! Slurm Queen: Is it? Honey comes from a bee's behind. Milk comes from a cow's behind. And have you ever tried copy pasting your own code?
Ben, agree 100% w you. Between Day job in IT mgmt, CEO/architect of startup, and coding in Obj-C, PHP, and MySQL there's no way I'd remember how to do everything. Also, stuff needs to get done. I was expecting this video to be about frauds who are trying to get developer jobs who flat out cannot create the most basic functioning app (in my iPhone app world that would be a calculator) without significant 'help' from the Internet.
Am I the only one that thinks the close up on his face the entire time is weird af? Like they are two guys having a conversation, why not pan out and show the two having their discussion?
Honestly at this point, I'm afraid to follow anything that ben says. When I watched the short for this video, I thought this was a parody. Now that I see the whole video, it's the opposite, but very well could be a meta-level satire. Which is it Ben?? Maybe you should consider putting (Satire) or (Not Satire) on the video title, for all us soydevs out here.
As a level 100XX developer, I stopped using external dependencies because I realized I was copying and pasting other people's code into my projects. Now I write everything from scratch and I am unemployed.
XD
High Boss Level XD
This is 😂😂😂😂
So reinvent the wheel over and over again. which consumes not just your time but probably your employers too.
I write my own compiler before using my code, i also write my OS for every project and create my own pc with breadboards and shit to run the OS on. Not only am i not employed, im not even a real programmer, im a hobby-ist/idiot
If your code isn't copy-pastable it's not good code. Code reuse is great.
Optimally it should be re-used without being copy-pasted, though.
Copy-Paste IS very often the starting point. Then you have to follow up by studying how and why it works. Then you've learned it.
That's not really my approach. I think it's much more helpfull to actually consider a logical problem and then try to solve it, preferably without libraries if that's possible. Not because you want to reinvent the wheel or because you want to show off, but because you want to improve your skills.
Just like how children learn how to add and multiply numbers mentally and then using paper. Sure you can use a calculator, but to start internalising a concept it's best not to use it. But when simple arithmetic becomes trivial, then use a calculator, otherwise you're wasting your time.
l dont really see an issue, as long as you understand what the code is doing
Here's my two cents: there's no point in re-inventing the wheel. Good design patterns that extract and abstract common functionality is the ultimate goal though.
HOWEVER, if you copy paste engineer and you don't know how the code works, it's not going to be fun later down the line when you have no clue how to fix it!
What, why cannot copy paste my own code? I have created templates for my self to literally copy paste.
sometimes those templates could be functions
Unpopular opinion: Stack Overflow usually has the best, most optimized solution. The key is to finding it and applying it correctly.
This is what functional programming solves. Each function stays focused on one task, and you can compose them in various ways to get the desired result. Most functions are too large and tightly coupled to be shared between two different use-cases.
I'm hitting the DRY wall all the time with React. I try starting with a 'reusable' component that supposed to do something. Then I reuse it somewhere else. Then I need to solve an edge case only on one place with the reused component but not bring any breaking changes to it. And I end up with like this magical component that holds so many logic and it's big and bulky...and I hate it. I actually start to prefer to copy-paste code if it's in like 2-3 places since it's not that big of an issue to change it in 2-3 places.
In that case I also sometimes split the magical component into smaller magical components
I only copy paste regex
Yeah *“reusing code, to save time”* is a thing! I can't imagine writing from scratch every time, that's a good way of decreasing productivity while lowering your average income 😂
Almost all developers copy paste, if not all developers! 😎 👌
Agree. The guy off camera is off camera for a reason (and doesn't give his name). There's no way I'm hiring a snob who's going to take way too long to do a project.
Ademoye Opeoluwa i guess im one of devs that don't copy paste, i mean i learn from the code first in the internet, then put it in
but wait I was reading that source codes may be licensed and copyright protected. But everyone does it and change it a little
As Stehan Mischoook says, quite often, about the three rules of coding:
1) reuse
2) reuse
3) reuse
No reason to reinvent the wheel every time.
Thanks for this kind of videos. You are letting us know you in a different way and that's cool. God bless you!
Program suppose to make our work easy not hard... You damn right I'm gonna copy paste my code but at the same time develop the skill to know when to do it and what to change according to situation.
Vaku Zaku yea don't be a complete skid
Copy paste saves gou time, and tge most important is that when you copy paste you bring the function and keep concentration on the step you was working on, if you dont copy paste, you need to pause the idea you was working on it and start writing that function you needed then when you're done you go back where paused, and thats not good fo production
Best thing after u learn something and get proficient is to make template. Like auth, validation, database boiler plate
A video for examples of React patterns on the back-end would be nice.
how about some postgresql on the frontend?
Ben Awad does sound interesting.
I copy paste my own code from different projects all the time. Like I made project in 9 different programming language, but as of now, i can only write codes in my latest language. I never really memorised commands syntax. So my paper plan for functions is a mix mash of these 9 prog language.
Copy-Pasta is common for Devs these days, but if you do it more than you either innovate or write your own code, you simply aren't learning anything.
I copy paste similar enough components, like the Footer from the Header with just some different labels and values. I write CSS "from scratch". It makes total sense to copy paste components, and to me, to build style more or less from the ground up, especially in a framework where your global and Layout styles already style the child components to some degree.
Emmets are just informal copy pastes anyway, so not a big deal at all to do it.
It is like asking a car manufacturer, if they use the same pieces over and over again, or design new pieces for each car they assemble. Hilarious.
I am here 5 years later third day into my coding journey. I quickly learn that you can learn the basics then from there you can get so much information online. Furtmore, when you know the basics you don't need to reinvent the wheel: Copy and paste! lol
Felt more like an interrogation than an interview. Perhaps because of the close shot.
Man, I soooo feel you! Also custom hooks can be a pain if you try to make them reusable.
i copy paste inside jupyter notebooks all the time, for example if i want to change preds=model.predict(test) to preds=model.predict(validation), i just copy paste both versions and comment out one i dont need in this particular case. Maybe i should put them in function taking parameter, but why should i refactor if even my model does not work correctly yet? In my experience jupyter notebooks very quickly dissolves into spaghetti code
“Inheritance is gross” OOP must be a lie 🤷♂️
OOP is bad practice, people just like it because they learned it in school and its easy to think about
@@boot-strapper Well I think you're entitled to that view to be honest man. I just think it makes it easier to abstract stuff for developers; it works really well along side any kind of complex DB, and honestly, whatever you think it's going to be present in a lot of legacy code that's too much of a company overhead to replace...
RoboChicken | 100% Organic yeah, true. That’s why I only work at companies that are building new things. Legacy code is gross. But let’s be honest, functional is easier to think about. Why do you need to abstract anything? Keep it real. Make it less about magic behind the scenes.
@@boot-strapper Legacy code is gross but someone has to do it. I think you're misunderstanding what I meant by abstraction. I don't have a personal issue with any particular methodology. I just know OOP better and i'm used to it that's all... Each to their own brother...
Straight up info. Thank you sir!
(I am over my comments limit for the week but) 3:08 (no) INHERITANCE IS GROSS
I don't always copy paste but when I do, instant karma struck back.
Hi! Ben, How i can get the user's location without asking permission from the window 🙏🏾? Such as UA-cam.
You can help me please?
I'm not sure, I haven't tried to do that before
0:30 I copy paste my code ( I just remember the episode of FUTURAMA where the visit the Slurm factory 🏭) :
Leela: How can you trick someone into eating something that comes from your behind? It's disgusting!
Slurm Queen: Is it? Honey comes from a bee's behind. Milk comes from a cow's behind. And have you ever tried copy pasting your own code?
* read title *
yes
im a copy paste coder from stack overflow when I have to do bash script....
Ben, agree 100% w you. Between Day job in IT mgmt, CEO/architect of startup, and coding in Obj-C, PHP, and MySQL there's no way I'd remember how to do everything. Also, stuff needs to get done.
I was expecting this video to be about frauds who are trying to get developer jobs who flat out cannot create the most basic functioning app (in my iPhone app world that would be a calculator) without significant 'help' from the Internet.
IMO as long as you don't stop learning it's fine to copy paste code.
D R Y Technic is not only for function (DONT REPEAT YOURSELF) copy pasting is a way not to repeat yourself (your replicating yourself)
People who copy paste their own code just don’t know how to create snippets in VSCODE or their IDE of choice
i am a copy-paste coder because i dont have time to type it one by one but i know what i am copying
So, decorators seem perfect for optional parameters.
If any line occurs twice in my code, my OCD sets in.
I'll copy paste for loops just so I don't have to type them out again
Before I watch my answer : yes
Great vid!
Now that I have learned hooks I copy paste hooks but now I at least use much less code and its more succinct
Why is the interviewer leaning so hard on this idea that copy/pasting code is 'bad'?
Rory Sandstrom ig that's spoon feeding the beginners
can you use recompose instead of inheritance with React?
Yes and hooks
I copy and paste the things I know, so that I have time to learn the things I don't know :)..nice smile!!
who's not?
2:00 Composition my man. :)
1:12 that's trash
well, you have no idea
This guy is a legend lmao
Yea, copy paste is fine if you know the requirements are going to diverge.
when billion dollars companies can be made on copy paste ideas why not code
YES
Honestly i don’t know anything about this subject but I can’t stop watching this video because he’s cute as a button
Honestly I'd rather see my mates copy paste the whole thing rather than make crazy ass abstractions which are unreadable and can't really be re-used
Aren't we all?
I wish I could see the guy's off screen reaction
🔜
I also copy/paste code :)
I copy paste my code!
Hahaha, you and Me, may be from the same school. But, I am 30 years ahead of you,
lol everyone copy and paste code
Brother I am
"inheritance is gross"
WHAT'S WRONG WITH YOU ?!
Hello world :)
Hello world!
cmn ctrl c ctrl v best way :DD
lol
Am I the only one that thinks the close up on his face the entire time is weird af? Like they are two guys having a conversation, why not pan out and show the two having their discussion?
art
Honestly at this point, I'm afraid to follow anything that ben says. When I watched the short for this video, I thought this was a parody. Now that I see the whole video, it's the opposite, but very well could be a meta-level satire. Which is it Ben?? Maybe you should consider putting (Satire) or (Not Satire) on the video title, for all us soydevs out here.