We Are Devs

Observations of the space at present.  Tongue in cheek of course Twilosophy\Twitosophy. I don't usually offer much opinion in what I do. I  sit on the fence alot, maybe I shouldn't . However, when I do, I try to base what I know on what I really know, not on what other people tell me I need to know.  I'm sure what I am observing has been commented on before, and maybe other people agree or not, but reading a post on Twitter and then using it as your own keen insight  or shallowly cited insight is more of an indication of your lack of ability instead of  just keeping schtum or just saying "I dont know", where more respect would probably be gained.  The above practice seems to be rife in software development at the moment.  I'd be a hypocrite if I said I hadn't fallen into the trap, but - like a recovering alcoholic - I have realised the errors of my ways and I am standing up and saying my name is Colin and I am a twitosopher (at times)  and shallow

Static Code Analysis. You may remember my opening gambit in a post about SSDT code analysis talking about coding standards back in May 2014 (but most probably not)  It went something like.... Coding standards (and more latterly styles) in any organisation of any size are liable to incite religious wars and makes zealots out of even the most considered or apathetic of us.   Inconsistency and subjectivity,  lack of enforcement and heavy handedness all contribute to the contempt often levelled at them... blah blah Contributing to solving the problem. As part of one of our projects we had some funding to invest some time  and dev into SQL static code analysis, after researching what was available we had the green light to incorporate analysis written to leverage the SSDT code analysis framework into our own CI/CD ALM framework.  The appetite for this waned somewhat with the DB community having their own take on what they wanted to use, but the code lives on and some small bits of w

I put up an article back in November '14 about using async/await for a toy project I had created.   I have now had a chance to use it for "real work" and, as a result, have had a chance to research the language feature in more depth and have come up with a list of considerations, resources, gotchas and tid-bits.    Must Reads There is a lot of literature available for this feature and plenty of MSDN articles and Stack Overflow related help, however, I'd highly recommend the following books for greater insight into TAP, TPL and async/await:  CLR via C# (Fourth edition for async/await content), Jeffrey Richter Concurrency in C# Cookbook, Stephen Cleary Async in C# 5.0 ,  Alex Davies Blogs by the latter two also cover this feature in great detail. They all overlap in their coverage on async/await. As an aside, the first book I would recommend to any serious C# developer anyway, I'd say its on a par with the "C Programming language by Kernighan