http://blog.slickedit.com/2008/04/coding-tips-generational-naming/ "Hello World" - The SlickEdit Developer Blog Wed, 08 Feb 2012 10:18:34 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://blog.slickedit.com/2008/04/coding-tips-generational-naming/comment-page-1/#comment-402 Monkeyget Wed, 02 Apr 2008 18:14:10 +0000 http://blog.slickedit.com/?p=228#comment-402 What I do is misspelling or subtely change the function name so that when you look at the new function you don't even notice something changed. For example findMatches could become findWatches. For best results impose a font to your team that makes characters hard to tell apart. What I do is misspelling or subtely change the function name so that when you look at the new function you don’t even notice something changed.
For example findMatches could become findWatches.
For best results impose a font to your team that makes characters hard to tell apart.

]]> http://blog.slickedit.com/2008/04/coding-tips-generational-naming/comment-page-1/#comment-394 mikeb Tue, 01 Apr 2008 17:38:07 +0000 http://blog.slickedit.com/?p=228#comment-394 For no good technical reason I prefer the 'Ex' naming convention for an 'enhanced/fixed' API. It's purely aesthetic and it devolves into using numbers if you need another round. Hopefully, you give things enough thought on the second go around to not have to do a third. For no good technical reason I prefer the ‘Ex’ naming convention for an ‘enhanced/fixed’ API. It’s purely aesthetic and it devolves into using numbers if you need another round. Hopefully, you give things enough thought on the second go around to not have to do a third.

]]>