The S.O.L.I.D. Principles of OO & Agile Design

The S.O.L.I.D. Principles of OO & Agile Design - Uncle Bob Martin

9 років тому

No copies of this video may be made and shared. This video belongs to David Schinkel.
READ FIRST:
This video is more valuable that just "another SOLID talk".
This talk is still very entertaining and informative so sit back, relax, and enjoy! Sometimes it's good for us to learn and understand the past, so that we do not make the same mistakes that have been made over and over again in this profession.
If you want a more in-depth training on it, UB has that on his CleanCoders.com site. Very good vids there...very in depth on coding techniques and he codes a lot there.
www.CleanCoders.com - ton of vids by UB, very in depth technically
www.WeDoTDD.com/interviews/com...
/ unclebobmartin
blog.cleancoder.com
blog.8thlight.com/uncle-bob/a...
Source:
This presentation was given by Uncle Bob on Feb 4, 2015 at the Arlington Lakes Golf Club in Arlington Heights, IL.
Schaumburg Microsoft .NET Technologies Meetup bit.ly/1hAO2ln
Be sure to change the video to 1080p when watching it
Recorded with my IPhone 6+ 1080p (60fps)
Side Note:
UB talks little about SR and DI toward the end, but it's more a talk around business and more top level tech talk around around decoupling code and history of coding (where the idea of decoupling stemmed from, how objects came into existence and why, and how programming languages were affected by it ended up providing polymorphism... and a lot of other interesting things around the importance of plug-in software....all indirectly related to the topic of SOLID itself as a whole.
The S.O.L.I.D. Principles of OO and Agile Design
What happens to software? Why does is rot over time? How does an Agile Development team prevent this rot, and prevent good designs from becoming legacy code? How can we be sure our designs are good in the first place? This talk presents the agile S.O.L.I.D. principles for designing object oriented class structures. These principles govern the structure and inter dependencies between classes in large object oriented systems.
The principles include: The Open Closed Principle, The Liskov Substitution Principle, and the Dependency Inversion Principle, among others.
About "Uncle Bob" Martin:
Robert C. Martin has been a software professional since 1970. In the last 35 years, he has worked in various capacities on literally hundreds of software projects. He has authored "landmark" books on Agile Programming, Extreme Programming, UML, Object-Oriented Programming, and C++ Programming. He has published dozens of articles in various trade journals. Today, He is one of the software industry's leading authorities on Agile software development and is a regular speaker at international conferences and trade shows. He is a former editor of the C++ Report and currently writes a monthly Craftsman column for Software Development magazine. software craftsmanship

КОМЕНТАРІ: 86

@tddtv Рік тому

Hey All: I just started TDD TV. TDD Practitioners apply SOLID principles and all sorts of other practices like Clean Code, etc when we practice TDD. SUBSCRIBE & hit the BELL to Learn! Many videos to come! (Also check out WeDoTDD.com!) 👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺👾📺

@camelcase9225 5 років тому

Before the talk starts: "Ok what crazy tangent is he going to start with this time?" Talk starts: "WHY DO WE HAVE A MOON?" Not disappointed lmao

@hasan0770816268 2 роки тому

