hårdkoda

Hårdkoda, or to hard-code, is a term used in software development to describe embedding data directly in source code rather than retrieving it from external sources such as configuration files, environment variables, or databases. The term originates from Swedish usage, but is widely understood in programming discussions across languages. Common examples include hard-coded API keys, file paths, numeric constants, or feature flags.

Advantages of hard coding include simplicity, fewer dependencies, and fast access at runtime. However, the practice also introduces notable disadvantages: rigidity, maintenance burden, difficulties in localization, testing challenges, and potential security risks when secrets are embedded in code. Because values are baked into the program, updates often require code changes and redeployment, increasing the chance of errors and outages.

Best practices recommend avoiding hard coding in production. Instead, extract values into configuration files or environment variables, use secret management for sensitive data, and employ patterns such as dependency injection or parameterization. In practice, developers may hard-code during prototyping or for small one-off scripts, but should refactor before deployment. Many languages and development ecosystems promote externalized configuration, alignment with twelve-factor app principles, and automated deployment pipelines to reduce reliance on hard-coded values. This approach improves flexibility, security, testability, and maintainability of software systems.