Code will be read more often than it is written

When we designed Norscode, we had one rule above all others: the code should be easy to read six months after it was written, by someone other than the person who wrote it.

Why readability wins

A programmer spends a small part of their time writing new code. The rest goes to reading existing code: finding bugs, understanding what the previous developer meant, making a small change without tearing down something else. A language that is fast to write but hard to read optimizes for the wrong part of the work.

That is why Norscode is deliberately a little verbose. returner is longer to type than a symbol, but it is impossible to misunderstand. We take a few extra keystrokes in exchange for code that explains itself.

Fewer ways to do the same thing

Many languages give you five ways to write the same loop. It feels liberating, right up until you read someone else's code and meet all five. Norscode holds back: one clear way, consistent throughout the whole standard library. When the patterns repeat, you don't have to interpret them anew each time.

Error messages that guide

An error message is also something you read — usually when you have the least time for it. Norscode tries to say what went wrong in plain Norwegian, not just where. The goal is for the message to point you toward the solution, not leave you with a web search.

Readability is not a property you add at the end. It is built into every single choice — and those are choices we have made deliberately.

A concrete choice: verbose on purpose

Look at a simple statement: returner beste. It is longer to type than a symbol, but there is no doubt about what it does. Norscode consistently makes that trade — a few extra keystrokes in exchange for code that explains itself. When you read it six months later, it saves you far more time than the writing cost.

One way, not ten

Many languages give you several ways to express the same thing. It feels liberating right up until you read someone else's code and meet all the variants. Norscode holds back on purpose: one clear way, consistent throughout the whole standard library. When the patterns repeat, you don't have to interpret them anew each time — you recognize them.

Error messages are reading too

An error message is something you read, usually when you have the least time. Norscode tries to say what went wrong in plain Norwegian, not just where. The goal is for the message to point you toward the solution, not leave you with a web search. Readability is not something you add at the end — it is a choice at every single step, from keyword to error message.

Back to the overview