Onboarding Phase
Before we can function as a software engineering team, every individual must master the tools of the trade. Weeks 1 through 4 function as a technical bootcamp. During this phase, our goal is not “product delivery,” but “individual competency.” We focus entirely on setting up your development environment and passing the certification.
Unlike the Sprint phase, where you are expected to self-manage, the onboarding phase is high-touch and instructional. We use the following format for these sessions:
Cadence
Concept Check (0:00 – 0:20)
We begin with a brief review of the Async material to ensure conceptual understanding. We will address the “Why” before the “How.” (e.g., Why do we use SSH keys instead of passwords? Why does Pixi exist?)
Code-Along (0:20 – 0:50)
You will open your terminal; I will open mine. We will perform the core technical tasks of the week simultaneously. This is a “follow-the-leader” exercise where we configure your specialized research environment in real-time. If you encounter a path error or permission denied message, we stop and fix it immediately. By the end of this block, you should have a working setup that allows you to attempt or work on the certification.
Open Lab (0:50 – 1:50)
The second hour is dedicated to completing your certifications. You will work individually or in pairs to generate the required artifacts. The instructor will circulate to sign off on completed certifications or assist with debugging.
Rules of Engagement
Because we move fast during the Code-Along, we need a high-bandwidth way to communicate status without interrupting the flow. We will use the note-card system.
- Blue: “I have completed the task.” Place this on your laptop lid so the instructor can see that the room is ready to move on.
- Pink: “I am stuck,” “I have an error,” or “I need help.” Place this on your laptop lid immediately.
This immediate “hand-raising” support model applies only to Weeks 1–4. Starting in Week 5 (Sprints), we will use the ticket system.