Moreover, I try to embedded documentation and diagnostic/debugging tools, such as meaningful error messages and traces, into code. Usually, debugging takes 3x m

Moreover, I try to embedded documentation and diagnostic/debugging tools, such as meaningful error messages and traces, into code. Usually, debugging takes 3x more time than coding, so it is very profitable to reduce debugging time from the very beginning. Also, I'm automating branching, building, testing, merging, committing, releasing procedures, so for me, it feels like a game: read a ticket, make a branch, write a test case, write the business code, update documentation, tests are OK? -> merge and commit, update resolution comments, send ticket for review and manual testing, next ticket. Of course, it works only when the whole team works the same way and each member of the team plays his/her role properly.