Last week a very nice thing happened with me. Two of my colleagues asked my advice on analyzing corner cases.
Many developers tell what they have done. They used Kafka, RabbitMQ and Kubernetes. They sharded, scaled and clustered. They moved the logic from monoliths to microservices. They built castles and teared down mountains.
What they often don’t say is why they did it.
I often ask this question on interviews:
“What is the most interesting or challenging task you have ever done?”
The answer tells me a lot.
How I sensed a bug while not seeing any, and what came of it.
Today I found a place on our website where we display the size of a recreational area in square kilometers.
I cannot fully explain what happened next, but I had a hunch something must be wrong with this feature.
Narrator: there was.
A little story about a very common mistake when working with Earth coordinates around 180th meridiane.
Several days ago, I got a bug request: no airports around a certain hotel were being displayed.
There certainly were some airports relatively close to the hotel, and judging by all conditions they should have been there. This hotel’s page could boast with very good air connections, but it did not.
Like a proper seasoned Geo-expert should do in this case, first thing I did – was checking the location of the hotel.
Of course, it was located on Fiji.
The problem immediately became absolutely clear to me.
I’ve been running A/B tests for 2 years now, and during this time I have run more than 300 experiments.
I will share with you my knowledge: I will explain what A/B testing is, when do you need it (and when you don’t), and how to utilize it to the greatest extent.
This article is based on my conference talk about A/B testing – check out the slides.
What is A/B testing, anyway?
Let’s imagine you own a webpage for selling flowers, and you have a red “buy” button in there.
Now let’s imagine your new designer tells you: hey, green buttons are a new trend in the flower selling industry. People like green more than red, red is aggressive, green is soft and persuading. Green button will be more visible on the page. Let’s make it green.
I presented this talk on the ItNonStop conference in Wrocław, on November 18th, 2017.
I explained what A/B testing is and how do we in Booking.com apply it to our location-related information, such as location of museums, landmarks, beach, shopping malls, or historical areas.
The easiest step you can take against your impostor syndrome.
Lately I’ve been trying to give this small advice to people with impostor syndrome, and I think it seems to work – so here it goes.
How to understand if this company is a good fit for you? Why, ask them questions, of course!
I’ve been on both sides of interviewing for a while now. As a candidate – for 9 years, and as an interviewer – for 90 interviews. (What a beautiful round number!)
So I decided to write down questions which I usually ask the company when considering their position.
What’s common between software and opera houses? Building of both often goes overtime. Read on to know why and what should you do about it, as a client or as a developer.
Many software projects go overtime. Software developers get blamed for that, laughed at, scorned at.
But guess what: it’s not only software developers.
Many building projects also go overtime, and most noticeably of all, perhaps, opera houses and concert halls.
You know how the software developers are always mocked because they don’t comply with the time limits? Read this article about my experience of hiring a team of freelancers who went way over the deadline.
Not so long ago I hired a team of freelancers to work on a project of mine.
Everything started as it usually starts. I found several teams, some through friends and some – through a website. I met with team leaders, we discussed my requirements, we agreed on time and on a budget. I picked the team that looked the most reliable to me, they rolled up their sleeves and started to work.