Why learn the basics of coding?

It sounds like a redundant question. To become a programmer, you start with the basics and work your way up. In practice, that path is easy to skip.

AI can draft code in seconds. Forums and docs are full of snippets you can paste until something compiles. Plenty of people ship software this way — and for a while, it works. The trouble starts when the code breaks, the model hallucinates, or you need a change that the snippet was never designed for. Without fundamentals, you are stuck in a rabbit hole of opaque libraries and hope.

People who know the basics can invent a solution when they have the recipe — an algorithm. They can read what a model wrote, catch the mistakes, and fix them. People who only assemble fragments rarely see under the bonnet: why a program is slow, bloated, or fragile. Assembling is a fine way to start, and sometimes it puts food on the table. Staying there forever, when you know you could go deeper, is a different choice.

Learning the basics of coding is how you solve problems with a computer on purpose — a weather-sensor log, a search index, anything practical you can invent — instead of hunting for a half-fit ready-made tool you cannot safely change.

That is why this site exists: to learn programming thoroughly, but incrementally, starting with C.

Why C?

C is old enough to still expose ideas modern high-level languages hide. You get memory, pointers, and real control of the machine — the foundations you need to write lean software and to understand what higher-level stacks are doing for you.

Harvard’s free CS50 course is a rigorous companion if you want lectures and problem sets alongside. Here on getc.uk we walk the same ground one step at a time — beginning with the tool you will use every day: the command line.