In order to learn the essentials of JavaScript, the apprenticeship practice assignments, final project, and my personal project were each set up differently-and none of them used React. That’s why having a deep knowledge of programming fundamentals is a crucial resource to have when the tech world inevitably moves on to the next new thing. This worked in the short term, but what if I wanted to work for a company or on a project that didn’t use React or JavaScript, at all? Tools like React are powerful and beneficial for many web apps, but they do tend to go in and out of vogue. However, since my basic knowledge of JS was relatively small before learning React, I tended to filter many JS concepts through my knowledge of React, rather than the other way around. React is a powerful and extremely popular library, so it was very useful to learn. My bootcamp had covered some basics, but then quickly pivoted to React. A Deep Learning of JavaScript Fundamentalsĭuring the apprenticeship, I also learned a lot about what I could do with basic JavaScript (JS). By the end of the apprenticeship, my Git proficiency had skyrocketed because I did my best to consistently adhere to Sparkbox’s best practices for writing software. During the apprenticeship, Sparkbox encouraged me to connect with their developers multiple times a week some of my most valuable collaborative sessions focused on walking through my commit history and learning to rewrite it, step by step (thank you Jordan, for all the pairing we did on this!) While I don’t regularly rewrite my commit history as a developer today, these one-on-one collaborations were an invaluable resource that allowed me to deepen my understanding of the ways in which I use Git on a daily basis.
Initially, the idea of using Git to travel back in history and rewrite it was intimidating, but luckily, I had help from more experienced developers.
Sparkbox apprenticeship reddit how to#
In those cases, it’s important to know how to add work in patches (using git commit -p), edit commits, and create an organized history that’s easy for a reviewer to understand. This sounds easy enough in theory, but in practice, the work that we do doesn’t always happen in such a logical, linear fashion. Each of these represents separate ideas, and should, therefore, be separate commits. For instance, on one branch, you might have some bug fix work as well as some refactoring work. The idea is that each commit should contain a small amount of work that corresponds to a central idea-an atomic commit. For more on why well-written commit messages are important, check out this article. One of the most important parts of this Git flow is writing descriptive, concise commit messages because a well-written commit message is essential to a well-written commit history. As an apprentice, I learned about the Sparkbox Git Workflow and practiced following it while I worked on collaborative and personal projects. While I had learned the basics of Git in bootcamp, my confidence with Git really grew during the apprenticeship, and I use much of what I learned during the apprenticeship now. Here are three of the most important things that I learned in the apprenticeship as a bootcamp graduate: Git Workflow, Proficiency, and MentorshipĬurrently, I use Git and GitHub on a daily basis as a developer to contribute to the project I’m working on. The Sparkbox apprenticeship was the perfect opportunity for me to level up my skills before being hired as a web developer.
I chose a coding bootcamp to help me make the career leap to web developer, and while I learned a lot, I still needed to learn more. My origin story is that I was a high school teacher and then a stay-at-home mom. I also completed the Sparkbox apprenticeship recently and became a web developer on the Sparkbox team. At Sparkbox, many of the web developers with the most interesting backgrounds started out in web development through the apprenticeship program. Many developers started their careers in a completely different field before transitioning to web development, and I find that hearing origin stories from these developers is particularly interesting.
0 kommentar(er)
