As I plowed my way through A/B testing of more than 300 features, I was wondering: are there any cases when you don’t want to A/B test?
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.
You can’t possibly imagine what I found today! 😍
Back in 2008 I wrote a set of lectures on C++ and OOP for my uni, and never published them anywhere. Until today.
Continue reading “C++ From The Past – I found C++ and OOP lectures I wrote back from 2008!”
Code reviews are a great practice to apply in software development. The approach is very simple: when you’re done with your code, give it to someone else to look at and leave comments.
Despite of its simplicity, it brings considerable advantages. Here are 7 reasons why this practice is useful.
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.
I call it a hunch.
Sometimes I sense something’s wrong.
There is no visible indicator of it. Devs say it’s going well, products say it’s on time and under control, specialists say it’s all aligned and agreed on.
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.
Here are some sundry thoughts I’ve had throughout my career as a developer and lately a team leader.
Last week a very nice thing happened with me. Two of my colleagues asked my advice on analyzing corner cases.