Clean Code - Uncle Bob / Lesson 1

↓↓ ENGLISH DESCRIPTION ↓↓
"Coding Better World Together" is a set of master lessons from the famous Uncle Bob (Robert Cecil Martin), where he gives us a broad vision of the importance and future of Software in today's society.
In this first lesson, Uncle Bob demonstrates the need to write a clean code and establishes the bases to achieve it, being these bases of a social and scientific nature. Making it clear that the future of programming is based on an ethical and polite code.
↓↓ DESCRIPCION EN ESPAÑOL ↓↓
"Coding Better World Together" es un conjunto de lecciones magistrales del famoso tío Bob (Robert Cecil Martin), donde nos brinda una visión amplia de la importancia y el futuro del software en la sociedad actual.
En esta primera lección, el tío Bob demuestra la necesidad de escribir un código limpio y establece las bases para lograrlo, siendo estas bases de naturaleza social y científica. Dejando en claro que el futuro de la programación se basa en un código ético y cortés.
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
1:45:32 Science and Correct Software
↓↓ OUR MODEL OF SOCIETY ↓↓
- mutualwelfare.org
↓↓ NUESTRO MODELO DE SOCIEDAD ↓↓
- bienestarmutuo.org
↓↓ OUR CRIPTOCURRENCY FOR MONETARY FREEDOM - NUESTRA CRIPTOMONEDA PARA LA LIBERTAD MONETARIA ↓↓
- unitycoin.net
- PRESENTATION: unitycoin.net/presentation/
↓↓ OUR PAYMENT FRANCHISE - NUESTRA FRANQUICIA DE PAGOS ↓↓
- sbmlibre.com
↓↓ OUR SOCIAL PACT - NUESTRO PACTO SOCIAL ↓↓
- e-nation.org
- PRESENTATION: e-nation.org/presentation/
↓↓ OUR SOCIAL NETWORKS - NUESTRAS REDES SOCIALES↓↓
- Facebook: / unitycoin
- Twitter: / unity_coin

[@unitycoin_original]

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

[@Gregory.Pacheco]

DRY*

[@queensfinezt]

Save 10 mins of my life

[@matinmohebi5466]

NICE

[@chomo54andbabyaisha97]

Ten minutes into, which gives NOTHING and the rerst is about code without showing the code. Down voted and reported as spam.

[@Maybe4433]

Thank you!!!

[@somebodyoncetoldme1704]

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

[@AG-ld6rv]

I thought that was alcohol. If not, that's a very fancy glass bottle of water.

[@Malicos]

@@AG-ld6rv No judging Bob. He's had a hard life and had to deal with a lot of sloppy code.

[@mayeboy518]

A+ for exceptional sarcasm

[@larsonmedia7214]

There wasn’t a pause button a year ago? 😂

[@randomguy-vq4ue]

The director is rude

[@alsharefee]

"You are not done when it works, you are done when it's right." Uncle bob

[@alsharefee]

@@kidmosey Huh..ah...I..I did it intentionally to check if you guys would notice it

[@JayXdbX]

@@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.

[@pperez1224]

I am not paying you to make it right i am paying you to make it work ASAP My Boss

[@muslimsrememberapostacyday556]

This video... is the worst CRAP I have ever seen. They spent ALL the time showing anything but hte code. Fucking *_amateurs_*

[@TimePassedIsTimeWellSpent]

@@muslimsrememberapostacyday556 you're right there

[@shirumi2331]

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).

[@javiermartin9627]

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!

[@MrJcarr1985]

Whoever did the screen switching needs to reconsider their profession.

[@DanielBrownsan]

“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

[@BenjaminMJ]

it's software

[@SaHaRaSquad]

@@BenjaminMJ Whoever chose the software needs to reconsider their profession

[@teratoma.]

@@BenjaminMJ doubt it

[@bfg5244]

This person might be a Quantum physicist.

[@ofershor6481]

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.

[@ImLaminarBro]

