Do you number tasks/questions?
10/11/2018 10:16 AM by
It is good practice to be clear on what you want. One way you can make things clearer is to number tasks or questions.
Bad example - the different tasks may be skipped if the reader does not read carefully
Make sure to use Linq to SQL for the bit where you execute Stored Procs. First, double check that executing Stored Procs is still an outstanding issue with EDMX.
Don't forget to create a .txt file of the same name to the rule, so other developers know why you did this.
Good example - the different tasks are clear
1. Double check that executing stored procedures is still an outstanding issue with EDMX
2. Add .txt file of the same name with a link to the rule, so other developers know why you did this
3. In the .txt file, link to the UserVoice suggestion
4. In the .txt file, link to the rule on Rules to better LINQ
5. Make sure that actual rule links to the UserVoice (or Connect) suggestion too
See also: Do you send tasks one email at a time?
VIDEO - Top 10+ Rules to Better Email Communication with Ulysses Maclaren
Do you feel this rule needs an update?