| Companies that don't value these practices exist. They're everywhere. That's no excuse not to sharpen your skills, but hopefully it'll help you rest a little easier. That said, the best medicine is practice. To practice unit tests (or TDD when you feel like you're ready), do some katas. There are plenty of popular ones, and sites like http://www.codewars.com/ offer great challenges. As you're working through your katas, make sure you check in to source control as you go. Learn the basics well, and pick up the rest as you go. You can always Google the more advanced stuff if you need it (most of the time, the basics are all you'll need). For code reviews, read code. Read your own, certainly, but also read others. Hit up github. Find a repo you like, and then hit the 'commits' button. Read through the list of changes, and then write down what you think. In real life, code reviews will be a little more tricky. You'll have to navigate a social structure and determine what is and isn't okay to say in a code review. Some groups are ruthless. Some are academic. Most, however, will be regular developers who are proud of their work, and the ability to criticize constructively will be of great value. Two other suggestion come to mind for new team members. The first - be an apprentice first. Ask questions and learn. Especially in the beginning, your #1 job is to understand your environment - the people, processes, patterns, and practices that compose the overall work. The second, take a shower. Nobody likes smelly teammates. |