• Post Reply Bookmark Topic Watch Topic
  • New Topic

Crush refactoring(s)?

 
Juan Rolando Prieur-Reza
Ranch Hand
Posts: 237
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bill,
I just took a look at some of the examples which you have courageously published. I'm sure we will all find these useful.
I have some humble questions about at least one of the anti-patterns. For example, the Crush anti-pattern caught my attention because I recently addressed the same concurrent-update functionality. My solution was definitely not what you described as Versioning. I believe there are many variations both to this anti-pattern and ways of avoiding and fixing it.
Would you care to comment?
 
Bill Dudney
Author
Ranch Hand
Posts: 234
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi John,
Very good point. Versioning is one of the easiest ones to implement (least disruptive) but there are many others. In many of the situations that we have seen this AntiPattern the tables already had time stamps so adding a 'version' check based on that was fairly straight forward and not very disruptive to the rest of the code.
I'd love to hear about your expierence and refactoring!
Thanks again for the kind words about the content!
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!