Got a weird combination of determination and goosebumps. Imagine being this good at something, let alone something that is as difficult as programming.

[@shpluk]

Someone used too much of the budget on intros

[@engineergirl6869]

lmao!!!!!!!!

[@cuulcars]

@@PaulG.369 How is that necessary. Go take your sexism somewhere else

[@shpluk]

@@PaulG.369 but why? why would you say something like that?

[@SirGibbels]

@@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.

[@verified_tinker1818]

@@adrielbradley6677 I know, right! I hate it when people delete their comments.

[@Sunnyside--Up]

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!

[@BienestarMutuo]

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/

[@Sunnyside--Up]

@@BienestarMutuo I am going to look at it. Thank you for sharing.

[@aurelianspodarec2629]

@@BienestarMutuo Error 500

[@BienestarMutuo]

@@aurelianspodarec2629 Thanks, we were doing server maintenance. The server is working now.

[@aurelianspodarec2629]

@@BienestarMutuo Thanks :) The font is a bit small :/

[@MAURICAFonenantsoa]

37:00 It is more important to make your code understandable by your peers rather than by the computer.

[@sky-xk5be]

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.

[@Leto_0]

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

[@ViktorEngelmann]

I love how he always adds some completely unrelated, but super interesting things from other areas of expertise at the beginning of his presentations.

[@IvanSkodje]

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.

[@IvanSkodje]

I agree, but also imagine how it would be if all comments started like that

[@TheRafark]

I like his books but the sun thing was boring

[@vimux]

I think that's a way to condition the mind

[@benvella1728]

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!

[@Taronites]

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!

[@Nick-db1zp]

Having some beer and watching Uncle Bob videos this evening. Better than anything on Netflix.

[@bernoulli9047]

"You'll have one minute to read this slide" - camera person cuts away immediately and focuses on the audience OH C'MON!

[@stanstanstan]

Didnt even get to see the last slide until he started talking.

[@SBDavin]

It was a dick move by the video producer.

[@polish_programmer]

Are You too stupid to stop the video on the frame including the slide?

[@stanstanstan]

@@polish_programmer He starts talking about the slide long before its shown

[@polish_programmer]

@@stanstanstan You can still remember what he said and stop the screen then :)

[@mirageman2]

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.

[@DrewCocker]

"I'll give you 10 seconds to look at the slide." Camera shows the guy filling up his glass instead of the slide.

[@kmellos]

every slide is displayed in one point or another and then you can pause. EVERY slide

[@vsams14]

@@kmellos perhaps, but the format choice to not show the slides during the relevant timeframe is, to quote the presenter, RUDE

[@MATHURIN92]

@@kmellos the slide with file opening function is not displayed when completed.

[@pavelkostyuchenko3746]

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.

[@pugilistking5606]

"It is more important your peers know how your code works, not the computer."

[@CosasCotidianas]

I'll never forget this statement, just amazing

[@nailbomb420]

@@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.

[@cedricvillani8502]

It’s that thinking that took pure science and made a nuclear weapon

[@hughesd22]

@@kidmosey You entirely missed the point of what he was saying. By abstracting the code into functions, and naming those functions well, your code becomes self documenting. It becomes obvious what it does by the variable and method names instead of getting bogged down in the implementation. Instead of a bunch of loops and conditional checks, you have something that reads like a sentence. Prose. Not only that, but by having your code broken into separate modules, each module becomes easier to debug/refactor/change.

[@tangrila4971]

its actually amazing that this needs to be said.. its common sense

[@TheJP100]

Unexpectedly this presentation just went all over a bunch of wisdoms my very first tutor told me at university in 2014. Nice.

[@my_j.a.r.v.i.s.]

Uncle Bob intro be like A WWE Wrestler Entry

[@rahul-thakare]

A well deserved one..

[@TimePassedIsTimeWellSpent]

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.

[@bonbonpony]

My impressions were rather associated with those old-time TV commercials of some crappy products :J

[@ahmadmayahi]

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.

