Hi, I'm Nikita Lozgachev, a software engineer at the company behind your Invisalign.

Focusing on functional programming patterns, managing complexity through clean abstractions and framework-agnostic architecture.

Sometimes I also write libraries and tools.

And sometimes I write about programming, craft, and ideas that stick.

10 Principles of Good Code

1. Good code is innovative where it must be

The solution space is never exhausted. New languages, runtimes, and paradigms offer genuine opportunities. But innovation in code serves the problem — it is never the point.

2. Good code solves a real problem

Code is written to be used by people. It must solve a real problem someone has — not a problem the author imagined, not a problem that might arise. Good code makes its purpose obvious and removes everything that works against it.

3. Good code is readable

Code is read far more than it is written. Every function, name, and structure is a message to the next person — yourself included. Only code written with that person in mind can be called clean.

4. Good code is self-explanatory

It reveals its structure through naming, shape, and flow. At best, it needs no comment. A comment is an apology for code that could not speak for itself.

5. Good code is unobtrusive

Code is a tool, not a canvas. Clever tricks and expressive flourishes impose the author’s personality on every future reader. Restraint leaves room for the problem to breathe.

6. Good code is honest

It does not claim more safety, performance, or correctness than it provides. Types, signatures, and names tell the truth. An abstraction that lies is worse than none.

7. Good code is long-lasting

It does not chase the fashionable pattern of the year. It will be read by someone who was not there. That reader is the final judge.

8. Good code is thorough down to the last detail

Nothing is left to chance. Edge cases are handled or explicitly deferred. Sloppiness in the small is disrespect toward the next maintainer.

9. Good code is environmentally responsible

Code runs on machines that consume power. Unnecessary computation, bloated dependencies, and infinite loops have a physical cost. Efficiency is not premature optimization — it is basic hygiene.

10. Good code is as little code as possible

Less, but better. Complexity compounds; simplicity does not. Delete before you add. The best line is the one not written.


After Dieter Rams and the UNIX philosophy.