Tech roles beyond coding

Stage 2 · Lesson 1 of 10

How software is built: the lifecycle

Technical literacy

Software is built in a repeating cycle, often called the , or SDLC. Someone spots a need. The team designs a solution.

Engineers build it in small pieces, and other engineers review the code. check it, and sometimes QA (quality assurance) testers check it by hand too. It is released to users, and the team then runs and improves it.

In practice these steps overlap and repeat every week or two. Each non-coding role plugs in at specific points. PMs shape the need and measure the result.

Writers document the feature before or at release. Advocates teach it once it is live and bring back feedback. Knowing the whole cycle tells you when your input is cheap and when it is too late.

Common trapjoining at the end and being surprised that nobody can change a design that shipped last week.

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?