Although technically the sessions I submitted are entitled "Avoid Common Mistakes in T-SQL Programming" and "Developing Robust T-SQL for High Concurrency", the main thing you will take with you is the following: the ability to develop T-SQL that does not break in a changing environment, under real life concurrency. As such, you will not have to wake up at 3AM to make an urgent fix, and you will have your weekends for yourself.
When you have mastered the art of defensive programming, you will not need to spend 80% of your time making fixes after fixes after fixes - you will enjoy your job better, and you will surely have the time, energy, and motivation to learn all those cool new features.
If you would like to receive an email when updates are made to this post, please register here
Subscribe to this post's comments using
About Alexander Kuznetsov
Alex Kuznetsov has been working with object oriented languages, mostly C# and C++, as well as with databases for more than a decade. He has worked with Sybase, SQL Server, Oracle and DB2. He regularly blogs on sqlblog.com, mostly about database unit testing, defensive programming, and query optimization.
Alex has written a book entitled "Defensive Database Programming with Transact-SQL" and several articles on simple-talk.com and devx.com. Currently he works at DRW Trading Group in Chicago, where he leads a team of developers, practicing agile development, defensive programming, TDD, and database unit testing.