What software engineering is
Software engineering is building software that real people rely on, as a team, in a way that keeps working and can keep changing for years.
Programming is writing code that works. Software engineering is everything around that: deciding what to build, planning it, working with other people, testing it, releasing it, fixing it when it breaks, and changing it when needs change, often for years after it was first written. A small script you write for yourself is programming. A banking app used by millions, built by hundreds of people over ten years, is software engineering.
These four short notes explain what the job actually involves, the stages a piece of software goes through, the different roles on a team, and the different kinds of software engineering you could go into.
What youโll be able to do
By the end you will be able to:
- explain the difference between programming and software engineering;
- name the stages software goes through, from idea to maintenance, and what goes wrong when one is skipped;
- explain what each role on a software team is responsible for;
- describe the different areas you could specialise in, and which are hard to move into later.
Where to start
These notes are short and need no programming. Read them in order. Theyโre optional reading in week 1 of SWE 101.
- What Software Engineering Is: programming versus engineering, where a software engineerโs time really goes, and three habits every good engineer has.
- The Software Development Lifecycle: the six stages of building software, what breaks when each is skipped, and the difference between planning everything up front and working in small steps.
- The Engineering Roles: the eleven common roles on a software team, what each one worries about, and how seniority works.
- The Kinds of Software Engineering: the different areas you can work in, such as software for devices, games, operating systems and supercomputers, and which are hard to switch into later.
Where to go next
Nothing here is required for anything else. From here, pick a subject:
- Programming Fundamentals: if you havenโt written code yet.
- The home page: the map of every subject.
- The Primetechie Path: an order to work through the whole vault.
Related
- Best Practices: the habits that follow from โcode is read more often than itโs writtenโ.
- Architecture: designing software, in depth.
About this course
- Size: 4 short notes. Note 04 was added in August 2026.
- Where it came from: written from reference sources as an introduction. If youโve already worked on real projects, most of it will confirm what you know; its value is giving you the words for it.
Software engineering
Infrastructure & security
AI & data
Computer science
Hardware & engineering