Brad Abrams on GotDotNet Blogs posts On Designing Good Libraries. This is an excellent post, sort of a Cliff's notes (is Cliff still around?) or super-condensed version of the .NET Framework Design Guidelines for Class Library Developers. Under "First Principles" he says to write the code the developer will have to write, then model your library's API around making that possible. This is exactly what Test-Driven Development's first step is (write the unit test code that calls the method you want to create). Since Brad is responsible, in part, for keeping up the consistency in the .NET Framework with a large number of developers, his suggestions should certainly work for any of the smaller efforts most of us will work on.
Samer Ibrahim posts about Naming Conventions for Forms/Controls/Stored Procs/etc. He comes to the conclusion that naming things in noun-action format is easier, especially for maintenance, than action-noun. If you think about it regarding stored procs, when the stored procs are listed, would you rather be able to look for OrderDetails or Select? Roughly 25-50% of your stored procs will be Selects, so if you are a glutton for punishment, go right ahead! I prefer the noun-action format, for example: OrderDetailsSearch (for a muti-parameter query), OrderDetailsSelectMultiple (usually by foreign key), OrderDetailsSelectSingle (by primary key to most code generators), OrderDetailsInsert, OrderDetailsUpdate, OrderDetailsDelete.