> Try new things. I broadly agree with you here, but I have a minor side-note to make here: while trying new "new" things, don't forget about old "new" things.

> Try new things. I broadly agree with you here, but I have a minor side-note to make here: while trying new "new" things, don't forget about old "new" things. A technique from the '60s can, and often will be, new to you today, as well as for a vast majority of today's programmers. I find it incredibly sad that programming as a profession treats its history like a burden to be shunned in favor of yet another unconscious reiteration of a classical concept that gets fashionable in one part of the community for a year or a few, before slipping back into the huge pile of forgotten ideas and implementations. Try new things, but look for them both on twitter and in archives of many decades prior.