Skip to content
0:00 / 0:00

#solidprinciples#cleancode#oop

"Uncle" Bob Martin

Program on Entrepreneurship

1.8K subscribers • 1 video on Hallway

YouTube
  • Recommended by 4 people: 2 on Hacker News, 1 in engineering communities and 1 curated list.
  • A classic. People kept recommending it from 2019 to 2024.
  • Presented by Robert C. Martin
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

178K views11 years ago4 recommendations

Software designTools and practiceSoftware architectureDesign patternsObject-oriented design

Robert C. Martin discusses the S.O.L.I.D. principles, clean code, and the true meaning of object-oriented programming.

Software luminary “Uncle Bob” Martin spoke to members of the Yale and New Haven communities at Yale School of Management. Martin had been a professional programmer since 1970; since then he has become a prolific author and leader in the industry. Dan Bernier of New Haven’s Continuity Control and nhv.io, introduced Bob, noting that in the “weird and messy business” of software development, Uncle Bob is there to look out for and guide developers. Martin emphasized the importance of writing clean, efficient, well-written code—sage advise for aspiring programmers and tech-entrepreneurs. Interest in development and programming is on the rise at SOM as student-entrepreneurs explore tech-based startup ideas. Classes like CS112, co-developed by SOM’s Program on Entrepreneurship and the Department of Computer Science, give students curricular opportunities to develop their skills. Student-entrepreneurs are likewise embracing extracurricular opportunities around programming. HackYaleSOM, SOM’s student programming organization, continues to gain members while interest in HackYale, an undergraduate organization offering programming workshops, has reached record highs: one thousand candidates applied for only 80 seats in their “Introduction to Web Development” workshop.

Why it's here

4 people recommend this

What people say. Highly recommended as a formative talk on software architecture, OOP, and the SOLID principles.

Moments people linked to

u/Nuclear_Catapultin r/C_Programming • Recommends

Bob Martin's Thoughts about OO in C
158View on Reddit

mrkeenon Hacker News • Recommends

On “Don't Refactor Like Uncle Bob”

…ds to go where the people are in order to communicate to the most people, but that doesn't mean he doesn't speak out against fads if it's appropriate. This talk was really formative for me: link If I remember correctly, he rails against just sticking the database in the middle of your system and calling that your architecture. If I'm remembering link to this video correctly, he says OOP is no big deal, it's just encapsulation-polymorphism-inheritance, and then goes on to say things like C had better encapsulation than OO languages (you can keep your .c file to yourself, and just give someone the .h to program against.). And c-style bytes with stdin/stdout was designed with perfect forward-compatibili…

programming-talkscurated list on GitHubRecommends

Under “Software Development”

The S.O.L.I.D. Principles of Agile OO Design 01:23:35 by **Robert C. Martin** (way more interesting than it sounds) (2014)

slifinon Hacker News • Recommends

On “Pretending OOP Never Happened”

There's a good talk here from Uncle Bob who helped popularise the solid principles, about what OOP is, and isn't link to this video Towards the end of the talk note of the stickers on his laptop

u/TheLastSockin r/Clojure • Mentions

On “How does one start thinking in Clojure? I am writing a web app and I fall back to a very OO way of thinking.”

It night help to consider what oop really is. Bob talks about it here: link to this video I'm not saying the is the fastest route, but once you get an idea of the concepts history and it's flaws, you can reframe what you were taught, versus what you can do once the limitations are removed.

rimliuon Hacker News • Mentions

On “Introductory bullshit detection for non-technical managers”

To quote ironic remark from "Uncle" Bob Martin: > Why do we write the code that slows us down? > And the answer to that is "Well, because we had to go fast! link to this video