in my last article i was stressing the importance of testing code with realistic data volumes in order to detect potential performance issues when the code is actually deployed. that got me to thinking about something that i don't normally think about. the quality of the code we write. now you are probably wondering what on earth i mean by the "quality" of the code that we write? after all, code is either good (it works, does what it is supposed to and doesn't crash) or bad (it doesn't do what it is supposed to, or crashes). however, that… Continue reading