Learning

70-487 Study Info

I recently study for and pass Microsoft exam 70-487. This was the last test I needed for my Microsoft Certified Solutions Developer certification. It feel good to have this one under my belt. I thought the test covered a lot more information then the other two I took for this certification but in the end I might have over studied…

Continue Reading

Development, Process

GIVEN-WHEN-THEN

Given-When-Then is a way to represent behaviors or ‘features’ of a system. Also, know as Gherkin it is heavily used in Behavior-Driven-Development or BDD as well as Test-Driven-Development TDD. Here is a quick definition of each part of the style. Given – This describes the state of the system before any action is taking. In other frameworks, this is knowns…

Continue Reading

Development

Update Git on Windows

Over the last few years, the changes to the commands available for git has exploded. I was looking at some of the new commands and one looked super awesome. Switching branches has always been a little non-intuitive to me when using the git command line. You run the following command: This has always weird because I was not checking out…

Continue Reading

Architecture, Standards

T-SQL Documentation

This is a standard of how we should document databases and data structures. Philosophy In order to fully understand our data structures and to make our software more maintainable we want to have good documentation of our T-SQL. This helps lower errors in code and helps future developers understand why a database or data structure exists. Documentation Guidance Database Each…

Continue Reading

Architecture, Standards

T-SQL Code Readability and Format

This standard should provide guidance for developers who are writing and working in T-SQL. This for all T-SQL code including stored procedures, function, etc… Philosophy We want to have code the is readable and formatted in a consistent manner across enterprise. This will help provide high quality development as well as it will lower the cost of future maintenance of…

Continue Reading

Architecture, Standards

T-SQL Error Handling

This is a architectural pattern for handling errors in T-SQL. Philosophy The philosophy we will be using for error handling is that we want to make sure that all errors are understood and handled appropriately. This is important for T-SQL because we do not want to corrupt data, stop processing or have silent errors.   We will be using TRY CATCH…

Continue Reading

Architecture, Standards

T-SQL Logging

This is a framework and standard for handling logging different system messages including Debug, Error, Fatal, Info, Trace, and Warn for aiding in trouble shooting, auditing and tractability of the T-SQL system. Philosophy We want to make sure that if anything happens in the execution of T-SQL that is abnormal, that we log out what occurred to help with troubleshooting…

Continue Reading

Architecture, Standards

T-SQL Naming

This standard should provide guidance for developers who are naming object in T-SQL. Philosophy We want object to have simple to understand and consistent naming across all T-SQL in an enterprise. This will not only help your quality but speed up the development life cycle of T-SQL projects. Overall All Concepts This are concepts that apply to all T-SQL objects…

Continue Reading