0:00 Event Presentation 2:03 Presenter Introduces Uncle Bob 3:41 Uncle Bob Introduction / My Tribe 4:49 How Far is the Sun? 10:52 Introduction to Clean Code 12:21 The current Society works with Software 19:47 Volkswagen case / Introduction to the Ethics of Software Development 24:28 Why are Programmers so slow? 32:13 What is a Clean Code? 40:09 Analyzing some lines of code 43:43 Long code is not Good Code 49:25 Good Code / Refactored Function 52:40 Polite Code / Rules for writing a news paper article 55:25 Shrunk Code / The Rules of Functions 1:00:23 Shrunk Code / Drawing a Function 1:05:36 When and why was Java invented? 1:08:52 Prose Code / Arguments 1:16:13 Avoid Switch Statements / Problems and Evolution of some programming languages 1:26:15 The Uncle Bob's wife message (funny moment) 1:27:22 Output Arguments No Side Effects / Garbage Collection 1:32:21 No Side Effects / Using Lambda 1:34:26 No Side Effects / Command and Query Separation 1:35:30 No Side Effects / Prefer Exceptions to returning error codes 1:37:05 DRI Principle (Don't Repeat Yourself) 1:39:21 Structured Programming / Edsger Dijkstra Vision vs Actual Vision of the programming
After 40 years of programming, I experienced all the cases described. I just want to say how great you describe the feeling when reading code. At this level, clean code becomes poetry.
Got a weird combination of determination and goosebumps. Imagine being this good at something, let alone something that is as difficult as programming.
I have been a programmer in the 80s. In between I worked with databases a big chunk, took on the IoT, Gui, and now getting back to basics again. It was interesting how things changed over time when in the past, we knew there are better ways but there was just not enough 'time' and not enough powerful hardware. Thank you for making this lecture public. I utterly enjoyed it and the nearly 2 hours flew by. I also sent the link to my daughter who is studying computer engineering at the moment. Thanks a million!
May be you will like our article about Software Architecture, is based in the concepts in this series and more: mutualwelfare.org/organic-architectur-almost-infinite-scalability/
The concept of a "wormhole" or shortcut through space-time was first proposed by physicist John Wheeler in the 1950s, but it was popularized by the science fiction TV show "Star Trek" in the 1960s. In the show, the characters used a device called a "wormhole" to travel instantaneously to distant parts of the universe. While the existence of wormholes is still theoretical and has not been proven, they have captured the imagination of science fiction writers and readers for decades and continue to be a popular subject in science fiction today.
30:25 - After finally getting some piece of code to work, you're only done with half the job; you should spend roughly the same amount of time cleaning it. No one writes clean code first because it's just too hard to get code to work. 46:12 - Every line of a function should be on the same level of abstraction, and that level should be one below the name of the function. 52:22 - Polite code allows the reader to exit (=stop reading) early. 58:45 - A function does one thing if you cannot meaningfully extract another function from it. 1:32:22 - To make a method pair safe (remove side effect), use a lambda that does all the processing. 1:34:34 - A function that returns void must have a side effect, otherwise there would be no point in calling it. A function that returns a value should have no side effects. 1:36:00 - A function that has a try/catch block should have no other content beside that block. Within the try block, there should only be a single function call (the actual function that throws the exception).
1:13:10 Never pass a boolean to a function! Instead of that, create two differents functions. Maybe you duplicate some code, but you declare your intention with the method name, you remove a conditional and you don't read useless boolean values in the method call!
I see developers are complaining about the presentation length but as an engineer, I really loved the way he framed the talk from the solar system to a java function. of course, what better example than a man who calculated the sun's distance at 250 bc without any modern tools to understand our lack of creativity and patience for shitty code.
“When someone is drawing something on a screen that you can’t see, definitely keep the camera pointed at them scribbling and miss where they explain what they’re drawing as they draw it.” - Camera Operator
loved 31:54 .. " You are not done when it works , you are done when it's right" . I must say he really makes you look at programming with a different lens . Thanks for sharing this
@@PaulG.369 Just because you can speak it doesn't mean you should, please don't try and obfuscate your pathetic sexist outbursts under the guise of freedom of speech.
Management is the final decision makers. Delivery is the focus in corporates. No sayer's are thrown out. It's ok I was thrown out. But i am glad to learn the standards and follow the practices. I am learning and practicing the clean code very late at my age of 38, but i am glad I could see the big difference while coding. Thanks uncle bob.
This was not only precious but very helpful to me. I though that breaking long functions would lead to more complicated code. However, having the mindset portrayed in this video, I managed to break my functions into its "do one thing" components, and even managed to eliminate redundant variables. And, not as I initially thought, my code is far more readable and maintainable. If there is a bug, you can quickly go to the function you think it is responsible for it, instead of zooming in into long functions and loose yourself. Props to this man! He enlightened me, made me see my own mistakes, and substancially made my life easier as a programmer.
So it's been a few years now since I returned to Uncle Bob, and wow... I must say. He inspired me way back when I was no longer a Junior and hoping to ascend into a more senior position. And now I'm finding myself equally nodding and shaking my head at several points he's mentioning. Predicting them or criticising them. He was not the only influence, but he was a pivotal person in putting me down the path of better code, to try things for myself and form my own opinions. And above all else, I noted just how well he delivered his sessions. He speaks about code, and there's definitely competency there that he builds upon. But his ability to teach, and capture attention, to narrate and inspire or motivate is impeccable. That's the next big challenge - present what you know to juniors and seniors, and do it in a way that leaves them wanting more, not nursing a headache!
Thankfully this is on youtube with the ability to pause, if you feel the need to! But most important is what he says about it. This is not a test, but fantastic inspiration with super helpful observations. Enjoyed it tremendously!
Entertaining talk, but you should show the slides he is presenting while he talks instead of showing him or the audience or the presentation from so far away that you can't read it.
You were no supposed to understand what he talks about, you were supposed just to realize how cool the lector is, that's enough. And that's pretty much all he writes about, unfortunately, e.g. "now I'll give you simple rules how to write a good code", and then the reader-programmer comes to my team and writes the worst eye-gouging code I've ever seen in my life. Sad but true, no lector or couch can make you a good programmer without you putting a lot of afford yourself. Just like in soccer. And the worst kind of couch is the one which is not asking you to put the effort in.
I was trying hard to convince my ex boss to use some good tools and practices in our project, and moving slowly toward using a unified framework, because the current system was nothing but a mess, and he was laughing at me whenever I say that... I left the company after 3 years, now, he can’t hire anyone, because the system became over-complicated and no one can understand what the hell is going on.
This is genius. I laughed so hard because i can realte soooo much to this. Im new to my company and spend like 6 months here and experienced all of it already. Sucking out the energy of my team by being new and unexperienced, experiencing the mess of fixing exisiting code vs the speed of building a green field project etc.
@@kidmosey Not really. After refactoring, now you can more easily understand the function. If you need to understand a lower level of what's going on, then you go into one of the functions that the first function calls. However, most of the time you don't need to know that stuff in order to understand what you need to know. His analogy about news articles is apt if you ask me.
I get what he wants to say with that. But does it make logical sense? When the computer does NOT understand your code you probably can't run it. This is total nonsense. So do I really understand what he wants to say if such a big fallacy or possible misunderstanding is present from the start? Please ignore, these are my 2 subtleties to over-complicate things:)
Uncle Bob is great. I have seen other videos on Clean Coders channel. That's the way to go. This presentation has an exceedingly protracted intro that maybe was supposed to engender excitement, but, as I was anxious to get to the talk, I felt impatient through the entire first 4:49.
I don't think his advice applies to math based functions. When I have an equation which uses 4 variables, I don't see how I can reduce that to 3 arguments. For embedded systems, I dont even use OOP because it's more complicated than functional programming in that context. This talk is corporate coding advice where everything is written for the lowest common denominator. Everything is driven down to a bazillion very short functions.
this is awesome. I Know everything he talks about, but my current job leaded me quickly to forget everything about it. I have to work hard on my motivation, to stay somewhere to not drown in my bad gooey code -.- Thank you for uploading this !
If your current employment prospect consists of a lot of "I want to develop better code, but the boss won't let me", you should consider applying elsewhere. The tide is *beginning* to turn against companies that don't comprehend the value of code quality, and I think any companies that don't realize this quickly enough are going to be caught in the undertow. I'm not qualified to assess whether this change actually has the momentum I think (and frankly hope) it has, but nonetheless I urge you to consider whether it's worth the inefficiency of beating your head against the wall when there are other companies out there.
Seriously whoever did the editing of this speach/video should rethink his life. When Uncle Bob shows you code read at ~42 mins in we don't care about looking at the audience/him/different cameras with not much quality. It's about the bloody code.
I believe this was all done live on a video switcher, the person controlling the video switcher has the mind of production, not programming... someone who thinks staying on the same 'shot' for too long is boring for the audience. This person probably didn't consider keeping the code up. To be honest I thought the production quality of this video was superb. They had someone on a camera tracking the speaker for almost 2 hours, they had someone switching camera feeds and adjusting audio. I dont know if you should say they should rethink their life lol.. it was really well done
@@_TMac the thing I mentioned was the only issue for me. The points you made are perfectly reasonable, still the last page of code wasn't really shown until Uncle Bob was reviewing the code. @Angus MacGyver man, you got me here, like yeah... when I go to the theater I also pause the video, there wasn't a single movie I left unpaused, be it on my couch, or wherever.
Well the language design of Go is outdated even by 80s standards. It is created so that the underqualified people with poor cs background could write something useful without being too much surprised by a real modern language which would look quite different from C, python or java
Don't you know that every corporation has to have their own language? (Which is usually some copy-paste of Java with slightly modified syntax, and quite often runs on the JVM underneath)
OH MY GOD FINALLY someone is putting words to the anguish I've been feeling for years while my colleagues say things like "stop fixing things that aren't broke" or "80/20 rule" and other assorted bullshit. I knew intuitively this is bad, that code should not be done badly, and that there will be consequences. But also that the consequences are sufficiently far down the line that everyday shortsighted engineers won't recognize them. Because we got deadlines, bois! And that's all that matters! *insane traumatized cackling*
Fun until its not anymore, when you have a large project, with 1000s of functions that could be 5 times less. What he is doing he is just pushing complexity from longer code blocks to searching around in the function tree. And the referenced functions will not be nicely on the same page as in his examples.
For sure he's being idealistic. Real code can be written well, but expecting all functions to be less than 6 lines of code makes for a not very useful program.
Fun to see different "authorities" in this anarchic profession stand on a stage and expunge, in total confidence, diametrically opposite advice. Uncle Bob is clearly a big OOP fan. As a programmer in my mid-fourties, I tend to agree with most of the do-s and don't-s he presents here. But it is pretty easy to find functional programming gurus, or even just plain old structural programming proponents, offering the opposite advice in almost every respect. Neither side is very good at explaining why their approach is supposedly better, and both sides manage to produce a few plausible code examples that make it seem they're onto something. I think this was a good presentation, Bob is doing a good job. Even so, I honestly don't think he is very convincing. He's really just telling us his opinions. A big exception is the part in the beginning where he points out the *need* for software development to grow up and become more responsible and accountable, but that doesn't mean his ideas for _how_ to accomplish this are any better than competing ideas. And, given how many devs really like this whole idea of us being some kind of rebels, I think there is just about zero hope this will happen. The industry will have to become regulated, and it won't be fun....
Until time this industry is regulated most lectures are going to just that - opinions. The opinions however have different weight. This one is coming from someone who has seen it all.
OOP is slow, at least in C++. It leads to horrendous syntax, and everything becomes a pointer that needs to be dereferenced. On top of that, all things "C++ standard library" handle memory in horrendous way, further adding to the slow-code problem. When writing anything that requires performance, OOP is NOT your friend. C++ syntax is also bad. Java is bad for other reasons, but it at least attempted to make sense.
3 ปีที่แล้ว
I love this man: so wise. The dark side is to consider things work but the force needs to clean this mess before reaching the next stage = When is right !
31:50 hmmm that makes me picture a kitchen where the chef thinks he's done when the meal is ready... he's done when he has cleaned up the mess he made while cooking it.
The claim that software engineers rule the world because the software is everywhere is the same as saying that builders rule the world because there are buildings everywhere. The people who have the most influence on where to put buildings, when to write software etc. rule the world.
except buildings always are buildings, but software is penetrating every field and taking over them one small thing at a time valets will soon cease to exist once your car can part itself, that's one example
a project is a long line of process connected between business idea end to product delivery end. if you mean by people who rule the world is one who have money and want more money, you're correct. but if you mean who responsible for all the after-effects if anything happen, that depends on where they pour the money along the line for what we call it DECISION MAKING
The mantra I've always followed when coding is "The person that follows you and will maintain your code is a homicidal axe murderer, and they know where you live!"
”The majority of the world’s software infrastructure is held together by the equivalent of paperclips, duct tape and chewing gum” -Random guy on reddit
Great talk, I really enjoyed it. But I have to point out two things. First of all, he was a little dissmissive about the lambdas (1:32:00) which I think is a huge feature that Java lacked for a long time. Sure they can be thought of as being isomorphic to classes where captured enviroment maps to the fields and body maps to the body of the known method. But it is a huge ergonomics change, you don't need to write new Function() { Integer run(Integer i) { return i * 5 }, you can simply write i -> i * 5. This reduces clutter and enhances readability which should be the point of clean code, isn't it? Second point is, he claimed, at 1:33:38, that his open function is side-effect free, which is incorrect. It still does have a side effect (an effect that can be observed from outside, which in this case is whatever the proc does, like writing to that file). But he can claim that his function is rather resource-safe which is actually what he is talking about when he mentioned managed side effects (not leaking resources like open files, unreleased semaphores etc.). Also it would be better if he mentioned that he had to use try-finally to be absolutely sure that the resource is released no matter what. At this point he could mention non-compositional nature of try-catch as well and point us in the direction of functional effect systems like cats-effects, ZIO, etc. :)
The specific advice he gives is very OOP-centric. For instance, in functional languages you have case expressions which don't have the same pitfalls of switch statements. And you wouldn't want to (or couldn't) make variables into globals, but you can easily return more than one value as a tuple or a record. Turning everything into classes seems to be encouraging functions to have side effects, but pure functions are always easier to reason about.
If your object exists as a local then it doesn't have side effects when it goes out of scope, just like the rest of the functions locals. Just because it's an object doesn't mean the outtermost function that contains it has side effects. Your pure functions can have side effects too. That's actually where it starts.
A method should change only the state of the owning object, it is not taken as a side-effect since that state is private to the object itself. Things that are easy to reason about are that ones that does one thing well.
@@heraldo623 And then you run into concurrency problems when you working on multi-threading systems. a pure function as mentioned couldn't run into this problem at all. There is a difference between a pure function (a static function with no side effect in oop) and an object with encasplulated state. the object is not clearly pure.
@@RealDieselMeister Yes, in my comment I was not trying to say a method in OOP is pure. Concurrency issues is a programming flaw, it's not inherent to OOP.
As a "straight out of university" to "Senior Architect Wizard Lord & Software Engineer" @ flashy SF hardware startup called "SoftwareIsn'tRealEngineering.com" this talk is Extremely Fucking Useful. Thank you Tio Bob!
at 11:22 "The only valid measurement of code quality is # of WTFs per minute coming out from behind the door of where a code review is taking place.." OMG !!! I will use this phrase going forward for all the code reviews I do! It sums it all up in a beautiful, humorous nugget. For the # of WTFs that have come out of my mouth (in full voice and without the use of an acronym) .... I wish I had come up with this.
16:30 the pedal is mechanically connected to the hydraulics that power the brakes. The computer controls only the assisting elements, not the brakes themselves. The brakes themselves work even with the car turned off, albeit without hydraulic assistance after the first couple presses.
I was tempted to add to my last comment, but I had second thoughts since I wanted to keep my comments short-- my second comment-- this is an excellent lecture.. Bob is well worth watching!!
Also; Swift now has @unknown default for switch statements which will give you warnings when there are cases that you haven't accounted for and let the default only exist as a "this shouldn't happen" case.
0:00 Event Presentation
2:03 Presenter Introduces Uncle Bob
3:41 Uncle Bob Introduction / My Tribe
4:49 How Far is the Sun?
10:52 Introduction to Clean Code
12:21 The current Society works with Software
19:47 Volkswagen case / Introduction to the Ethics of Software Development
24:28 Why are Programmers so slow?
32:13 What is a Clean Code?
40:09 Analyzing some lines of code
43:43 Long code is not Good Code
49:25 Good Code / Refactored Function
52:40 Polite Code / Rules for writing a news paper article
55:25 Shrunk Code / The Rules of Functions
1:00:23 Shrunk Code / Drawing a Function
1:05:36 When and why was Java invented?
1:08:52 Prose Code / Arguments
1:16:13 Avoid Switch Statements / Problems and Evolution of some programming languages
1:26:15 The Uncle Bob's wife message (funny moment)
1:27:22 Output Arguments No Side Effects / Garbage Collection
1:32:21 No Side Effects / Using Lambda
1:34:26 No Side Effects / Command and Query Separation
1:35:30 No Side Effects / Prefer Exceptions to returning error codes
1:37:05 DRI Principle (Don't Repeat Yourself)
1:39:21 Structured Programming / Edsger Dijkstra Vision vs Actual Vision of the programming
DRY*
Save 10 mins of my life
NICE
Ten minutes into, which gives NOTHING
and the rerst is about code without showing the code.
Down voted and reported as spam.
Thank you!!!
Major thanks to the director who knows exactly what we want to see. Not the slide that has the code, rather the speaker drinking a glass of water
I thought that was alcohol. If not, that's a very fancy glass bottle of water.
@@AG-ld6rv No judging Bob. He's had a hard life and had to deal with a lot of sloppy code.
A+ for exceptional sarcasm
There wasn’t a pause button a year ago? 😂
The director is rude
"You are not done when it works, you are done when it's right."
Uncle bob
@@kidmosey Huh..ah...I..I did it intentionally to check if you guys would notice it
@@alsharefee huh? your sentence is suppose to be
"
You are not done when it is works,
You are done when it is right.
"
edit:
Guess you fixed it.
I am not paying you to make it right i am paying you to make it work ASAP
My Boss
This video... is the worst CRAP I have ever seen. They spent ALL the time showing anything but hte code.
Fucking *_amateurs_*
@@AtheistReligionIsCancer you're right there
After 40 years of programming, I experienced all the cases described. I just want to say how great you describe the feeling when reading code. At this level, clean code becomes poetry.
Got a weird combination of determination and goosebumps. Imagine being this good at something, let alone something that is as difficult as programming.
40 years of programing lol Ok, I was Alan Turing boyfriend then.
Having some beer and watching Uncle Bob videos this evening. Better than anything on Netflix.
I have been a programmer in the 80s. In between I worked with databases a big chunk, took on the IoT, Gui, and now getting back to basics again. It was interesting how things changed over time when in the past, we knew there are better ways but there was just not enough 'time' and not enough powerful hardware. Thank you for making this lecture public. I utterly enjoyed it and the nearly 2 hours flew by. I also sent the link to my daughter who is studying computer engineering at the moment.
Thanks a million!
May be you will like our article about Software Architecture, is based in the concepts in this series and more: mutualwelfare.org/organic-architectur-almost-infinite-scalability/
@@BienestarMutuo I am going to look at it. Thank you for sharing.
@@BienestarMutuo Error 500
@@aurelianspodarec2629 Thanks, we were doing server maintenance. The server is working now.
@@BienestarMutuo Thanks :) The font is a bit small :/
I love how he always adds some completely unrelated, but super interesting things from other areas of expertise at the beginning of his presentations.
The concept of a "wormhole" or shortcut through space-time was first proposed by physicist John Wheeler in the 1950s, but it was popularized by the science fiction TV show "Star Trek" in the 1960s. In the show, the characters used a device called a "wormhole" to travel instantaneously to distant parts of the universe. While the existence of wormholes is still theoretical and has not been proven, they have captured the imagination of science fiction writers and readers for decades and continue to be a popular subject in science fiction today.
I agree, but also imagine how it would be if all comments started like that
I like his books but the sun thing was boring
I think that's a way to condition the mind
30:25 - After finally getting some piece of code to work, you're only done with half the job; you should spend roughly the same amount of time cleaning it. No one writes clean code first because it's just too hard to get code to work.
46:12 - Every line of a function should be on the same level of abstraction, and that level should be one below the name of the function.
52:22 - Polite code allows the reader to exit (=stop reading) early.
58:45 - A function does one thing if you cannot meaningfully extract another function from it.
1:32:22 - To make a method pair safe (remove side effect), use a lambda that does all the processing.
1:34:34 - A function that returns void must have a side effect, otherwise there would be no point in calling it. A function that returns a value should have no side effects.
1:36:00 - A function that has a try/catch block should have no other content beside that block. Within the try block, there should only be a single function call (the actual function that throws the exception).
1:13:10 Never pass a boolean to a function! Instead of that, create two differents functions. Maybe you duplicate some code, but you declare your intention with the method name, you remove a conditional and you don't read useless boolean values in the method call!
@@javiermartin9627better : you make the function with the boolean private and you expose functionTrue() and functionFalse().
I see developers are complaining about the presentation length but as an engineer, I really loved the way he framed the talk from the solar system to a java function. of course, what better example than a man who calculated the sun's distance at 250 bc without any modern tools to understand our lack of creativity and patience for shitty code.
I think its more to do with the deadlines they're forced to meet. Aristotle was allowed to work on whatever he wanted for as long as he wanted
Whoever did the screen switching needs to reconsider their profession.
“When someone is drawing something on a screen that you can’t see, definitely keep the camera pointed at them scribbling and miss where they explain what they’re drawing as they draw it.” - Camera Operator
it's software
@@BenjaminMJ Whoever chose the software needs to reconsider their profession
@@BenjaminMJ doubt it
This person might be a Quantum physicist.
loved 31:54 .. " You are not done when it works , you are done when it's right" . I must say he really makes you look at programming with a different lens . Thanks for sharing this
37:00 It is more important to make your code understandable by your peers rather than by the computer.
Someone used too much of the budget on intros
lmao!!!!!!!!
@@PaulG.369 How is that necessary. Go take your sexism somewhere else
@@PaulG.369 but why? why would you say something like that?
@@PaulG.369 Just because you can speak it doesn't mean you should, please don't try and obfuscate your pathetic sexist outbursts under the guise of freedom of speech.
@@adrielbradley6677 I know, right! I hate it when people delete their comments.
The presentation is structured in the same way he described from abstract to detailed, lovely.
I only noticed that about 1 hour 20 minutes in, when I realised: 'hold on. Everything has been _really easy_ to follow so far. I wonder w- oh.'
"You'll have one minute to read this slide" - camera person cuts away immediately and focuses on the audience
OH C'MON!
Didnt even get to see the last slide until he started talking.
It was a dick move by the video producer.
Are You too stupid to stop the video on the frame including the slide?
@@polish_programmer He starts talking about the slide long before its shown
@@stanstanstan You can still remember what he said and stop the screen then :)
Management is the final decision makers. Delivery is the focus in corporates. No sayer's are thrown out.
It's ok I was thrown out. But i am glad to learn the standards and follow the practices. I am learning and practicing the clean code very late at my age of 38, but i am glad I could see the big difference while coding. Thanks uncle bob.
This lecture is filled with pure knowledge of software engineering.
This was not only precious but very helpful to me. I though that breaking long functions would lead to more complicated code. However, having the mindset portrayed in this video, I managed to break my functions into its "do one thing" components, and even managed to eliminate redundant variables. And, not as I initially thought, my code is far more readable and maintainable. If there is a bug, you can quickly go to the function you think it is responsible for it, instead of zooming in into long functions and loose yourself.
Props to this man! He enlightened me, made me see my own mistakes, and substancially made my life easier as a programmer.
same with me today. watched this and redid my homework after I turned it in just to see what I could do.
I'm just 1 point in the lecture and i'm already learning loads. Thanks for the upload!
which sucks when you want details. 50% or more of this is fluff and a waste of time.
So it's been a few years now since I returned to Uncle Bob, and wow... I must say. He inspired me way back when I was no longer a Junior and hoping to ascend into a more senior position. And now I'm finding myself equally nodding and shaking my head at several points he's mentioning. Predicting them or criticising them. He was not the only influence, but he was a pivotal person in putting me down the path of better code, to try things for myself and form my own opinions.
And above all else, I noted just how well he delivered his sessions. He speaks about code, and there's definitely competency there that he builds upon. But his ability to teach, and capture attention, to narrate and inspire or motivate is impeccable. That's the next big challenge - present what you know to juniors and seniors, and do it in a way that leaves them wanting more, not nursing a headache!
Thankfully this is on youtube with the ability to pause, if you feel the need to! But most important is what he says about it. This is not a test, but fantastic inspiration with super helpful observations. Enjoyed it tremendously!
And just like that, Bob's your uncle.
underrated comment
"You are not done when it works, you are done when it's right."
Uncle bob
Roger that, no need for hail Marys, it's the real McCoy.
☻/ This is bob. Copy and paste him so he can take over youtube.
/▌
/\
Joke ;)
Entertaining talk, but you should show the slides he is presenting while he talks instead of showing him or the audience or the presentation from so far away that you can't read it.
"I'll give you 10 seconds to look at the slide." Camera shows the guy filling up his glass instead of the slide.
every slide is displayed in one point or another and then you can pause. EVERY slide
@@kmellos perhaps, but the format choice to not show the slides during the relevant timeframe is, to quote the presenter, RUDE
@@kmellos the slide with file opening function is not displayed when completed.
You were no supposed to understand what he talks about, you were supposed just to realize how cool the lector is, that's enough. And that's pretty much all he writes about, unfortunately, e.g. "now I'll give you simple rules how to write a good code", and then the reader-programmer comes to my team and writes the worst eye-gouging code I've ever seen in my life. Sad but true, no lector or couch can make you a good programmer without you putting a lot of afford yourself. Just like in soccer. And the worst kind of couch is the one which is not asking you to put the effort in.
Unexpectedly this presentation just went all over a bunch of wisdoms my very first tutor told me at university in 2014. Nice.
This man is genius and incredible, I barely watch 1+ h videos on youtube except for this one, it was joyful watching it.
Uncle Bob intro be like A WWE Wrestler Entry
A well deserved one..
Well observed. And just as much self-focused hokum to follow. I really didn't have the patience to be lead so slowly by the nose in this video.
My impressions were rather associated with those old-time TV commercials of some crappy products :J
This man changed my life, forever!!
How
@@asharkhan6714 Taught me how to properly approach code architecture which in turn led to big changes in my career
After his talk I understood that I have to refresh my knowledge and approach
I was trying hard to convince my ex boss to use some good tools and practices in our project, and moving slowly toward using a unified framework, because the current system was nothing but a mess, and he was laughing at me whenever I say that... I left the company after 3 years, now, he can’t hire anyone, because the system became over-complicated and no one can understand what the hell is going on.
Natural consequence. I think you earned your last laugh
Grandee Tio Bob!! Te queremos papá!
Buenardo
I wish the intro was juust a little longer. Like 30 mins.
This is genius. I laughed so hard because i can realte soooo much to this. Im new to my company and spend like 6 months here and experienced all of it already. Sucking out the energy of my team by being new and unexperienced, experiencing the mess of fixing exisiting code vs the speed of building a green field project etc.
"It is more important your peers know how your code works, not the computer."
I'll never forget this statement, just amazing
@@kidmosey Not really. After refactoring, now you can more easily understand the function. If you need to understand a lower level of what's going on, then you go into one of the functions that the first function calls. However, most of the time you don't need to know that stuff in order to understand what you need to know.
His analogy about news articles is apt if you ask me.
It’s that thinking that took pure science and made a nuclear weapon
its actually amazing that this needs to be said.. its common sense
I get what he wants to say with that. But does it make logical sense? When the computer does NOT understand your code you probably can't run it. This is total nonsense. So do I really understand what he wants to say if such a big fallacy or possible misunderstanding is present from the start?
Please ignore, these are my 2 subtleties to over-complicate things:)
Nothing beats the pleasure of writing code for something you truly care for :)
Uncle Bob is great. I have seen other videos on Clean Coders channel. That's the way to go. This presentation has an exceedingly protracted intro that maybe was supposed to engender excitement, but, as I was anxious to get to the talk, I felt impatient through the entire first 4:49.
This was the best introduction to something I've ever seen in my whole life
I think there must be a "Clean Directing" book too. In Clean Directing, camera looks at where you expect it to
I love the hype intro for a coding presentation.
Code snapshots
41:15 page 1 wiki code
42:27 page 2 wiki code
44:04 page 3 wiki code
50:11 Refactored wiki code
41:12 ahh yes. Let’s just keep randomly switching the camera around during this slideshow which means now you have to pause and skip around!
lol yeah.. i was looking at it when they suddenly switched the camera
Yeah. And there comes the stupid software: TH-cam shows up some garbage when you pause the video.
I don't think his advice applies to math based functions. When I have an equation which uses 4 variables, I don't see how I can reduce that to 3 arguments. For embedded systems, I dont even use OOP because it's more complicated than functional programming in that context. This talk is corporate coding advice where everything is written for the lowest common denominator. Everything is driven down to a bazillion very short functions.
this is awesome.
I Know everything he talks about, but my current job leaded me quickly to forget everything about it.
I have to work hard on my motivation, to stay somewhere to not drown in my bad gooey code -.-
Thank you for uploading this !
If your current employment prospect consists of a lot of "I want to develop better code, but the boss won't let me", you should consider applying elsewhere. The tide is *beginning* to turn against companies that don't comprehend the value of code quality, and I think any companies that don't realize this quickly enough are going to be caught in the undertow. I'm not qualified to assess whether this change actually has the momentum I think (and frankly hope) it has, but nonetheless I urge you to consider whether it's worth the inefficiency of beating your head against the wall when there are other companies out there.
Seriously whoever did the editing of this speach/video should rethink his life.
When Uncle Bob shows you code read at ~42 mins in we don't care about looking at the audience/him/different cameras with not much quality.
It's about the bloody code.
PajakTheBlind Thank you!! So annoying they didn’t show the code there
captain here: you can pause the video. flies away...
I believe this was all done live on a video switcher, the person controlling the video switcher has the mind of production, not programming... someone who thinks staying on the same 'shot' for too long is boring for the audience. This person probably didn't consider keeping the code up. To be honest I thought the production quality of this video was superb. They had someone on a camera tracking the speaker for almost 2 hours, they had someone switching camera feeds and adjusting audio. I dont know if you should say they should rethink their life lol.. it was really well done
@@_TMac the thing I mentioned was the only issue for me. The points you made are perfectly reasonable, still the last page of code wasn't really shown until Uncle Bob was reviewing the code.
@Angus MacGyver man, you got me here, like yeah... when I go to the theater I also pause the video, there wasn't a single movie I left unpaused, be it on my couch, or wherever.
This is what happens when you hire your brother-in-law, who is a wedding videographer, to shoot your coding event.
I am glad that they made chapters and put them in here.
Bob`s a legend!!! Whoever was in charge of the screen switching needs to be punished...
"No modern language has a GOTO" - Uncle Bob
Golang would like a word.
Who cares about Golang?
@@umer.on.youtube Google.
Well the language design of Go is outdated even by 80s standards. It is created so that the underqualified people with poor cs background could write something useful without being too much surprised by a real modern language which would look quite different from C, python or java
Don't you know that every corporation has to have their own language? (Which is usually some copy-paste of Java with slightly modified syntax, and quite often runs on the JVM underneath)
great lecture. watched it more than 18 months ago and going back to it every while.
OH MY GOD FINALLY someone is putting words to the anguish I've been feeling for years while my colleagues say things like "stop fixing things that aren't broke" or "80/20 rule" and other assorted bullshit. I knew intuitively this is bad, that code should not be done badly, and that there will be consequences. But also that the consequences are sufficiently far down the line that everyday shortsighted engineers won't recognize them. Because we got deadlines, bois! And that's all that matters! *insane traumatized cackling*
I have never been so humbled and enlightened
I'm actually taking notes like I'm back in college. Very educational.
I wish school didn't make people hate learning :(
It's incredible the way that my code has improved after dividing one function in many other functions.
Fun until its not anymore, when you have a large project, with 1000s of functions that could be 5 times less. What he is doing he is just pushing complexity from longer code blocks to searching around in the function tree. And the referenced functions will not be nicely on the same page as in his examples.
For sure he's being idealistic. Real code can be written well, but expecting all functions to be less than 6 lines of code makes for a not very useful program.
Fun to see different "authorities" in this anarchic profession stand on a stage and expunge, in total confidence, diametrically opposite advice.
Uncle Bob is clearly a big OOP fan. As a programmer in my mid-fourties, I tend to agree with most of the do-s and don't-s he presents here. But it is pretty easy to find functional programming gurus, or even just plain old structural programming proponents, offering the opposite advice in almost every respect.
Neither side is very good at explaining why their approach is supposedly better, and both sides manage to produce a few plausible code examples that make it seem they're onto something.
I think this was a good presentation, Bob is doing a good job. Even so, I honestly don't think he is very convincing. He's really just telling us his opinions. A big exception is the part in the beginning where he points out the *need* for software development to grow up and become more responsible and accountable, but that doesn't mean his ideas for _how_ to accomplish this are any better than competing ideas. And, given how many devs really like this whole idea of us being some kind of rebels, I think there is just about zero hope this will happen. The industry will have to become regulated, and it won't be fun....
Until time this industry is regulated most lectures are going to just that - opinions. The opinions however have different weight. This one is coming from someone who has seen it all.
OOP is slow, at least in C++. It leads to horrendous syntax, and everything becomes a pointer that needs to be dereferenced. On top of that, all things "C++ standard library" handle memory in horrendous way, further adding to the slow-code problem.
When writing anything that requires performance, OOP is NOT your friend.
C++ syntax is also bad.
Java is bad for other reasons, but it at least attempted to make sense.
I love this man: so wise. The dark side is to consider things work but the force needs to clean this mess before reaching the next stage = When is right !
Rest in peace Bram Moolenaar, author of Vim and hero of many developers
The open source software legend left us on August 3 at age 62.
When you read 2 years old code and you ask yourself "Who the fuck wrote this sh... uh that's me!!!"
Uncle Bob: I'm putting some code on the screen, read it now.
Camera operator: lol. no
31:50 hmmm that makes me picture a kitchen where the chef thinks he's done when the meal is ready... he's done when he has cleaned up the mess he made while cooking it.
Which makes me think... What if there were programmers who just clean the dishes? Which would be refactoring cover made by others... 🤔
@@cristianpallares3847 Yes, we need those guys! Someone needs to clean up all that open source code…
Loved him in My Dinner With Andre. Had no idea he was a programmer.
Does sound pretty like him eh
Incon-CEI-vable!
I thought he sounded a bit like Patton Oswalt myself.
The claim that software engineers rule the world because the software is everywhere is the same as saying that builders rule the world because there are buildings everywhere. The people who have the most influence on where to put buildings, when to write software etc. rule the world.
but regardless of who tells you to or when to write the software you write it and have complete control over what it does
Buildings don't made you adapt your entire life to operate them.
Not the same, you need permission and approval to build buildings on a specific lot of real estate. You need zero permission to write a program.
except buildings always are buildings, but software is penetrating every field and taking over them one small thing at a time
valets will soon cease to exist once your car can part itself, that's one example
a project is a long line of process connected between business idea end to product delivery end. if you mean by people who rule the world is one who have money and want more money, you're correct. but if you mean who responsible for all the after-effects if anything happen, that depends on where they pour the money along the line for what we call it DECISION MAKING
My main thought about the first 19 minutes of this is "With great power comes great responsibility"
tough crowd - his jokes were A+
This is such a good presentation put together. Dang
The mantra I've always followed when coding is "The person that follows you and will maintain your code is a homicidal axe murderer, and they know where you live!"
Better to set your git name to something vague and not sign your comments then. There is such a thing as subjectivity in what makes clean code.
This is awesome! Thanks for the tip!
That's something new way to start your presentation. #unique
We never learned if the water was working :(
is it a meme?
Yeah! Ending on such a cliffhanger :/
28 minutes in quote of the day... you add new people to the team, and they suck the life out of the existing ones, so true---
Such a great talk to review a couple of times.
спасибо, очень умный мужик, было полезно!!
Great job of the camera guy switching __out__ of the code when we are supposed to read the code.
Love it when he says it’s ROOOD!
”The majority of the world’s software infrastructure is held together by the equivalent of paperclips, duct tape and chewing gum”
-Random guy on reddit
Wow, thanks a lot, I'm following all article on Medium about Clean Code, and this talks is the true source of all clean code. Thanks for Sharing
Who else is thinking about their code while watching this ? And virtually applying the the fixes you are gonna do 😅
Great talk, I really enjoyed it. But I have to point out two things.
First of all, he was a little dissmissive about the lambdas (1:32:00) which I think is a huge feature that Java lacked for a long time. Sure they can be thought of as being isomorphic to classes where captured enviroment maps to the fields and body maps to the body of the known method. But it is a huge ergonomics change, you don't need to write new Function() { Integer run(Integer i) { return i * 5 }, you can simply write i -> i * 5. This reduces clutter and enhances readability which should be the point of clean code, isn't it?
Second point is, he claimed, at 1:33:38, that his open function is side-effect free, which is incorrect. It still does have a side effect (an effect that can be observed from outside, which in this case is whatever the proc does, like writing to that file). But he can claim that his function is rather resource-safe which is actually what he is talking about when he mentioned managed side effects (not leaking resources like open files, unreleased semaphores etc.). Also it would be better if he mentioned that he had to use try-finally to be absolutely sure that the resource is released no matter what. At this point he could mention non-compositional nature of try-catch as well and point us in the direction of functional effect systems like cats-effects, ZIO, etc. :)
I'm so glad I don't work with you
30:42 this is SO true - and I'm guilty of it!
In my town people say: "dress me slowly I'm in a hurry"
that's not your town... that's napoleon
just like that, Bob is my uncle ❤
This talk is a treasure!
Great storyteller! Though I initially thought he was just long winded it turns out he really gets the point across in a memorable way.
Thank you!
The specific advice he gives is very OOP-centric.
For instance, in functional languages you have case expressions which don't have the same pitfalls of switch statements. And you wouldn't want to (or couldn't) make variables into globals, but you can easily return more than one value as a tuple or a record.
Turning everything into classes seems to be encouraging functions to have side effects, but pure functions are always easier to reason about.
If your object exists as a local then it doesn't have side effects when it goes out of scope, just like the rest of the functions locals. Just because it's an object doesn't mean the outtermost function that contains it has side effects. Your pure functions can have side effects too. That's actually where it starts.
@@puddlejumper3259 by definition, pure functions don't have side effects.
A method should change only the state of the owning object, it is not taken as a side-effect since that state is private to the object itself. Things that are easy to reason about are that ones that does one thing well.
@@heraldo623 And then you run into concurrency problems when you working on multi-threading systems. a pure function as mentioned couldn't run into this problem at all. There is a difference between a pure function (a static function with no side effect in oop) and an object with encasplulated state. the object is not clearly pure.
@@RealDieselMeister Yes, in my comment I was not trying to say a method in OOP is pure. Concurrency issues is a programming flaw, it's not inherent to OOP.
As a "straight out of university" to "Senior Architect Wizard Lord & Software Engineer" @ flashy SF hardware startup called "SoftwareIsn'tRealEngineering.com" this talk is Extremely Fucking Useful.
Thank you Tio Bob!
This video could've been perfect if the editor just showed the screen when uncle Rob was talking about code...
Fora BOZÓ
O Brasil voltou à FOME
Watching this in December 2020. Hope to be a better programmer in 2021😉😉
This camera work is killing my vibe man
at 11:22 "The only valid measurement of code quality is # of WTFs per minute coming out from behind the door of where a code review is taking place.." OMG !!! I will use this phrase going forward for all the code reviews I do! It sums it all up in a beautiful, humorous nugget. For the # of WTFs that have come out of my mouth (in full voice and without the use of an acronym) .... I wish I had come up with this.
16:30 the pedal is mechanically connected to the hydraulics that power the brakes. The computer controls only the assisting elements, not the brakes themselves. The brakes themselves work even with the car turned off, albeit without hydraulic assistance after the first couple presses.
I think it's about ABS.
Was thinking the same, some cars, especially electric ones, implement brake-by-wire but all road legal models will have mechanical failovers
All the dislikes are from people who write pyramids larger than those found in Egypt.
Sometimes, the 1.25 TH-cam speed is a godsend.
Sometimes 1.75 also works great
I also had mine on that speed :)
I set it to 2x, fortunately I had already heard the worthwhile stuff before, so I didn't need to do a double take.
True but some people really need that slow pace lol no offense to anyone it's good for beginners
1.5 is also good
I was tempted to add to my last comment, but I had second thoughts since I wanted to keep my comments short-- my second comment-- this is an excellent lecture.. Bob is well worth watching!!
Very nice video. Except for the fact that you are filming him when he is drawing, instead of the screen.
I wish I can like this video multiple times! This is great!!!🥰🥰😘😘
1:07:12 " The best way to sell hardware was to win the hearts and minds of programmers first." That's true!
This is the sexiest opening of a code talk I have ever seen.
The intro wasn't long enough lol.
Also; Swift now has @unknown default for switch statements which will give you warnings when there are cases that you haven't accounted for and let the default only exist as a "this shouldn't happen" case.
We don’t rule the world. We are creative people but we write the business told by business owners.
Oooh I see multiple parts to this talk. Ahh I'm so grateful uncle Bob will be accompanying me to work tomorrow; courtesy of earbuds and discretion.
i'm not even a programmer, but i watched the entire thing.
Now you can become one :)
I just love how Uncle Bob is always starting out with some science! 😁