Code Complete: Module Interfaces
2026-02-21 02:54 Diff
https://hexlet.io/blog/posts/code-complete-module-interfaces

In some languages, such as Python and JavaScript, variables and constants declared at module level can be imported to other parts of the program. On the one hand, this opens up a world of possibilities when compared to languages that require all data to be contained within functions, classes, etc. On the other hand, it makes it much easier to write code with issues.

Assume we are creating a web service that converts currencies. This converter specifies which currencies can be converted into which and at what rate:

Other parts of the program use this information for their own calculations and checks:

The code proved to be simple but unreliable. If the user requests an exchange rate for a currency that does not exist in the system, the following access error will occur:

Even if the first currency exists, then when the second one is absent, the constant rate will contain undefined, which can lead to an error.

Let's fix our code:

The error won't occur again, but the solution remains flawed. Working with rates will almost certainly not be limited to a single handler. As the program grows, currency rates will be used all over, which means that error handling will be required everywhere. Furthermore, any changes to the data structure will lead to rewriting all the pieces where it was used.

These issues typically arise when working with data directly without creating at least a minimal abstraction (functions) for data access. It’s easily solved, you just need to add a function to the module currency.js.