Skip to content
0:00 / 0:00

#cleancode#softwarearchitecture#unclebob

Clean Code - Uncle Bob / Lesson 5

UnityCoin

22K subscribers • 3 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Robert C. Martin, author of Clean Code
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

358K views7 years ago2 recommendations

Software designTools and practiceSoftware architectureDesign patternsRefactoring and legacy code

Robert C. Martin explains the fundamentals of software architecture, discipline, and the importance of quality code.

↓↓ 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 fifth lesson, Uncle Bob criticizes the culture of "making a disaster as quickly as possible" to generate economic gains, obtaining in the long term, exactly the opposite effect, due to a generalized lack of awareness, about the importance and purpose of a good Software Architecture. In this chapter, you will learn the fundamentals of software architecture, its rules, the value of discipline in the production of quality code, and the responsibility of disseminating the need to implement these good practices in the community of programmers. ↓↓ 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 quinta lección, el tío Bob hace una crítica a la cultura de "hacer un desastre tan rápido como se pueda" para generar ganancias económicas, obteniendo al largo plazo, exactamente el efecto contrario, debido a una falta de conciencia generalizada, acerca de la importancia y el propósito de una buena Arquitectura de Software. En este capítulo aprenderás los fundamentos de la Arquitectura de software, sus reglas, el valor de la disciplina en la producción de código de calidad, y la responsabilidad de diseminar en la comunidad de programadores la necesidad de poner por obra estas buenas practicas. Opening. Dick Vlot about Architecture and Agile Software Development. Presentation of Uncle Bob. Diffraction: Why do incandescent lights glow? Architecture Introduction / I've built lots of apps / "I want to be a programmer" anecdote. The Architecture rules are independent of every other variable. Working vs. Right. What is Design in Architecture? What is the goal of Software Architecture? Case study of bad Architecture. Executive View / What went wrong / Secret to going fast. Messes aren't faster even in the short term. Solution of the Executive's Dilema / Two Values of Sofware. Behavior / Are we going to see self driving cars? Scope vs. Shape / Stakeholders want changes. Urgency and Importance / Eisenhower Matrix. Fight for the Architecture. A Rails App / The web is a Ddelivery Mechanism. Architecture Floor Plans / A Use Case Driven Approach. Interactors / Entities / Interfaces Objects. Request Model. What about MCV? / Design Patterns / How MCV goes wrong as a web Architecture. Model View Presenter / Dependency Rule. What about the Database? / The Database is a detail / ORM Fitnesse: a wiki page porj

Why it's here

2 people recommend this

What people say. Recommended for its discussion on software architecture and whether applications truly need a database from the start.

Moments people linked to

u/Rennpain r/softwarearchitecture • Recommends

On “Hexagonal and Onion architecture”

link to this video The real topic starts after about 15 minutes. link to this video In this video the author actually works with code. 😉

u/OrdinaryTensionin r/programming • Recommends

On “What database should I use for my mobile app”

Do you really need a DB? Could you not simply use the local file storage? Alternatively, you could use a very simple DB, but only store meta data and a URI. Using the URI approach would allow for you to support local and remote images without duplicating the storage costs. I highly recommend watching this Uncle Bob presentation. I've linked to the point where he discusses your exact question with the suggestion of how to abstract and delay the DB decision. [video
2View on Reddit