Quiz
Warm-up from lesson 7-2: code that runs in the user's browser and makes the page interactive is called the...
The roles, in plain terms
Software engineering jobs mostly map onto the picture you built in unit 7:
| Role | Builds | Typical tools |
|---|---|---|
| Frontend engineer | What users see and click | HTML, CSS, JavaScript, TypeScript, React |
| Backend engineer | Servers, data, business logic | Python, Java, Go, SQL databases |
| Full-stack engineer | Both sides of one product | A mix of the two rows above |
| DevOps engineer | The machinery that builds, ships, and monitors everyone's code | Cloud platforms, Linux, automation scripts |
A typical day is not eight hours of typing code. Engineers read existing code, debug (lesson 1-1's word), review teammates' changes, write small tests, and spend a lot of time in discussions deciding what to build. The core skill under all of it is the one this course has been training: take a fuzzy goal, turn it into exact steps, and verify the result.
Quiz
A login page looks perfect, but pressing the button never actually checks the password against stored accounts. Which kind of work is missing?
Problem
What do you call an engineer who works on both the frontend and the backend of a product? (Two words or one hyphenated word.)