123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101 |
- - title: "Programming across paradigms"
- speaker: "Anjana Sofia Vakil"
- slug: programming-across-paradigms
- description:
- license: youtube
- site: youtube
- id: uNPdZm5oF_E
- - title: "Connascence Examined"
- speaker: "Jim Weirich"
- slug: connascence-examined
- description: >-
- Introduction to the idea of connascence its relation to coupling. Excessive
- connascence in our software means that the system may be hard to change,
- and hard to maintain.
- license: confreaks
- site: youtube
- id: HQXVKHoUQxY
- - title: "Running a Government Department on Ruby for over 12 Years"
- speaker: "Jeremy Evans"
- slug: running-government-on-ruby
- description:
- license: youtube
- site: youtube
- id: 2Rm7wLNmsco
- - title: "Advanced Ruby Class Design"
- speaker: "Jim Weirich"
- slug: advanced-ruby-class-design
- description:
- license: confreaks
- site: youtube
- id: vwBpTgdZBDk
- - title: "Workflows of Refactoring"
- speaker: "Martin Fowler"
- slug: workflows-refactoring
- description:
- license: youtube
- site: youtube
- id: vqEg37e4Mkw
- - title: "Seven Ineffective Coding Habits of Many Programmers"
- speaker: "Kevlin Henney"
- slug: ineffective-coding-habits
- description:
- license: youtube
- site: youtube
- id: ZsHMHukIlJY
- - title: "The computer revolution hasn't happened yet"
- speaker: "Alan Kay"
- slug: computer-revolution-hasnt-happened
- description:
- license: youtube
- site: youtube
- id: oKg1hTOQXoY
- - title: "OOP is Dead! Long Live OODD!"
- speaker: "Daniel West"
- slug: oop-is-dead
- description:
- license: youtube
- site: youtube
- id: RdE-d_EhzmA
- - title: "The Grand Unified Theory"
- speaker: "Jim Weirich"
- slug: grand-unified-theory
- description:
- license: confreaks
- site: youtube
- id: NLT7Qcn_PmI
- - title: "Debt Metaphor"
- speaker: "Ward Cunningham"
- slug: debt-metaphor
- description: >
- The debt metaphor refers to our ability to deliver code without a full
- understanding of the problem domain. The ability to pay back our technical
- debt depends on us writing clean enough code to be able to refactor it as
- we come to understand the problem. Rushing code out shouldn't be an excuse
- for poor coding.
- license: youtube
- id: pqeJFYwnkjE
- site: youtube
- - title: "MiniTest: Refactoring Test Unit and RSpec"
- speaker: "Jared Ning"
- slug: minitest-refactoring-frameworks
- description: >
- Differences, and similarities, among Ruby testing frameworks.
- license: confreaks
- id: IHB__duBuT0
- site: youtube
- - title: "A Philosophy of Software Design"
- speaker: "John Ousterhout"
- slug: philosophy-software-design
- description: ""
- license: youtube
- id: bmSAYlu0NcY
- site: youtube
- # - title: ""
- # speaker: ""
- # slug:
- # description: ""
- # license:
- # id:
- # site:
|