﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>nichols.mike.s AT gmail.com (Mike Nichols) commented on A code base has its own style</title><description>I see alot of this in dealing with presentation problems such as patterns that have worked for deeply nested collections that are written to the view without letting the view have any significant code. For example, I am using Observer alot to stick inside a repeater to deal with collection item presentation from the presentation layer.
  
I always try to suffix the objects that either are employing a pattern or are parts of a bigger pattern with standard names for these so that I can know how to relate to it. 
</description><link>http://ayende.com/2807/a-code-base-has-its-own-style#comment5</link><guid>http://ayende.com/2807/a-code-base-has-its-own-style#comment5</guid><pubDate>Fri, 28 Sep 2007 16:34:20 GMT</pubDate></item><item><title>Joe Ocampo commented on A code base has its own style</title><description>Favorite design pattern syndrome!  
  
  
Seems the teams really groks one pattern and uses the hell out of it for everything!  Not that this is a bad thing but it is funny to see how many XYZstrategy classes there are in the solution.
</description><link>http://ayende.com/2807/a-code-base-has-its-own-style#comment4</link><guid>http://ayende.com/2807/a-code-base-has-its-own-style#comment4</guid><pubDate>Fri, 28 Sep 2007 15:54:15 GMT</pubDate></item><item><title>Francois Tanguay commented on A code base has its own style</title><description>Definitely,
  
  
We come up with conventions such as:
  
  
- FindXYZ methods will return null while GetXYZ methods will throw.
  
- TryXYZ will return bool and out value
  
- All DTOs are suffixed with the Data keyword.
  
... and it goes on and on....
  
  
Surprisingly, those are never documented although they come through naturally by pairing...
</description><link>http://ayende.com/2807/a-code-base-has-its-own-style#comment3</link><guid>http://ayende.com/2807/a-code-base-has-its-own-style#comment3</guid><pubDate>Fri, 28 Sep 2007 14:57:17 GMT</pubDate></item><item><title>Scott Allen commented on A code base has its own style</title><description>I'm looking at code now with a string pattern - that's the worse. 
  
  
i.e.
  
  
Session["magic"]
  
dataSet["magic"]
  
Cache["magic"]
  
  
Everywhere I look, I see string literals. 
</description><link>http://ayende.com/2807/a-code-base-has-its-own-style#comment2</link><guid>http://ayende.com/2807/a-code-base-has-its-own-style#comment2</guid><pubDate>Fri, 28 Sep 2007 14:07:12 GMT</pubDate></item><item><title>Nate Kohari commented on A code base has its own style</title><description>My own code seems to always include type triplets: an interface (IService), the abstract base class (ServiceBase) and the standard implementation (StandardService). Interaction is based on the interface and inheritance is based on the abstract base class.
  
  
I don't necessarily like it -- the Base suffix in particular can be obnoxious. :) I just started doing it that way, and it stuck.
</description><link>http://ayende.com/2807/a-code-base-has-its-own-style#comment1</link><guid>http://ayende.com/2807/a-code-base-has-its-own-style#comment1</guid><pubDate>Fri, 28 Sep 2007 12:13:15 GMT</pubDate></item></channel></rss>