That's an amazing story. Few questions: 1) How many lines of code is in that man-century project? Is the number of lines of code ~proportional to the number o

That's an amazing story. Few questions: 1) How many lines of code is in that man-century project? Is the number of lines of code ~proportional to the number of man hours, or lines(man-hours) function is ~ logarithmic? 2) How does your typical project look like (or how does that project look like) in terms of testing vs coding? Do you spend few months of covering old code by tests and only then start testing? Or you do "add tests - add features - add tests - add features - ..." cycle? What's the proportion between time spent on writing tests and writing code? 3) What's the proportion of time you spend directly working (analyzing requirements/testing/writing code) and generally learning (books, HN, etc.)? 4) Do you do most of the work yourself or you mostly leading your team? 5) How do you pick your projects, and when you pick them - what are your relationships with the clients: Fixed contract? Hourly contract? Employment? Thanks!