Writing Good Unit-Tests: A Step By Step Tutorial

A tutorial to help you write comprehensive unit-test suites.

Let’s imagine we just wrote a method calculating distance between two points on our planet. And let’s imagine we want to test it as well as possible. How do we come up with test cases? And what exactly do we need to test?

Continue reading “Writing Good Unit-Tests: A Step By Step Tutorial”

The Hunch: 4 Times I Felt It And 1 When I Didn’t, And What Were The Consequences

I sometimes have this feeling: The Hunch™. It’s when I sense there is something wrong with the project, with the requirement, or with the feature, even when everyone else is sure all is well.

When I sense this, I feel like a dog who picked up the scent. I follow the scent by asking questions, until I get my answer.

Here’s how it happens.

Continue reading “The Hunch: 4 Times I Felt It And 1 When I Didn’t, And What Were The Consequences”

11 Mistakes To Avoid On A Technical Interview

You’re in for a technical interview. They ask you a question, and you have to build a system or to write some code, either on a whiteboard (brr!), on a piece of paper, or on a laptop at home. And then you discuss it with the interviewer.

Some enjoy it, and some dread it. But if you are going through it, it means the end of the process is near! And you really want to show the best side of yourself.

I led more than 120 interviews. Here are some common mistakes I noticed the candidates make.

Continue reading “11 Mistakes To Avoid On A Technical Interview”

Unit-testing: best practices

I have unit-tested my code for many years.

While building a GIS-system, we really cared about our product quality. Our users’ needs demanded the app to work properly. I had all critical and/or complex parts of code 100% test-covered, with multiple paths and corner cases. It was such a pleasure to find a bug, fix it, write a couple of tests for this surprise scenario, and be sure it won’t break again. Ah, good times.

Continue reading “Unit-testing: best practices”