Oct 23, 2017 11:00:06 AM by Denny Cherry
I found the above instructions on a blog post I was trying to use to fix an issue in visual studio recently. (Ignore the fact that I was in Visual Studio and focus on the screenshot.) This post has 4 step. Step 1, which you can see above has two warnings in it, but now followup information about what to do it you get the errors that it says. It doesn’t give you links out to posts on how to fix these critical errors. In fact, I could go no further in working through this issue in Visual Studio. I ended up simply copying the code manually from one branch to another as that took me 20 minutes and I spent 6 hours trying to figure out how to fix the issue.
When it comes to writing blog posts, writing for the expert is fine, but at the least, you need to have links out for the beginner, if not put those details in your post. Not everyone out there is an expert and knows how to use products at the Scott Hanselman level. If they did we wouldn’t need blog posts on how to do things. Some people like myself and really good in some areas (SQL Server) and not others (Visual Studio) and posts should cater to everyone.
Tags: SQL Server
Written by Denny Cherry
I am a Senior SQL Server DBA at CDW with 10 years of IT experience, mostly as a software developer building web and windows based applications (VB, VB.NET, C#, C++ and a smidge of Java). I have always found database design and set based logic interesting, so 3 years ago I took the plunge and became a DBA, soon after I discovered people would tell anyone who would listen all about the SQL Server internals. I was hooked. I have not looked back since. The things I say represent my opinion and in no way represent the views or opinions of my employer or coworkers.