This makes the case for thinking before coding brilliantly. I wonder if you/Qonto have ideas or templates for carrying out the technical dive-in? You list some considerations (endpoints, error responses, refactoring etc) - I wonder if you have any further information on how to go about the dive-in, how to structure it etc. That would be very interesting, possibly a future article!