How Lazy Programmers Outperform Everyone
HTML-код
- Опубликовано: 27 сен 2024
- Ever wondered why a casual game of chess with friends takes just 10-15 minutes, while a world championship match can drag on for 6 hours? Are the pros lazy, or are we onto something bigger? Today, we’ll explore how the so-called “lazy” programmers often outshine their peers and how you can leverage these “lazy” techniques for a tactical advantage.
If you enjoy the content, don't forget to hit like and subscribe! See you in the next video.
t10x
Song Credits:
-------------------------------------------------------------------------------------------------------------------
All songs Licensed under Creative Commons: By Attribution 4.0 License
-------------------------------------------------------------------------------------------------------------------
"Thinking Music" Kevin MacLeod (incompetech.com)
"Spy Glass" Kevin MacLeod (incompetech.com)
"Kool Kats" Kevin MacLeod (incompetech.com)
"Hard Boiled" Kevin MacLeod (incompetech.com)
"Acid Trumpet" Kevin MacLeod (incompetech.com)
I agree with the entire point you made, but i think the problem with lazy developers is that absolute majority of them doesn't understand how these libraries and frameworks work on a low level scale, instead they're just searching for the most time saving abstraction in order to ship the final product as soon as possible, without knowing how these dependencies affect performance.
I think having some deep low level knowledge while using high level tools is basically a superpower, because it allows you to be time efficient while writing efficient code.
I agree, knowing what happens under the hood is the real power move
@@fredericotuchtenhagen4851 I feel being lazy is a something you have to your hard for. Until you don't actually unlock the deep knowledge of your field study, you shouldn't be lazy at all
@@ZeEduardo95 yeap, totally, but i feel being lazy is the norm in programming right now, no one is worried about deep learning, it's just about who can learn the most JavaScript frameworks
As a notoriously lazy developer, I wanted to minimize the effort needed for each feature. So, I studied architecture intensely to create a structure that lets me work with minimal context for each business requirement-saving my one remaining brain cell from burnout.
As a computer programmer, whenever I become lazy I never get anything done. I was lazy and depressed and I didn't write a single line of code for 3 months! Thankfully I am sober now. The key thing is to never stop coding. Always do something every day.
I’m glad you are feeling better. Stay strong mate 🙏
1 gulp of VODKA I can write code non stop bro, i follow KISS bro, I follow DRY, i never give up unless last try, I AM PROFESSIONAL GNU LINUX DEV
Programming is thinking, not thping
Depending on the job, according to this video, coding is not a good idea when you can get a low-code or no-code solution. Many times, I wrote a toolset only to find it was already created and better, so why reinvent the wheel?
As a teacher told me, work smarter not harder.
As a certain Primeygen once said, smartness comes with hard work and mental agility
If you know what to ask, you're half way there.
If you're lazy, yet it works, then it's not because you're lazy, it's you're working less because you know how to do things which scale.
Gauss as a child solving the problem of arithmetic series sum is the best example.
Wow youtube actually suggested me something cool and interesting! Great work on the thumbnail though. Awesome content, great points right there.
Subscribed keep it up good quality content
shoulda subbed the first vid...
Good stuff. ButI would suggest that your advices are more applicable for experienced devs, since the majority of the junior devs have no clue how to code less, I'd advice that coding non stop isn't that bad cuz you are learning stuff
The video was mainly for experienced developers, but I’m going to make one just for junior developers in the near future✌️
I use Claude 3.5 Sonnet now so that no more relying on searching for "the best library/framework" to do the job for me
searching for the existing library or framework to do the job is exactly the busywork and leads to extremely sub par results. Slow and lazy professionals know all to well that a third party dependency is a liability and must be a last resort, if all other approaches were ruled out.
Glueing third party pieces of code together is the worst kind of engineering.
HEY! why do you do that to Java!?!?!? Java is the best language!! ;-)
Fun fact: Java was the first programming language I have learnt ✌️
On automation, always do the process that takes 10 mins first, then automate it EVEN if you are "assured" it was a one and done.
It's never a one and done.
I'd agree with everything except for two things.
To become better at doing something, i.e.: writing code; one needs to code more. So "code non-stop" would not be the issue here. The issue would be to code non-stop for the sake of doing so and doing it without thinking "what am I trying to achieve? What problem am I trying to solve". I.e. to be a brainless code monkey implementing ideas that you didn't think of, or to code without thinking what you're trying to solve or how to improve.
The second issue, for me, is that I find it pleasure in reinventing the wheel. If you actually want to understand how something works, trying to come to the solution that works and understanding why it's elegant is a great way of developing deep knowledge. Nonetheless, I still think there's even more value in "trying to break the wheel" and figuring out why it is the way it is and not the other way around.
But this is just my opinion and I prefer the hard way of learning sometimes.
Other than this, this is such a great video, and by being "lazy" I'd figure you actually tire yourself less and get something working by actually thinking the problems thouroughly instead of coding and coding and coding and readjusting, which on itself makes for a much lesser clean path to achieve things.
Even better 0:53 print "std::cout
Infinite money glitch 🔥
git push origin master --force 🗿
10x chessers
Oh! You picked up the right topic. But you phrased it a bit wrong. Just recently I have read psychological research on this topic.
Long story short.
It appears that the performant human brain makes less effort to achieve the result and has less brain activity, while the less performant brain makes a lot of effort, struggles a lot and has very active brain activity. As a result, smarter people on the outside appear lazier.
While both can achieve their results, the energy difference to achieve a goal is huge!
Thanks for sharing, this definitely explains a lot
Two points I disliked how they were portrayed:
Planning first: Unless it's a problem you have a lot of experience solving, chances are, your plans and trying to stick to them, will cause you to lose even more time than just writing something dirty and refining it into a good solution. Some research first would be still prudent, though.
Reinventing the wheel: It's only a waste of time, if you have no reason for doing it. If performance is critical, but libraries you have access to have overhead you can't afford, or are simply not good, then you might want to reinvent the wheel instead. It'll likely be quicker than looking through dozens of libraries, understanding them and profiling them properly. Because all you need to reinvent is the parts of the library you need, not the whole suite of functionality they tend to have, which allows to optimize it further for your project, rather than having lots of functionality you have no use for bog the whole thing down.