title

Using Code Contracts for Safer Code · forty-two

charset

utf-8

content-language

en

viewport

width=device-width,initial-scale=1

X-UA-Compatible

ie=edge

og:url

https://buksbaum.us/2011/04/20/using-code-contracts-for-safer-code/

og:site_name

forty-two

og:title

Using Code Contracts for Safer Code

og:description

Note: This was presented to the Tampa C# Meetup on April 20th, 2011. One of the greatest challenges in writing code is that nebulous time when the code is too complex to keep the flow all in your head, and when the debugger gets too much in the way for watching the state of your program as it runs. This is the coding twilight zone in which the quality of the code tends to drop as you add line after line of instrumentation to your code to find that spot where something goes wrong. For most of my code writing career I solved this by littering my code with lines like the following:

og:locale

en

twitter:card

summary

twitter:title

Using Code Contracts for Safer Code

twitter:description

Note: This was presented to the Tampa C# Meetup on April 20th, 2011. One of the greatest challenges in writing code is that nebulous time when the code is too complex to keep the flow all in your head, and when the debugger gets too much in the way for watching the state of your program as it runs. This is the coding twilight zone in which the quality of the code tends to drop as you add line after line of instrumentation to your code to find that spot where something goes wrong. For most of my code writing career I solved this by littering my code with lines like the following:

apple-touch-icon

/apple-touch-icon.png

canonical

https://buksbaum.us/2011/04/20/using-code-contracts-for-safer-code/

icon

/favicon-32x32.png

icon

/favicon-16x16.png

manifest

/site.webmanifest