Episode 112: Programming Rules of Thumb Part 3
Podcast: Play in new window | Download
Laws and more rules of thumb to make your projects SOLID!
News and Follow/Ups – 01:00
- Feels like spring kinda, excited for backpacking
- Square works great
- SXSW
Geek Tools – 09:20
Webapps – 11:27
- Egg Timer – Easy web timer
- JSFiddle – Web-based javascript IDE (via email from Qasim Alyas)
Programming Rules of Thumb Part 3 – 18:18
- Metcalfe’s Law
- The value of a network is the square of the number of participants
- Twitter/Facebook/Ebay
- Murphy’s Law
- Anything that can go wrong, will go wrong
- Brooks’s law
- Says that “adding manpower to a late software project makes it later – The Mythical Man-Month
- Parkinson’s law
- Work expands so as to fill the time available for its completion.
- SOLID
- Stands for five basic patterns of object-oriented programming and design
- Single responsibility principle – An object should have only a single responsibility.
- Open/closed principle – Software entities … should be open for extension, but closed for modification
- Liskov substitution principle – objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program
- Interface segregation principle – many client specific interfaces are better than one general purpose interface
- Dependency inversion principle – one should “Depend upon Abstractions. Do not depend upon concretions
- Stands for five basic patterns of object-oriented programming and design
- GEFN
- Good enough for now
- Worse is better
- MVP
- Minimum Viable Product