The time has come where I need to start looking for jobs in the field of software development. These jobs require rigorous interview processes, which generally include some sort of coding assessment; in fact, I just took such a test only a couple days ago. I want to ensure that I will do the best that I can do during each assessment, while also continuously improving so that my performance will get better with each interview. This growth requires practice, practice, practice, which, conveniently, is the pattern that I will be discussing this week.
Practice, Practice, Practice, as the name of the pattern suggests, describes the ever-present need to keep up with skills and striving to improve upon current level of skill. One of the common challenges, though, is that an apprentice may only have the opportunity to practice in the workplace, so that there is a risk to make mistakes with potentially harmful effects. Apprentices should have the opportunity to practice techniques outside of this environment so that there is room to make mistakes. When there is the looming pressure of causing lasting damage should the on-the-job practice go wrong, it can definitely be stressful for the apprentice. This could result in a lack of learning from any mistakes made from the process. The whole point of practicing is to ultimately learn from it, and so it is imperative to separate practice from job training.
I completely agree with the points discussed from this week’s apprenticeship pattern. It’s so important that I have the chance to make mistakes and learn from them, without having to worry about messing something up in my job’s overall system. It’s also important that I keep working on my skills in general. As I keep applying to development positions, I need to (and will) make sure that I maintain a level of consistency with my practice exercises. Using online tools such as code katas, as described in the apprenticeship pattern, as well as other resources, I have plenty of ways to implement high-quality patterns of practicing.
Thanks for reading!