[@Twisted_Code]

Natural consequence. I think you earned your last laugh

[@AlexandrosFotiadis]

The presentation is structured in the same way he described from abstract to detailed, lovely.

[@ME0WMERE]

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.'

[@father_mihai]

I'm just 1 point in the lecture and i'm already learning loads. Thanks for the upload!

[@heinzerbrew]

which sucks when you want details. 50% or more of this is fluff and a waste of time.

[@odewoleabdul-jemeel8859]

This lecture is filled with pure knowledge of software engineering.

[@Whiskey_Actual]

And just like that, Bob's your uncle.

[@mayrw1]

underrated comment

[@williamlong4112]

"You are not done when it works, you are done when it's right." Uncle bob

[@Rob81k]

Roger that, no need for hail Marys, it's the real McCoy.

[@cybernaab]

☻/ This is bob. Copy and paste him so he can take over youtube. /▌ /\ Joke ;)

[@mydemon]

I wish the intro was juust a little longer. Like 30 mins.

[@yuvarajvelmuruganmudaliyar]

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.

[@ohwenphakade9207]

well said, experienced the same thing on my last job. where I was required to integrate new features for a app that was developed by a team who were no longer part of the company anymore. worst thing is, it was not build according according standard. it took me ages to build a payment gateway

[@RemiOdufuye]

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

[@PajakTheBlind]

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.

[@robdandy9324]

PajakTheBlind Thank you!! So annoying they didn’t show the code there

[@macgyver2k11]

captain here: you can pause the video. flies away...

[@_TMac]

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

[@PajakTheBlind]

@@_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.

[@DanielBrownsan]

This is what happens when you hire your brother-in-law, who is a wedding videographer, to shoot your coding event.

[@bloguetronica]

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.

[@riveralonzo]

same with me today. watched this and redid my homework after I turned it in just to see what I could do.

[@khalidelgazzar]

great lecture. watched it more than 18 months ago and going back to it every while.

[@antonnym214]

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.

[@shashanksharma8254]

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

[@markamber1480]

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!

[@SidharthShambu]

lol yeah.. i was looking at it when they suddenly switched the camera

[@zoltanboros8963]

Yeah. And there comes the stupid software: KZbin shows up some garbage when you pause the video.

[@dojohansen123]

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....

[@jomt5614]

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.

[@alex_chugaev]

After his talk I understood that I have to refresh my knowledge and approach

[@casperes0912]

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.

[@antonomaseapophasis5142]

1:15:24 A double take is when you see something, and take it in as a normal perception; then an awareness of something in that perception causes you to look again (in surprise) to retake your perception. The idea is that there is a disparity between expected and actual perception.

[@Minotauro_di_Chieti]

This man changed my life, forever!!

[@asharkhan6714]

How

[@lhaugh]

@@asharkhan6714 Taught me how to properly approach code architecture which in turn led to big changes in my career

[@ahmadmayahi]

This man is genius and incredible, I barely watch 1+ h videos on youtube except for this one, it was joyful watching it.

[@davidbhaskara6880]

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

[@bundlesofun9568]

I have never been so humbled and enlightened

[@steffenderfreak1]

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 !

[@Twisted_Code]

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.

[@ceyceycey21]

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. :)

[@xX_dash_Xx]

I'm so glad I don't work with you

[@adennis200]

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.

[@aedd3307]

I am glad that they made chapters and put them in here.

[@TJ-hs1qm]

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.

[@tedvangageldonk7698]

Such a great talk to review a couple of times.

[@ahmedel-hindawi9226]

This was the best introduction to something I've ever seen in my whole life

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 !

[@localhost0]

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.

[@inuke4fun832]

but regardless of who tells you to or when to write the software you write it and have complete control over what it does

[@marciusaraujo6940]

Buildings don't made you adapt your entire life to operate them.

[@Andrews27]

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.

[@gamemusicmeltingpot2192]

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

[@thorandlundeve]

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

[@srinivasanrajagopal9062]

