Bob Martin SOLID Principles of Object Oriented and Agile Design

Channel:People career · Length:1:23:35 · Published:2015-05-24 · Views:516918

Watch on YouTube

Summary

Robert C. Martin (Uncle Bob) gives a talk on the SOLID principles of object-oriented and agile design, in the context of encapsulation and clean code.

Why HN recommends it

Cited in discussions of OO design, access modifiers and private fields, and why writing messy code slows you down.

there's an interesting talk from Uncle Bob saying exactly that — HN, 2017

Software architecture & design · Software practice, open source & careers

Subtitles (excerpt)

good evening my name is Kyle Jensen I'm on the faculty here at the El School of Management and I'm also the director of entrepreneurial programs here uh our uh guest tonight is Robert Martin uh who's going to talk about solid principles of object-oriented and agile design and we are very lucky to have him here uh it comes at a he's here at a great time for Yale um as you may know the university is investing a great deal and Entrepreneurship and that is creating I think um or mixing with the University's traditional uh expertise in let's say computer science and the theory side and producing all sorts of great things on campus so for example uh two years ago Yi started the tech boot camp and hackel started uh a year ago y hack brought together a thousand developers from around the country for a two-day hackathon uh this semester uh Daniel body changed the introduction to programming course here which is the kind of core program course for non- Majors to be um mobile application development and Daniel and I are teaching together next year uh in the spring computer science 113 which is entrepreneurship and programming and we have a course on management of software development here at the El School of Management so

On Hacker News

Do they care if a year down the road your maintenance costs increase fivefold? Have they seen the analysis which shows that initial development cost just makes a small fraction of the total cost and that fraction get smaller the longer software is in use? Do they care if a year down the road your TTM times increase tenfold? We know that the bad code slows us down. Why do we write it? Why do we wr… — rimliu, 2017-12
The keywords were reserved in the latest spec for just this purpose. I don't think the rationale for their inclusion is a good one. The inclusion of such keywords in languages like C++, Java, etc was well-meaning but a mistake in retrospect. In the presence of global variables and direct assignment these keywords are the PHB approach to information hiding. They require ceremony and diligence to a… — agentultra, 2017-08
> Except that languages which try to provide facilities for this principle have bolted it on in the wrong way and we as an industry have come to accept some other feature ("public/final/private" keyword languages) to mean we have, "encapsulation," in our language. Actually, there's an interesting talk from Uncle Bob saying exactly that: [VIDEO] The idea is that public/private/protected is an atte… — Ace17, 2017-06

Related videos