Tech roles beyond coding

Stage 2 · Lesson 7 of 10

Reading code without writing much

Technical literacy

You do not need to write production code, but you do need to follow it. This topic is about yourself. Start with names: files, functions and variables usually say what they do.

A function is a named block of code that does one job. Its signature, the first line, shows what goes in and what comes out. Read the tests, because they show intended behaviour in small examples.

Read descriptions to learn why something changed. To find where something happens, search the for a word from the screen or an error message. Then ask the author a precise question. This lets you answer many questions yourself and check that docs or specs match reality.

Common trapeither pretending to understand code you do not, or refusing to open it at all. A precise question shows respect for engineers' time.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with· follow one of these

  • VideoFree
    Crash Course Computer Science

    CrashCourse · Beginner

    Short free videos on how computers, networks and software work, pitched at beginners

  • CourseFree
    Select Star SQL

    Zi Chong Kao · Beginner

    A free interactive SQL tutorial on real data, enough for product and docs analytics

Practise

Keep handy

  • Clear reference for HTTP methods, headers and status codes

  • See how an API is described formally, which all three roles meet at work

Also worth your time

Mark this stage as not done?