Widgets Flotsam and Jetsam #75

Flotsam and Jetsam #75

By Nick at January 20, 2013 12:44
Filed Under: Delphi, Flotsam and Jetsam
  • Now here’s a blog after my own heart:  Sadly, it hasn’t been updated in a while, and there are only a few articles, but what is there is really good.  There are four or five articles about Dependency Injection (particularly about how it doesn’t necessarily mean using a DI Container…..) and we’d all do well to read and heed. Thanks to Stefan Glienke for pointing me to it.
  • RAD Studio won the “Top Innovator: Developer Tools” at the Developer Week Conference.  Nice thing to see.
  • I wanted to strengthen my SQL skills, so I decided to give Head First SQL a try.  It was my first foray into the world of the Head First Series, and I was pleasantly surprised. I wasn’t quite sure what to expect, but what I got was a great review/tutorial on SQL.  The examples were simple but to the point, the style a touch irreverent but enjoyable, and I actually did, and learned from, the exercises.  Now I’m working on Head First Design Patterns which so far is the same: excellent, interesting, and attention-holding. I do believe that I'll seek out Head First titles in the future if I want to learn something new.
  • I’d like to put in another plug for the Google Plus Delphi Developers Community.  We’ve been having a lot of fun over there – or at least I have, maybe the rest of the folks are sick of me.  Winking smile  In any event, please stop by and participate. 
  • Shameless Plug of the WeekSign up for Sprint cell phone service.

Comments (11) -

1/20/2013 2:22:01 PM #

When I read "Head First Design Patterns", I realize how much the so-called Patterns breaks sometimes the SOLID principles.

I really can't get into Design Patterns... any feedback from you is welcome!

Arnaud Bouchez France |

1/20/2013 10:11:07 PM #

Interesting -- can you give an example?  Breaking SOLID isn't a good idea.

nick United States |

1/20/2013 2:43:23 PM #

Select the Head First books wisely. The older the better - the earlier the a certain topic head been covered the more likely it is to get a good book. Head first HTML, Head First Java, Head First Design Patterns are a good choice. After a few good (most of them IT related books) authors sold under the Label 'Head First' ...

Bunny Austria |

1/20/2013 8:04:30 PM #

The Head First Design Patterns book is what let me get a real handle on Design Patterns and both how and why to use them.
I had read Gang of Four years before that, and slogged through...knew it was good for me, but not really sure why. After Head First, I went back to Gang of Four...still a BIT of a slog, but much, much better.
And I have enough stuck in my brain that I know what is available to use when I need it (but not just for the sake of applying patterns...I would NEVER do that!)

Doug Johnson United States |

1/21/2013 8:31:03 AM #

I find interesting one of the comments on "Just say no to the Service Locator abomination."

All the more interesting, taken in the context of your many positive comments on Spring4D, and your own writing on DI....

William Meyer United States |

1/21/2013 9:41:57 AM #

Bill --

Service Locator is a very controversial topic in the DI world.  The root of it comes from the notion that "Singleton's are bad".  I'm not sold on that idea, but clearly others are.  Wink


nick United States |

1/21/2013 11:31:21 AM #

So I see. Reminds me of the Free vs. FreeAndNil arguments. ;)

I'm still time-challenged for making use of frameworks, and continue to wish that they were better documented. The two I feel most inclined to spend time on are DSharp and Spring4D, but so far, the time available is insufficient for a serious look at either. Hopefully I can remedy that lack soon.

William Meyer United States |

1/21/2013 3:36:50 PM #

Singletons are not bad because they are bad, but because people use singletons for wrong purposes, and because they use singleton implementations that cannot be tested.

Dalija Prasnikar Croatia |

1/21/2013 11:28:58 PM #

singletons are global vars and as such they are always bad. The only place Service Locator should be used is in the composition root of the application. Any other use is an anti-pattern. If you must create objects outside of the composition root then use an object factory.

Service Locator is the perfect example of "a little knowledge can be dangerous".

Tapper United States |

1/21/2013 2:54:44 PM #

I have learned a lot from books in the Head First series

Pato Moschcovich United States |

1/23/2013 3:32:30 PM #

Well, it's nice to see there is no disagreement on Singletons...  ;)

William Meyer United States |

Comments are closed

My Book

A Pithy Quote for You

"No concept is so difficult that it cannot be conquered by the repeated attacks of the ordinary mind"    –  Morrison Hodges, MD (My Dad)

Amazon Gift Cards

General Disclaimer

The views I express here are entirely my own and not necessarily those of any other rational person or organization.  However, I strongly recommend that you agree with pretty much everything I say because, well, I'm right.  Most of the time. Except when I'm not, in which case, you shouldn't agree with me.