2020, December 23th
A* just came back from New York to spend holidays with his family. We take advantage of his come back to work together.
For the first time in 8 months, we will work together at the same place. I go to his place in the morning, sit with my computer, and we code. He codes for the IFC, and me for my Python projects.
When we brainstorm, we are very straight to the point. A bit like when we talk online. Because of the distance, we never see each other. And the truth is that we don’t call often to brainstorm or whatever. Sometimes we do, but not a lot.
In the contrary, we have become accustomed to developing the product by communicating almost exclusively in writing. Writing gives time to process before responding. While in real life, it is usual to answer immediately before thinking.
And it looks like we replicate this “straight to the point” way of talking offline as well. We don’t talk a lot, we go straight to the point.
Idea -> Feedback <-> Feedback -> Execution
Here is an example of one of the many written conversations we talk about the product.
- Here is my proposition : Instead of Group A, Group B, you swipe to access the next day.
- But we said it was bad to swipe didn’t we ? If there are 40 games
- Yes. The best is what you did with the website.
- I’m not sure that it’s the best. See how it works. You have tabs, and you add new tabs. We have to make an expendable ranking.
- What do you mean ?
3 messages later
- Ok, let’s do this.
We have hundreds of written conversations like this.
— — — — — — —
The app keeps improving, and captains now all have their logos !