https://nalar.dev/software-engineering/ Recent content in Software Engineering on Nalar Hugo en-us Tue, 01 Sep 2026 00:00:00 +0700 https://nalar.dev/evolving-apis-without-breaking-clients/ Tue, 01 Sep 2026 00:00:00 +0700 https://nalar.dev/evolving-apis-without-breaking-clients/ <p>An API is not only an HTTP path or function signature. It is a contract about syntax, semantics, timing, errors, ordering, defaults, and lifecycle.</p> <p>Breaking changes often happen because a server remains syntactically compatible while changing one of those less-visible assumptions.</p> <p>Safe API evolution starts by identifying what clients can reasonably depend on and designing changes that allow old and new versions to coexist.</p> <h2 id="compatibility-has-multiple-dimensions">Compatibility has multiple dimensions</h2> <p>A change can preserve JSON shape and still break clients.</p> https://nalar.dev/programming-languages-and-tools-with-language-server-protocol-lsp-support/ Wed, 01 Oct 2025 00:00:00 +0700 https://nalar.dev/programming-languages-and-tools-with-language-server-protocol-lsp-support/ <p>Modern editors such as VS Code, Neovim, Emacs, and Sublime Text can share language intelligence through the <strong>Language Server Protocol (LSP)</strong>. A language server runs separately from the editor and provides features such as completion, diagnostics, symbol navigation, hover information, and refactoring support.</p> <h2 id="how-lsp-works">How LSP Works</h2> <p>A typical setup has three parts:</p> <ol> <li>a language server installed on the system or inside the project;</li> <li>an editor or editor plugin that speaks LSP;</li> <li>project configuration the server can understand.</li> </ol> <p>For example, Neovim can connect to <code>gopls</code> for Go, while VS Code normally installs the appropriate extension that manages the server integration.</p>