three things resonated with me (as a person in the long time programmer camp) 1. > You’re going to forget what your code does in a few months. Make it ridiculo

three things resonated with me (as a person in the long time programmer camp) 1. > You’re going to forget what your code does in a few months. Make it ridiculously easy to read. Sometimes, all you need is a one-liner in sed. 2. > No matter how many managers are screaming at you, the first step is to reliably replicate the bug 3. > Sooner or later, you will meet some older man who has been around for a while. At some point, this man will lecture you about the Laws of Programming. Ignore this man entirely. The first has to do with knowing yourself and having years of experience with a diversity of tools. (lessons: be reflective and work on a diverse toolbox) The second has to do with experiencing and learning from team/org dynamics and to some degree how to operate under pressure. The third is tricky - key red flag to watch for "the laws of programming" or "you don't have enough education" or similar put downs. But the older programmer who is always rolling up his/her sleeves to jump into the bug fixing process and and help - follow this person around like a puppy and watch everything - these guys are epic. edit: one more thought on my note about the third item: look for these people across the org - technical or business - look for the people who jump into to constructively help when its needed. (very Mr Rogers)