John Nunemaker wrote a very nice article on assorted tips that improved his code… One of which revolved around naming. Regarding naming… I absolutely agree. It is worth arguing about. The more critical the class is to the system design, the more I might go to the mat and wrestle a good name to the …
Category Archive: modeling
Dec 30
Uncle Bob Challenges The Architecture of a Rails App
Uncle Bob has a very interesting keynote at the Ruby Midwest 2011 conference. I developed apps with the fundamental architecture of the following (with dependencies only crossing one layer): —— UI Layer —— Business Object Layer —— Data Mgt. Layer —— Born from the one pattern that is king of the hill in my book: …
Oct 04
Design Debates
many times there are two (or more) seemingly viable approaches that people can be arguing for… when in doubt, sketch it out… that is, quick model diagrams, or quick sequence diagrams, compare and contrast now let’s (hopefully continue to) presume this is about an exceedingly critical aspect, a make-or-break design decision. because surely, you aren’t spending …
Sep 26
Do I Still Do Domain Modeling?
Got a very nice “blast from the past” contact (4 levels deep) on LinkedIn. Scott was a member of a team where we went through object modeling for their business application. The reason I wanted to contact you was two fold: First for some reason that training has stuck with me more that many trainings …
Apr 24
MongoMapper Query Overview
There was a question on the MongoMapper Google Group from a Mongoid user about how MongoMapper handles associations. Brandon was surprised that this query returned an Array: Product.first.releases.where(something) Let’s break it down, one bit at a time and clear things up: # This would be an instance of Product Product.first # Class. This simply gets …
Apr 17
Multiple Many-to-Many Associations in MongoMapper
There was a question in the Google Group for MongoMapper, so I decided to post an answer in the form of a simple demo. You can find the source code on Github.com here. The basic shape of the problem was this: And the solution issues were around the multiple many-to-many associations, more or less. For …