Thanks a ton for this

[@JerreMuesli]

Drawing a function part is gold. Even for Sr. developers

[@poprockssuck87]

In the future for anything substantial (e.g., life threatening or over a certain monetary threshold), there will be national software regulations and inspectors, just like with every other engineering field. How we've gotten this far without them is beyond me.

[@lucasl.treffenstadt4688]

Is the water working, though? I need to know!

[@lmlizwpfhsjmcyt7545]

"No modern language has a GOTO" - Uncle Bob Golang would like a word.

[@umer.on.youtube]

Who cares about Golang?

[@lmlizwpfhsjmcyt7545]

@@umer.on.youtube Google.

[@flyingsayon]

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

[@bonbonpony]

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)

[@pacesferry]

A function should do one thing, 'like creating a tree', and other great pointers. Love the perspectives! Thank you!

[@tracyn4662]

NOTES -- (What is clean code and how does it look like?) INTRODUCTION * Software is everywhere and so much of society depends on it. That's why it's important to have ethics and standards in software. Eventually our jobs would be regulated/legislated illogically if we make mistakes due to negligence, that's we should get ahead and decide, as software developers, what's the standard. Legislators and politicians would instead look at what we've already invented and turn that into law. It happened with doctors, with engineers, with lawyers, with architects, etc. * One thing we all value is clean code * Implementation Patterns by Kent Beck (Book) "Good code matters" * Look into who Kent Beck is * Why do programmers go so slow? Because we make a mess because we want to go fast because they expect us to meet a deadline * Usually our code isn't clean when building our app but when we get it working, we clean it up. The time it took to build it should be the time you spend to clean it up * "The only to go fast is to go well", "Twice as fast, twice as well" * "Clean code is simple and direct... clean code reads like well-written prose" - Grady Brooch * "Clean code looks like it was written by someone who cares" - Michael Feathers * The important part of your job is to write code that can be understood by others * "Clean code is when each routine is pretty much what you expected" - Ward Cunningham (No surprises, no wtfs lol) PRACTICES/CONCEPTS * Every line of a function should be the same level of abstraction (One below the name) (eg. derived object vs int) * Functions should hardly be 20 lines long, let alone 100 * Should read like an article. Start with a headline then an abstract/synopsis and get more specific with each paragraph (Be polite to the reader and allow them to exit early when they're no longer interested) * If you can meaningfully abstract one thing from a function, then your function does more than one thing * Soft rule: Keep function parameters to 2-3 * Almost never pass in booleans as an argument * Avoid switch statements. If you add another class, you'll have to go to every switch statement (Dependency magnet). Instead create base classes and derive it. Have all the relevant functions belong to that class * Open-close principle: Module should be open for extension but closed for modification * Side-effect: Causing a change to the system (eg. new keyword, leaving a file open). Side-effect functions come in pairs * Command & Query Separation: When a function is a command and returns nothings, it should have a side-effect. Queries return a value and should have no side-effects * Exceptions > error codes * Don't Repeat Yourself (DRY) * Treat software like mathematics not science. It can be proven

[@pt8306]

We never learned if the water was working :(

[@me2beats313]

is it a meme?

[@magdalenaerliksson9274]

Yeah! Ending on such a cliffhanger :/

[@amarissimus29]

Loved him in My Dinner With Andre. Had no idea he was a programmer.

[@Newtube_Channel]

Speaks the gospel truth

[@ed6393]

Does sound pretty like him eh

[@LARathbone]

Incon-CEI-vable! I thought he sounded a bit like Patton Oswalt myself.

[@badjoke5130]

Nothing beats the pleasure of writing code for something you truly care for :)

[@willd0g]

He’s a great orator and easily understood even at 1.5x speed - ROOODE!

[@WorldView22]

Aristarchus of Samos (Αρίσταρχος ο Σάμιος c.310 - c.230 BC) not only caclulated the sun-to-earth disance but, most importantly, was the first to formulate a sun-centered theory, not Copernicus.

[@yeetthyannoyingchild2346]

Indians did that 28,000 years ago.

[@Leto_0]

@@yeetthyannoyingchild2346 Can you back that claim up with some sources? This is all I could find on the subject: "Ancient India's contributions in the field of astronomy are well known and well documented. The earliest references to astronomy are found in the Rig Veda, which are dated 2000 BC."

[@SumoCumLoudly]

And its still a theory after all this time, wonder if it will ever be proven, not likely

[@firebladex8586]

30:42 this is SO true - and I'm guilty of it!

[@saidtorres3]

It's incredible the way that my code has improved after dividing one function in many other functions.

[@vast634]

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.

[@tonyblack1981]

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.

[@orparga140]

In my town people say: "dress me slowly I'm in a hurry"

[@tickoschannel]

that's not your town... that's napoleon

[@hannesjvv]

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*

[@trinhngo2204]

Thank Uncle, I learn one more key point, that is about estimation on a `done task`. Thats great!

[@goehlergamedev]

I just love how Uncle Bob is always starting out with some science! 😁

[@emilianoborselli9787]

When you read 2 years old code and you ask yourself "Who the fuck wrote this sh... uh that's me!!!"

[@Anythingforfreedom]

Great storyteller! Though I initially thought he was just long winded it turns out he really gets the point across in a memorable way.

[@karanbhatt9320]

1:15:00 this is main issue with Pass By Reference. When we pass array and do modifications it does in main array and that main array is now out of state.

[@PabloGnesutta]

It would be really nice if the video showed the code the whole time Bob showed it to the audience to understand it. Much better than seeing the audience itself. Anyways, great material. Thank you

[@Potts1966]

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!"

[@nextlifeonearth]

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.

[@MrDoboz]

This is awesome! Thanks for the tip!

[@GeorgeTsiros]

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.

[@user-tc1cx2zs7k]

I think it's about ABS.

[@ShortFilmVD]

Was thinking the same, some cars, especially electric ones, implement brake-by-wire but all road legal models will have mechanical failovers

[@PennyAfNorberg]

In a collage exam where i was supposed to prove the existence of sequence of binary words suck that each neighboring elements differ in just one letter for every word size. I did so by writing a lisp program , in paper, that would generate the next sequence. Then I proved that it did that and used induction.

[@rahulmathew8713]

if you have a try catch in a return function then the return variable must be declared outside try catch else its unreachable code. so there is a line before and after try catch unless its a void function

[@micknamens8659]

Just place the return statement inside the try block.

[@harikrista]

We don’t rule the world. We are creative people but we write the business told by business owners.

[@ErdoganKurtur]

I think there must be a "Clean Directing" book too. In Clean Directing, camera looks at where you expect it to

[@GameFuMaster]

1:11:54 personally, I only do 2, and I split that between required arguments (first) and optional (second). If there are multiple required arguments, then it's simply an object that needs to be passed in. Of course, if it's just one argument which is optional, then it'll just be one argument (maybe with a default)

[@willemvdk4886]

This talk is a treasure!

[@BenRangel]

1:12:54 it’s not hard to see what a bool does as a function argument! Just peek at the function definition - if you have a proper name for the bool it should be clear as daylight! Having 2 separate functions instead of a bool can lead to convoluted naming as you need both DoStuffWithX and DoStuffWithoutX instead of just DoStuff(bool x). Also consider that you can use default parameters in many languages.

[@patmelsen]

It's kind of hard to tell what a function does when you call it like ```create_customer_invoice(true, true, true)```. Forcing you to peek at the definition is wrong. Better patterns are Python, Ruby or Objective-C named parameters, like `create_customer_invoice(draft=true, a4size=true, otherparam=true)` or using something like the builder pattern in Rust: `CustomerInvoice::new().as_draft(true).pagesize(PageSize::A4).with_other(OtherParam::new()).create()`. Also, usually only `CONSTANTS` and `ClassNames` are uppercased, functions and methods should be lowercased, so you can visually distinguish them.

[@BenRangel]

@@patmelsen Oh I 100% agree named params is the way to go

[@Rob81k]

I'm actually taking notes like I'm back in college. Very educational.

[@Tubeytime]

I wish school didn't make people hate learning :(

[@QAYWSXEDCCXYDSAEWQ]

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!!

[@zehahaha2899]

Uncle -God- Bob Martin is amazing...

[@ViktorEngelmann]

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.

[@cristianpallares3847]

Which makes me think... What if there were programmers who just clean the dishes? Which would be refactoring cover made by others... 🤔

[@bonbonpony]

@@cristianpallares3847 Yes, we need those guys! Someone needs to clean up all that open source code…

[@sheksbear]

Who else is thinking about their code while watching this ? And virtually applying the the fixes you are gonna do 😅

[@elkeospert9188]

01:16 "Avoid Switch-Statements" The argument that in case a new shape is added and you have to modifiy all switch statements is of course true - but the argument that you might overseen one of them depends on the programming languages. In many languages the compiler could detect swith statements which are not covering all possible options (as long as you not define a default/else rule to handle exactly such cases) - so it is easy to avoid this possible error source. So it is "only" more work as you have to extend all you switch statements when a new share is introduced but on the other side it makes the code easier to read as you can see everythere when something with a shape is done what types of shapes are really possible in that version of the software. And maybe when it comes to rotate a shape an object orientated approach would implemented a "dummy" rotate method for the class CircleShape as nothing changes when a Circle rotates. But know think aboubt the user does a right click on a shape and you want to show a local popup menu showing him the different actions he can do with that shape. If you forget at this moment that there are circle shapes (or circle shapes were implemented after you programmed the code for this popup menu) it will ends that the popup menu will offer the action "rotate" evene when the selected shape is a circle for which rotate does not make sense. If you instead have implemented this by a switch statement it is much more probably that you would not make this mistake when you are defining the actions for the popup menu if the switch statement part which is responsible for the case the selected object is a circle.

[@lepidoptera9337]

There are very good uses for switch statements. I use them all the time because much of my code control flow are state machines. These can be made correct by design but they are, of course, a very restrictive strategy.

[@patmelsen]

I write primarily Rust at work, and we make good use to switch statements -- the compiler will not compile something unless you have covered all possible cases. So when you add a new variant to an enum, you cannot forget to handle it. But obviously, Java does not have something like that (another reason why I dislike it).

[@analuiza2677]

My main thought about the first 19 minutes of this is "With great power comes great responsibility"

[@marianoms4846]

This video could've been perfect if the editor just showed the screen when uncle Rob was talking about code...

[@ciroheadbanger2008]

Fora BOZÓ O Brasil voltou à FOME

[@fatihhamza3259]

just like that, Bob is my uncle ❤

[@NikolayMishin]

спасибо, очень умный мужик, было полезно!!

[@Chemaclass]

This is simply amazing. Thanks.

[@pbamma]

This was SUPER-close to a working irony. Cue hard guitar... Now jeans. The presentation did not need the guitar intro... though it might be fun for something else.

[@Anthonyngoploti]

1:07:12 " The best way to sell hardware was to win the hearts and minds of programmers first." That's true!

[@devjuninho]

Vou legendar esse vídeo, não consigo acreditar que até hoje não o fizeram.

[@OMGicantwayyyyyyyyyy]

Goto is probably considered evil for this kind of web/desktop application software but it's very useful in embedded and low-level (i.e., kernel) code to deal with resource deallocation in error conditions. It's the preferred method for doing so within the Linux kernel.

[@dane2565]

This camera work is killing my vibe man

[@jacquesdemolay2699]

Yes ! I do care how far is the Sun -- for I have never excluded the possibility of my visiting it in a near future. Now, I do prefer 8 light-minutes because it sounds less than 8 heavy-minutes, right? forget kilometres, they are off-putting. it makes a difference psychologically.