Work smarter

In the previous posts, we examined the Why, When, and How Much of testing. In this post, we will complete the thread with an examination of What we should be testing and What we should not be testing.

In the previous post, we examined the Why and When of testing in this post, we will build on that foundation and look at How much we should be testing.

When it comes to testing, the most common misunderstanding is the motivations of testing itself. Some folks see testing as a burden imposed from on high. Some folks see testing, or more specifically, test coverage, as a metric that determines how well they did their job. Sorry, but neither of these is true. This post will address these fallacies and give you a different perspective on testing.

This is my light-hearted attempt to help engineers get the most value out of a downtime incident.

This is my light-hearted attempt to help engineering managers get the most value out of a downtime incident. Introduction So you had an incident? Condolences.On...

Ever hear the expression, the punishment should fit the crime? How about, a proportionate response? How about, to a man with a hammer every problem looks like a nail? Now, I'm not trying to implying that your...

If you "write code" for a living, chances are you have a one time described yourself as a "Software Engineer".  And chances are, you are not.Personally, I graduated with an Engineering (Software Systems) degree...