Every web studio remembers its first bad Monday. Ours \u2014 the one a friend who runs a small agency tells best \u2014 involved a junior developer onboarding onto nothing: no repository access, no staging credentials, a project manager off sick, and a welcome lunch that happened because somebody felt guilty. If you build websites for a living, you already believe that launches fail without preparation. This primer makes the same case for people: new developer onboarding is a project, it has phases and deliverables, and the vocabulary below will help you run it like one.<\/p>\n
Agency work is deadline-shaped. A new hire who drifts for two weeks is not an abstract inefficiency; they are a missed sprint on a client project someone promised in writing. Yet the joining period at most studios is held together by chat messages and good intentions, which is odd for an industry that would never treat a client build so casually. We would insist on mapping a site completely before development begins<\/a>; the same instinct should apply before a human being walks through the door.<\/p>\n Part of the trouble is that this field has its own words, and teams use them loosely. Here are the ones worth knowing, in the order they occur.<\/p>\n Here is the human truth: a junior developer’s first weeks are a fog of half-explained conventions. Which branch do we deploy from? Who approves content changes? What does the client actually see? Teams that answer these questions with a real curriculum \u2014 rather than osmosis \u2014 get competent colleagues dramatically faster.<\/p>\nA mini-glossary for the joining journey<\/h2>\n
\n
The part studios skip: structured early training<\/h2>\n