The frontend developer, explained

Everything you have ever touched on a screen — every button that pressed, every form that received your details, every page that arranged itself politely on the phone and the laptop — was built by a frontend developer. The word means simply the front: the part of a program that faces the person using it. Every workshop has a front and a back — the stall that faces the road, and the store room where the stock and the accounts live. The frontend is the stall. It decides whether the customer can find what they came for, whether the price is readable in the sun, whether the transaction finishes or the customer walks in irritation.

The craft stands on three layers, and you may as well have their true names now. HTML is the skeleton: this is a heading, this is a paragraph, this is the box where the customer types. CSS is the clothing: colours, spacing, what it looks like when the screen is a small phone in the rain or a wide monitor in an office. JavaScript is the movement: what happens when the button is pressed — the menu that opens, the total that recalculates, the form that checks itself before travelling. Larger buildings are raised with frameworks — prepared skeletons and conventions with names like React, the very technology this page is served with — the way builders raise estates with prefabricated parts instead of moulding every brick by hand.

What the work actually is, day to day

Less invention than conversation. A designer hands over a picture of what a page should be; the frontend developer makes it real, exactly, on every screen size — and reports back where the picture fights the truth of small screens and slow networks. A backend — the store room, staffed by its own developers — sends goods in parcels of data; the frontend receives, arranges, and sends back what the customer filled. Much of the day is the two elders of this shelf in professional clothes: careful text selection and a thousand small saves — build one piece, look at it in the browser, adjust, save again. The loop you practised in Notepad at lesson three is, genuinely, the trade.

The good ones are good in ways you can already judge, because you have been a customer all your life on this shelf. Fast: a page that opens on a three-bar network in Onitsha traffic, not only on office fibre. Clear: letters that read, buttons that say what they do, forms that confess their errors in ordinary sentences. Honest on every screen: the phone is Nigeria's computer, and a stall that only stands on a laptop is a stall on a street with no foot traffic. None of that is decoration — it is the trade's version of the virtues these notes kept repeating: respect for the person on the other side of the screen.

• Look at any page you admire and name its three layers: the skeleton, the clothing, the movement.
• View the source of a simple page once — right-click, View page source. The skeleton, in public, is not a secret.
• The free-learning lesson applies in full: one month, HTML and CSS, hands on the keys, one real page built by the end.
• When you are ready for a room, a machine and a person, the academy's web courses start exactly where this note stops.

Is the stall for you?

If you finished lesson three secretly pleased — if arranging the page, naming things properly and seeing your change appear on refresh gave you a small honest joy — then the frontend is a door worth walking through, and the road from these notes to paid work in it is walked every year, self-taught hands included. The watching rooms of lesson one hundred and twenty-two guard the compound; the stall builders raise what the compound is for. Both are honest work. Only you know which chair fits your temperament — and now you have sat in both, described without mystique, before spending a naira on either.