3 ms·

In the building where I live I have a neighbour that I thought he was 60 (or less) years old because it was very vitalized, moved very well.. and one day I happ

In the building where I live I have a neighbour that I thought he was 60 (or less) years old because it was very vitalized, moved very well.. and one day I happened to talk to him, he told me he is 74 years old, he obtained two university degrees when he was young, he had been a teacher, he also was a calligraphy national award and finalist of a novelist award.. I asked him what's his secret to being so active and vitalize at his age.. he told me "it's all in the mind" he then proceeds to tell me that he reads and writes every day (he is writing a piece of a novel everyday) I then ask him what is a better exercise to keep the mind active, reading or writing? his answer, "absolutely the writing, writing is the backing of the imagination".. and then I see this article on hacker news and start connecting dots..

hackinthebochs 13y ago
On that same note I've often wondered how useful it would be if our IDEs actually recorded our keystrokes as we developed code. The problem with commits is that we only see the end result. There is usually a process of evolution of code, and through this evolution we can fully understand the end result. So much information about a codebase is lost because we only see the end result. Git and Mercurial are steps in the right direction here. You see groups of changes as one unit, and the philosophy of these systems is one of frequent commits. But what if we went even further and could see code evolve as its being typed?