*Embrace failure. “Embrace things being broken and know it’s not your fault, it’s not because you’re stupid, it’s not because you’re bad at programming. It’s because that is the nature of this craft: to exist in a broken state.”

*In fact, failing is GOOD. “The only way for everything to work all the time would be to stop innovating. So get comfortable existing in a state of error.”

*Finish learning what you started. “Even if you’re learning a language that has become outdated, the act of finishing that learning process gives you something you won’t get by jumping from one thing to the next every time someone tells you to.”

*Give back to the coding community. “When it comes to finding a job as a developer, we always say that one of your goals is to become a ‘no-brainer hire.’ Imagine interviewing two candidates who are as competent as each other, but one blogs and one doesn’t. Who do you hire? I guarantee you it’s going to be the candidate giving back to the coding community.”

copied Laurence Bradford laurence@learntocodewith.me via