Articles

Peter Ramsey: “But the issue isn't the completion rate, it's the experience.” → Read More

Ian Spalter: “When I start a new project, the first thing I do is to define the problem, to understand the “why” of what we're trying to do and what is the thing we're trying to solve for?” → Read More

Tom MacWright: “The emerging norm for web development is to build a React single-page application, with server rendering.” → Read More

Superhuman: “Every interaction should be faster than 100ms. Why? Because 100ms is the threshold where interactions feel instantaneous.” → Read More

Linear: “We truly believe that the tools teams use directly impact the outcome of their work. Bad tools encourage bad habits. Good tools encourage good habits.” → Read More

Vjeux: “I see people appearing to somehow always be in easy projects where everything just works out fine and they deliver a lot of impact. I used to think that they were lucky, now I think that they are pro players and are able to plan multiple shots in advance and able to execute on their strategy.” → Read More

Repeatability, robustness, shareability, mastery, documentability. That's automation, although at a bigger scope than just plain computer automation and scripting. That's why I like to be organized and to create systems in my life. It's a way for me to be consistent, coherent, efficient and meticulous. To care about what I do without putting more charge on me. → Read More

Marty Cagan: “What I believe is the largest source of waste in technology, and that’s waste in large companies […] that spend shocking amounts of money on technology every year for such paltry results.” → Read More

Jonathan Lefèvre: “This has mostly allowed me to realize what was truly making the strength of the customer service at Capitaine Train: its operational efficiency. In the end, if we could manage 2 millions of customers with a small team of 15 people, it was because we were extremely well equipped.” → Read More