Vague Requirements | Code Walks 032
Автор: Christopher Okhravi
Загружено: 2016-09-09
Просмотров: 4875
Описание:
Sandi Metz argues that you need abstraction when your requirements are vague. I've previously been saying that abstraction always is pragmatism, but I'll gladly admit that I now believe more in Metz's postulation. Abstraction is appropriate only when your requirements are not 100% clear. In some sense this is just another way of saying that if you are expected change.. you should introduce abstraction.
PREVIOUS VIDEOS ON ABSTRACTION
Premature abstraction is not premature
• PREMATURE abstraction is NOT premature | C...
Abstraction is pragmatism
• Abstraction is Pragmatism | Code Walks #003
OTHER VIDEOS MENTIONED
Sandi Metz on defining Object-Oriented Design
• Hashrocket Lunch n' Learn - Defining Objec...
GEAR USED
► CAMERA: Canon 70D http://amzn.to/29wR8wG
► LENS: Canon 10-18mm http://amzn.to/29srabL
► TRIPOD: JOBY Gorillapod Zoom http://amzn.to/29AdkHT
Повторяем попытку...
Доступные форматы для скачивания:
Скачать видео
-
Информация по загрузке:
