The Academy

Loading the search index…

Searches the academy on this device only.

Next steps: programming, web development and data analysis

Understand what programmers, web developers and data analysts do, which parts of this academy already prepare you, and which small projects and three-month goals make a good start.

25 minintermediatePractical task needs a laptop or desktop

Marking a lesson as read does not prove you can do it. Skills count as demonstrated when you pass the quiz (not yet) and complete the practical tasks (not yet).

By the end of this lesson you will be able to

  • Describe what programming, web development and data analysis involve in a normal week.
  • Connect lessons you have completed to the first needs of each direction.
  • Choose one beginner project and describe what finished looks like.
  • Write a realistic three-month goal with a weekly routine.

If you enjoyed making a web page do something, or finding the answer inside a table of numbers, this lesson is for you. Programming, web development and data analysis all ask you to give clear instructions to a computer and to check carefully that it did what you meant. You have already met variables, conditions, loops, HTML, CSS, JavaScript and spreadsheets. Here you will see how those pieces grow into three different directions and how to start a first project in each.

Three directions that share one habit

The shared habit is breaking a problem into small steps and testing each one. You used it in the Algorithm and flowchart lesson, and again when you read error messages and fixed a Bug. All three directions reward the same person: someone who is patient with errors, curious about why something happened and happy to look things up.

Diagram

Programming, web development and data analysis compared by purpose, tools and first project.

ProgrammingSolve problems with code
  • Code editor
  • Python or JavaScript
  • Test and debug

First project: a file-name tidier

Web developmentBuild for the browser
  • HTML, CSS, JavaScript
  • Git and GitHub
  • Accessible pages

First project: a multi-page site

Data analysisFind and explain patterns
  • Spreadsheets
  • Cleaning data
  • Charts and reports

First project: a short data report

Programming, web development and data analysis compared by purpose, tools and first project.
Read this figure as text

Three columns comparing programming, web development and data analysis with focus, tools and a first project.

Three columns. Programming: write instructions that solve problems; tools are a code editor and a language such as Python or JavaScript; first project is a small program that tidies a list of file names. Web development: build pages and sites people use in a browser; tools are HTML, CSS, JavaScript and Git; first project is a multi-page personal or community site. Data analysis: ask questions of data and explain the answers; tools are spreadsheets and later a language such as Python; first project is cleaning and summarising a small data file with a short written report.

Programming

A programmer writes instructions that a computer follows, then tests them and fixes mistakes. The work can be anything from a small tool that renames photos to part of a large system. Many beginners start with Python because its grammar is easy to read, but the ideas you learnt in JavaScript carry across: variables, conditions, loops and functions look slightly different in each language, yet they do the same jobs.

The next ideas to learn are lists and dictionaries (ways to hold many values), reading and writing files, splitting a program into small functions and writing a few tests that check your functions give the right answers. You also need the habit of reading documentation, which you practised in the module on reading error messages.

  • Skills you already have: variables, conditions, loops, functions, flowcharts, error messages and debugging.
  • Skills to add: a second language, working with files, writing tests, using a Code editor well and keeping your code in Git.
  • Beginner project: write a small program that reads a list of file names from a text file and prints a tidy version, for example all lower case with spaces replaced by hyphens. It must only print the new names; it must not rename any real file until you have tested it on a practice folder.
  • Beginner goal: in three months, finish three small programs, each under one hundred lines, and keep them in a Git repository with a short README for each.

Web development

Web developers build the pages and applications that people use in a browser. The front end is what the visitor sees and uses: HTML, CSS and JavaScript. The back end is the part that runs on a Server, storing information and answering requests. You have built a simple page and published it, which is a real first step on the front end.

  • Skills you already have: page structure, styling with the box model, flexible layouts, JavaScript events, form checks, browser developer tools, Git and publishing a Static site.
  • Skills to add: responsive design on real phones, accessibility testing, a front-end tool or framework later, and eventually a back end with a database.
  • Beginner project: build a three-page site for a community group, such as a choir or a small shop, with a contact form that only checks its fields in the browser. Test it with the keyboard alone, with zoom at 200% and on a phone. Publish it and write down what you learnt.
  • Beginner goal: in three months, publish one site that passes your own accessibility checklist and ask two people to try it and tell you what confused them.
Diagram

A safe way to run any first coding project.

  1. Step 1: Small idea
  2. Step 2: Define finished
  3. Step 3: Smallest version
  4. Step 4: Test
  5. Step 5: Save in Git
  6. Step 6: Show and reflect
A safe way to run any first coding project.
Read this figure as text

A flow of six steps from choosing a small idea to publishing and reflecting.

A flow of six steps. 1 Choose a small idea you can finish in two weeks. 2 Write what finished looks like in two sentences. 3 Build the smallest working version. 4 Test it with fictional data. 5 Save it in Git with clear messages. 6 Show it to someone and write what you would change.

Data analysis

A data analyst turns raw figures into answers that people can act on. A typical question might be: which three products sold best each month, and did the weekend sales change after the shop moved? The work has four parts: collecting a Dataset, cleaning it (fixing typing mistakes, missing values and duplicates), calculating and charting, and explaining the result in plain words. The last part matters most: a correct number that nobody understands is of little use.

You can start with a spreadsheet. Data is often shared as a CSV file file, which a spreadsheet opens easily. The picture below shows the kind of small table you can practise on, using fictional sales.

Simulated interface: not a real screenshot

A small fictional sales table with a total, ready for practice.

B5fx=SUM(B2:B4)
RowABC
1ProductUnitsPrice
2Tea403
3Sugar254
4Rice305
5Total units95
  1. Marker 1: Headings say what each column means
  2. Marker 2: One row per product, one value per cell
  3. Marker 3: A formula calculates the total
A small fictional sales table with a total, ready for practice.
Read this figure as text

A simulated spreadsheet of three products with units sold and a total in the bottom row.

A simulated spreadsheet. Row 1 headings: Product, Units, Price. Row 2: Tea, 40, 3. Row 3: Sugar, 25, 4. Row 4: Rice, 30, 5. Row 5: Total units in B5. Cell B5 is selected and the formula bar shows =SUM(B2:B4), which gives 95. Marker 1 points to the heading row, marker 2 to the data cells and marker 3 to the total.

  • Skills you already have: spreadsheets, formulas, cell references, sorting and filtering, and charts.
  • Skills to add: averages and ranges and how they can mislead, pivot-style summaries, cleaning messy data, choosing an honest chart, and later a language such as Python for larger files.
  • Beginner project: find or create a small fictional dataset of about two hundred rows, such as a month of imaginary shop sales. Clean it, answer three questions with formulas and charts, and write a one-page report that a non-expert can understand.
  • Beginner goal: in three months, finish two reports and explain, in one sentence each, what the data does not tell you.

A weekly routine that works

Five hours spread over the week beat one long session. A sensible pattern is three short sessions of about an hour for building, one session for reading and notes and one for showing your work to someone. Keep a notes file where you write what you tried, what failed and what the error message said. In three months that file becomes proof of how much you learnt.

A suggested weekly pattern of about five hours
SessionTimeWhat to do
Build 1, 2 and 31 hour eachWork on your project; stop each time with something that runs
Read and note1 hourRead documentation or a tutorial and write down three things you learnt
Show and fix1 hourShow a friend, collect feedback and fix one thing

Common mistakes

  • ✖ Instead of: Starting a project far too big, such as a whole online shop.

    ✔ Do this: Choose something you can finish in two to four weeks. Finishing a small project teaches more than abandoning a big one.

  • ✖ Instead of: Copying code you do not understand and hoping it works.

    ✔ Do this: Type it yourself, change one thing at a time and explain each line in your notes.

  • ✖ Instead of: Using real customer details as practice data.

    ✔ Do this: Use invented names and numbers, or public datasets with a licence that allows reuse.

  • ✖ Instead of: Skipping testing because the program seems to work once.

    ✔ Do this: Test normal values, empty values and unexpected values, and record the results.

If something goes wrong

I am stuck on an error for hours.
Stop, copy the exact error message, search for it, and write down what you expected and what happened. If nothing helps in 30 minutes, ask for help with a clear description and the smallest code that shows the problem.
My spreadsheet total is wrong.
Click the total cell and check the formula range. Make sure numbers are not stored as text, which often shows as left-aligned values.
I do not know which language to pick.
Pick one, such as Python or JavaScript, and stay with it for three months. The ideas carry over to others.
My published page looks different on a phone.
Check that the viewport meta tag is present and test with the browser's device mode. Use relative widths rather than fixed ones.

Key terms

Dataset
A collection of related data, usually arranged as rows and columns.
CSV file
A plain-text file where each line is a row and commas separate the columns.
Code editor
A text editor made for writing code, with colouring, helpful hints and tools for working on many files.
Static site
A website made of ready-written files (HTML, CSS, JavaScript, images) that the server sends unchanged.
Version control
Software that records the history of a set of files, so you can see changes, compare them and go back to an earlier state.

Practise it for real

Reading is not the same as being able to do it. Complete these on your own computer, then tick only what you have actually done. These ticks are your own honest record: nothing checks them for you.

Guided exerciseNeeds a laptop or desktop

Taster: one hour in each direction

Spend an hour on each. For programming, write in plain language, then as a flowchart, the steps that turn the file name Holiday Photo 1.JPG into holiday-photo-1.jpg. For web development, open your published page and use the browser's developer tools to check one thing, such as the heading structure, then change one colour in your own copy and reload. For data, type the small sales table above into a spreadsheet, use =SUM for the total and add a column that multiplies units by price. Note which hour you enjoyed most and why.

You have succeeded when:
Independent challenge

Challenge: plan your first project

Choose one direction and write a one-page project plan. State the idea in one sentence, what finished looks like in two sentences, the tools you will use, the fictional or public data you will use, three milestones with dates and the first small step you will take this week. Add one risk (for example, 'I may get stuck on errors') and what you will do about it.

You have succeeded when:

Knowledge check

6 questions. You need 80% to pass. Mistakes here are part of learning, and you can retry as often as you like.

  1. Question 1.Which description fits web development best?
  2. Question 2.Match each direction to a sensible first project.
  3. Question 3.It is best to learn a large framework before you understand plain HTML, CSS and JavaScript.
  4. Question 4.Kamau wants practice data for a report. He has a spreadsheet of real customer names, phone numbers and purchases from his uncle's shop.What should he do?
  5. Question 5.Put the first-project steps in a sensible order.
    1. Build the smallest working version
    2. Choose a small idea
    3. Describe what finished looks like
    4. Test with fictional data
    5. Show it to someone and reflect
  6. Question 6.Which routine is most likely to lead to steady progress?

Summary

  • Programming, web development and data analysis share one habit: small steps, tested carefully.
  • You already have variables, conditions, loops, HTML, CSS, JavaScript, spreadsheets and Git.
  • A first project should be small, finished, saved and shown to someone.
  • Use fictional or properly licensed data for practice.
  • Regular short sessions beat rare long ones.

Checklist: can you do these?

Marking a lesson as read does not prove you can do it. Skills count as demonstrated when you pass the quiz (not yet) and complete the practical tasks (not yet).

Related lessons

References and further reading

Official sources for details that can change between versions.

On this page