Phil Factor

  • Interests: Motorbikes, Beer, gardening, conservation, Local history.

SQLServerCentral Editorial

Programming Rules and 'Best Practices' Can't Replace Professional Judgement

In which Phil Factor casts doubts on 'programming policies'. For certain, any IT team development requires plenty of methods of working that maximise productivity, but coding standards and ‘best practices’ have to be treated with caution. Programming rules can’t replace professional judgement

4.86 (7)

You rated this post out of 5. Change rating

2015-02-09

201 reads

SQLServerCentral Article

Static Code Analysis: a necessary irritation.

There is little doubt that static code analysis can contribute to code quality and deliverability. As an aid to a developer, it seems increasingly essential, but can it ever deliver reliable metrics of code-quality? One shudders at the potential misuse of quality metrics in the wrong hands. My hope is that it remains just an aid to human judgement; and creativity.

5 (1)

You rated this post out of 5. Change rating

2014-07-28

57 reads

Blogs

A New Word: Lilo

By

lilo– n. a friendship that can lie dormant for years only to pick right...

Learning Database Design and Power BI Performance

By

I spend my days working on and managing SQL Server instances—working days at least,...

Free SQL Training: Dive into Databases This December!

By

Want to learn SQL and get some real practice this December? Check out the...

Read the latest Blogs

Forums

how to calculate an average only if a minimum number of records exist?

By water490

Hi I am working on a rolling average calculation that is not working quite...

Subscribing to a Great New Year

By Louis Davidson (@drsql)

Comments posted to this topic are about the item Subscribing to a Great New...

dont want pkg to abort if someone is in excel source document

By stan

Hi, is there a way when using excel as a flat file source in...

Visit the forum

Question of the Day

The Funny Dynamic SQL

What happens when I run this code:

EXEC sp_executesql N'PRINT 1; GO';

See possible answers