Archives
-
What Would You Not Like To Be Today?
-
IDs to Objects
A few months ago I blogged about Domain Objects vs. Primitive Types. Back then it felt right to me to transform a primitive type, like a Guid that represented an organization ID, to an Organization domain object. Unfortunately at that time I was not educated enough to know that this is a common idiom among many object designers. Apparently it is. Craig Larman writes it nicely in his book (in my case Organization is what Craig references to as a Customer):
-
Have Honest Opinion
It is very hard to provide an honest opinion when you are involved in a situation. I found it always difficult for myself and admired people of being able to do it, lifting themselves from emotional attachments to the matter.
-
Command-Query Separation Principle
A few days ago read in Larman's book about Command-Query Separation Principle. Funny to mention that I heard about the concept many times ago, but this is the only source that stated it as a principle. And it makes total sense once you evaluate all the pros and cons of the idea.
-
3 Years
Today is 3 years since I started working with the company I work today. It's being a long journey from figuring out what I want, till realizing what I am and need to be. The team has accepted all of my wildest ideas about the code and was very tolerant to the fact that I cannot wait to get something done. We've made a long way.
-
Code Smell vs. Code Stench
Interesting difference I picked up from a book this morning - code smell vs. code stench.
-
Google Shortcut Keys - Awesome
For all keyboard junkies out there - if you are also hooked on Google products (GMail, Reader, Calendar, etc), don't miss the option of using GMail with keyboard shortcuts. The are awesome. I loved the navigation shortcut (combination of pressing first G and then another key, neat).
-
Two Loosely Coupled Code - Part 2
In the
I raised the question of "Too loosely coupled design". There's a lot to discuss about it, and I am not going more time on it, except showing one more sample that IMHO shows the benefits and outcomes of the principle being applies, or consequences of not doing so. -
Too Loosely Coupled Code
Strive for loosely coupled designs between objects that interact.
-
A Month of Silence
[Pure personal content]
-
OCP Principle
Jeremy Miller (aka The Shade Tree Developer) has a very good article about OCP principle printed by MSDN magazine. This is a valuable article for any developer that strives to work according to law of "measure twice, cut once", and not just cook spaghetti. http://msdn.microsoft.com/en-us/magazine/cc546578.aspx