Showing posts with label Design Patterns. Show all posts
Showing posts with label Design Patterns. Show all posts
Friday, July 27, 2012
Is that why you didn't come to work yesterday?
You can read about lazy loading at: http://en.wikipedia.org/wiki/Lazy_loading.
I didn't know Martin Fowler had delineated four different styles of lazy loading: "There are four ways of implementing the lazy load design pattern: lazy initialization; a virtual proxy; a ghost, and a value holder."
I've used three of four. Ghost is not the one I've missed.
Title: Is that why you didn't come to work yesterday?
Snarky: Not so fast. I'm a lazy loader.
Thursday, June 14, 2012
Just because dot-driven development returns a function, doesn't mean that function does anything useful.
I love the phrase dot-driven development. Not because I think it's sad that developers might not know their language of choice inside out and have to rely on the IDE, but because programming has evolved over the years, and a bit of dot-driven makes it possible to code in multiple languages, particularly when they're similar (ahem, Java and C#), but have slight variations on function names. You know what it does and what it's probably called, but it would be painful to have to dig around on line or in documentation to verify every single method call.
Ploeh Blog in Design Patterns Across Paradigms states, "As Phil Trelford kindly pointed out at GOTO Copenhagen 2012, OOD is often characterized by 'dot-driven development.' What does that mean? It means that given a variable, we can often just enter ".", and our IDE is going to give us a list of methods we can call on the object..."
Title: Just because dot-driven development returns a function, doesn't mean that function does anything useful.
Snrky: If only our manager was OO I could ask the IDE to provide appropriate functions to call.
Monday, October 31, 2011
Subscribe to:
Posts (Atom)


