Deployment & Release: Going Live

The moment code leaves an engineer's computer and reaches a user is called Deployment. This is the most stressful and exciting part of the job.

The Environments

Code usually travels through three "environments" before it is finished:

1. Local: The engineer's own computer. ("It works on my machine!")
2. Staging: A private version of the app that looks exactly like the real one. We use this for testing.
3. Production (Prod): The live version that customers use. Never break Prod!

Release Vocabulary

• To deploy/push: To move code to an environment. ("We're pushing to staging now.")
• Rollout: Releasing a feature to users (often slowly, e.g., "a 10% rollout").
• Rollback: Reversing a deployment because something broke. ("We had to rollback the last release.")
• Hotfix: A small, urgent fix for a bug in Production.
• GA (General Availability): When a feature is finished and available to everyone.

Technical Debt

Sometimes, to meet a deadline, engineers write code that is "quick and dirty" rather than perfect. This creates Technical Debt. Like financial debt, you have to "pay it back" later by rewriting the code, or it will slow you down.

Common Phrase: "We're taking on some tech debt to hit the Friday deadline."

Alex's Tip: If you hear an engineer say "I'm pushing to Prod," don't distract them. It's a high-focus moment. Wait until you see the "Success" message in Slack!

Examples:

• Could you clarify the rollout plan? (I do not fully understand it.)
• Can you confirm the launch date is the 14th? (I want to make sure it is final.)
• Let me check the ticket and get back to you. (I will verify the detail myself.)

Grammar after confirm

After confirm if or confirm that, use statement word order, not question word order.

• Correct: Can you confirm if the meeting is at 3?
• Incorrect: Can you confirm is the meeting at 3?

The verb confirm is not a question word, so the subject (the meeting) comes before the verb (is).

Asking about blockers

In standups, you will ask and hear questions about blockers. Use these patterns:

• Are you blocked on anything?
• What's blocking you?
• Do you need any help unblocking this?

Avoid the direct why are you blocked?, which can sound like blame. What's blocking you? focuses on the problem, not the person.

Common mistakes

1. What do you mean? used as a real question. This phrase can sound confrontational. Use Could you say a bit more about that? instead.
2. Question word order after if. Say Can you confirm if the deadline is Friday? not Can you confirm if is the deadline Friday?
3. Using clarify for every check. Can you clarify the meeting time? is slightly off. The natural verb is confirm: Can you confirm the meeting time?

Practice

Rewrite each blunt question as a polite, professional clarifying question:

1. What do you mean by "soft launch"?
2. When is the deadline?
3. I didn't understand the API change.

Possible answers:

1. Just to clarify, could you explain what you mean by "soft launch"?
2. Can I just check the deadline for this?
3. Sorry, could you say a bit more about the API change? I want to make sure I understood.

You have now completed the Tech Vocabulary Foundations course. You can name the roles, tools, workflows, sprints, products, money terms, and meeting structures of a modern tech team. In the next course, Email Writing Essentials, you will turn this vocabulary into clear, professional written communication.