Sql-Server

This is the part one of a lighting talk I’m giving at the SQL Saturday Edmonton Speaker Idol Contest.   Imagine I’m actually speaking the words below and showing some of the images on slides and/or doing a demo.  Code can be found here.

This is a rough draft so constructive feedback at chris.cumming@saturdaymp.com is much appreciated.

Skip ahead to Part 2 if don’t feel like reading all of part 1.

Developer Bud wants to create a new application to track the board games he and his friends play.  He wants a simple website where him and his buddies can login to update the results from the board games they have played.  Being a .NET Developer he creates a ASP.NET MVC Core application with individual authentication.

Once upon a time in the far off land there a young handsome software developer.  This developer married the fairest maiden in the land and together they formed a company to slay problem monsters that prevented others from getting stuff done.  After a couple of successful adventures of banishing problem monsters the developer was asked by another problem monster slaying company to help deal with a monster bugging the local government.  The developer agreed to help.

You’ve been staring at the SQL Server view vwCustomersGH for the past hour.  The view is part of a project you just started maintaining and like many views and stored procedures in the project you are sure it’s not being used anymore.  Because you are a conscientious and professional software developer you want to remove this view along with the others.  You don’t want to leave it lying around for the next developer to stumble over like you did, getting confused between the legit vwCustomers and  suspicious vwCustomersGH.  What does the GH stand for anyway?