notes to self: 29:00 polymorphism is why OO is so successful 47:00 a DLL is not a logical grouping of classes but a grouping of classes that you want loaded at runtime 49:00 single responsibility means design the class so it has a single reason to change or, to put it in another way, gather the things that change for the same reasons and separate the things that change for different reasons 56:00 the database exists to make accessing data from a disk easier for us, disks are disappearing and in the future we will have virtually infinite amount of persistent ram 59:00 open-closed: being able to change what the class does without changing its source code (you write new code but don't touch old code)

@znacly1184 Рік тому

Most I’ve learned from a single UKposts video in a very long time! Thank you for posting this lecture!

@GrindThisGame 5 років тому

I could listen to him for hours.

@Nick-db1zp 2 роки тому

I have been, and I can tell you, it is worth it

@morantNO1 2 роки тому

All talks of him I find on youtube are roughly the same though :(

@pastafarian3758 2 роки тому

I do same

@devofshane4399 7 років тому

Gotta love Bob's little tangents he has before he starts his talks. It is really effective at getting the listener's engaged in the talk.

@honkderhase8724 2 роки тому

So cool to hear him talking about the "old" days and how thing were actually implemented... I started with C and C++ and still remember lots of this stuff.

@ismailm123 6 років тому

I did clean code course with uncle bob and the tangent talks at start of each topic kept you focused also they were really interesting stories

@GK-rl5du 8 років тому

Thanks for the upload, a really fascinating talk.

@stevehyles743 8 років тому

A fascinating overview of the history of programming languages. After 50 mins two SOLID principals are introduced SRP and OCP but only surface deep.

@roeelcohen 4 роки тому

I haven't seen 1 lecture of him explaining the whole 5 principles

@Paretozen 8 років тому

What a fun and engaging speaker! Thanks.

@Gunth0r 6 років тому

I'm starting to get why they call him "Uncle Bob". It's the crazy stories that make you think about the other more serious stuff he's saying. He oscillates wildly between foolishness and wisdom, which is the sign of a true teacher.

@ottorask7676 4 роки тому

I thought the name came from a co-worker who liked giving odd names to their colleagues.

@jodypipowski2376 2 роки тому

To me he is the Stephen King of code. Always on the edge of your seat.

@somebodyoncetoldme1704 Рік тому

And the sign of a true uncle.

@TheRaspPie 8 років тому

Wonderful insight into the history of OOP and what's it's really about. In fact, OO can be just an extension to some functional language or procedural one.. it has nothing to do with mutability or state at all.

@dannyknowlton 2 роки тому

Uncle Bob is a national treasure.

@notdrone 7 років тому

starts at 3:23

@dashenno 6 років тому

Anecdote ends at 8:14

@binaryum 5 років тому

doing god's work

@MartinJungblut 7 років тому

9:30 "We used to call it C++ for dummies."

@adrianmotasilverio Рік тому

This guy is awesome.

@yonathanhailemelekot5238 2 роки тому

I love this man

@alexandersoltesz8103 5 років тому

this guy is golden

@reyou7 6 років тому

Uncle Bob

@Atharvak1910 7 років тому

So wait how do we fix the class he described in the Single responsibility principle example? Edit : Oh ok he talks about it at 1:05:00

@javiermarchetti1520 8 років тому

This guy is crazy, but I really like his videos

@williamdavidwallace3904 7 років тому

You say that Sun was the first to realize that winning the hearts and minds of programmers. Way back in the 50s and 60s IBM figured it out too and gave universities huge discounts on systems. Unfortunately for IBM they forgot about it.

@pafauk361 2 роки тому

Doesn't PL/SQL have functions local to other functions?

@jay6645 Рік тому

At 20:05, Bob explains C had perfect encapsulation, and explains why C++ does not. He says, in C++, since the new operator needs to know the size of a class's object, it's definition therefore must be in a header file, hence losing encapsulation. My question is: Even in C, wouldn't you need to know the size of the structure you want to malloc?

@miikavihersaari3104 Рік тому

That's a good question! I think he means the paradigm encouraged by C++, instead of what you can do with C++. In C, you'd often have a function that would do the malloc for you, and you'd be responsible for calling the corresponding clean up function once you were done. As long as you'd be operating with a pointer to the struct and pass that to the functions in the header, the compiler would allow you to do that. You can do this in C++ too, but I believe the point Bob is making is about going the C++ way, i.e. using classes and 'new'.

@miikavihersaari3104 Рік тому

57:18 I don't think tables (arrays) are going away any time soon. It's true we don't have spinning disks anymore, but it still is much more efficient to read data that is contiguously laid out. Also, even though we'll have more memory in the future we'll still need to serialize our data. And lastly, computers aren't getting that much faster anymore. All capacities are still finite, and the idea that we don't need to care will (and has) lead to poor performance, and as such, poor software quality. In the end, programming is engineering, and engineering is about the physical reality. I don't think trying to 'escape the hardware' as an underlying principle and goal is a wise way forward. Abstractions aren't like math, because all abstractions are imperfect and each one comes with a complicated price tag. I absolutely agree with Bob on the point he makes about not "trusting" frameworks. The technical relationship is the wrong way around. Most websites have somehow missed this point, but then again web development is very broken.

@TJ-hs1qm 25 днів тому

14:26 Algol: "Algorithmic Language" also a star and Arabic for Daemon (al ghoul)

@guybrushthreepwood2910 Рік тому

Great talk, as usual with Uncle Bob. Too bad he only made it to the "S.O." out of "S.O.L.I.D.".

@nathangrube2374 11 місяців тому

Ha. Yes. I came here specifically hoping for I. and D. since in the previous talked I just watched, he only got through S.O.L. Someone should try to book him for a D.I.L.O.S. talk.

@rakeshmali1727 2 роки тому

at 36:50 what did the guy say?

@toddmullen5765 7 років тому

What IDE does he name at ~ 35:18? I can't make it out & I don't work with C#, NET, or Java.

@toddmullen5765 7 років тому

Many Thanks. 8)

@umer.on.youtube 2 роки тому

Does he have a problem with C# ? Is there some passive-aggression in his tone? Not sure!

@insertoyouroemail 4 роки тому

bob: "any good class couples data and behaviour" me: *triggered in haskell*

@sumertheory 5 років тому

did he mention objective c and jobs?

@comicsans1689 5 років тому

Not in this talk, he mentioned Java and C# instead. In one of his other SOLID talks, he talked about Objective C and Steve Jobs.

@playwtmk 5 років тому

does anyone have a link where he gets past o?

@tddtv 5 років тому

CleanCoders.com

@RobertLeather 9 років тому

I loved this video, but lets be honest... all those wonderful recollections meant we didn't actually cover the subject of the video.

@GireesanNamboothiriP 8 років тому

+Robert Leather I strongly disagree and I think you are missing the main point : AGILE. To design software systems in agile, Uncle Bob always suggests to think in the most loosely coupled ways of structuring the program blocks. Starting with the business logic with no gui and no db, which can be tested in each iteration, you will add your gui and db as dynamically "pluggable" modules. Most funniest-perfect way to tell the programmers that they should think beyond the injected and repeated keywords "inheritance, polymorphism etc and make things loosely coupled.

@GireesanNamboothiriP 8 років тому

+Dave Schinkel Really appreciate your team effort to improve the coding and having such great sessions, which we could watch on-line. I started following Uncle Bob right when I found them from NDC at Vimeo. Since then, kept on watching such videos, then further debates and hangout sessions from David (DHH) , Beck and Martin. Started practicing it throughout my codings, refactoring (using Boy's scout rule) and in an year, the program I wrote became complex; yet well maintainable. I could change my UI from native to web without cascading it to my logic, or change the database without cascading again. First time I really felt; "yeah! I did something good". What I missed is adding unit tests from the beginning; which I am trying to incorporate now. :-) . Problem again is the mindset from the management on spending that 30 seconds extra for unit tests and further the TDD :( Not yet there when marketing guys can just take the latest build and sell it when they want it, but I am striving to.

@Paretozen 8 років тому

+Dave Schinkel Absolutely Dave! I had a lovely day programming thanks to using TDD. All is covered, everything in the green, great tangible process. Now I have to stop working, but I don't want to.. so what better alternative than watching Uncle Bob :) I'll eat bread & water before dealing with fast, messy and untrustworthy code again!

@abdulwahidgul 4 роки тому

8:15 where the actual talk starts

@gmoschwarz 8 років тому

The moon is made of the same material as the earth, except for the iron core of the earth, which comes from another body (the body of the size of Mars), but it couldn't belong to the solar system, because another sun must have produced it, the solar system either captured or it simply collided with earth.

@AdrianPoplavsky 6 років тому

What's the question in 1:08:35 ?

@AdrianPoplavsky 6 років тому

Dave Schinkel thanks! I got the second part of the question which is about dependency injection or inversion. Couldn't catch the first part that was answered with the rect/square example.

@AdrianPoplavsky 6 років тому

Oh, FYI, just got what they are talking about by paying attention to Uncle Bob repeating the question. He says: "Should i touch briefly on LISKOV----- and Dependency Inversion?". Those are the L and the D from SOLID. That's why he talks about the rectangle/square example, and why square cannot inherit from rectangle. Basically the answer is: "both Rectangle and Square should inherit from SHAPE, to comply with the Liskov's substitution principle". A Square IS a Rectangle, and that's Uncle Bob's bait because Square doesn't BEHAVE as a rectangle. en.wikipedia.org/wiki/Liskov_substitution_principle

@Frangles00 8 років тому

Can someone explain joke from 36:50 to not native English speaker please?

@ryanfoothills6059 7 років тому

The comment made by the audience suggests that uninstalling Resharper(Jetbrains) from your Windows(Microsoft) computer is not easy, and that it's a headache(it's difficult and unpleasant) to uninstall.

@zainulabidin5554 7 років тому

I think it implies that if user uninstall re-sharper Microsoft will be in trouble because v. studio won't be that effective without it. So Jetbrains do have a way to damage microsoft

@alejandrohierro8947 4 роки тому

I think he says "have you ever tried to uninstall it?"

@uRamPlus Рік тому

Because it’s sometimes even when you uninstall it, it won’t get completely uninstalled😂

@ehabahmedyassen 2 роки тому

It is the fifth not the 2nd or 3rd.

@MrBct524 8 років тому

Sorry it's my audio device.

@AtanasovPetar 6 років тому

A correction about similarities between Java and C#. While they are similar, some of the similarities are only on the surface. Yes, the syntax is the same but the implementation is different.

@mortenbork6249 2 роки тому

This whole talk is about how to communicate with your code, to OTHER PROGRAMMERS. Your point is literally, that machines read 100101010101010 NOT code. So the point of this talk is -> How to write code a human can understand. And your correction is, to say, what was already said... You weren't paying attention my friend.

@MrMasterKaio 5 років тому

18:36 bob gettin angery

@injSpasov Рік тому

😮

@videofountain 7 років тому

SOLID at ukposts.info/have/v-deo/rGhnqmmFa4WkyYU.htmlm16s

@karanbhatt9320 Рік тому

Uncle Bob entere 3:20

@MrPDTaylor Рік тому

Don't get screwed by your GUI

@BenPearson_kd7uiy 7 років тому

C# is Java done right;-)

@daanbouws1538 6 років тому

Microsoft products are not for programmers

@MrBct524 8 років тому

Three principles are covered nicely, but last two are not.

@_aullik 8 років тому

naresh dhami its always the same, i cannot find a talk about everything

@behnamrasooli8801 8 років тому

+naresh dhami You can go to his own website and watch more videos like this. www.cleancoders.com

@behnamrasooli8801 8 років тому

I watched almost all of them and I highly recommend them. Although the Design Patterns section of it wasn't very helpful but the rest specially SOLID section was fantastic.

@mauriciorossi8477 2 роки тому

He never really covers them because they arent as interesting and as insidious and subtle as the first 3 I feel. You can just read them from his book. For example DIP is simply to use an interface because high level (ie policy) modules shouldn't contain direct references (be dependent) on particular implementation. Its not much more nuanced than that. But the points he covers are way more nuanced.