IT Glossary
What is a code library?
Code already written and tested by other people, reused inside your application — the standard bricks modern software is built from.
No modern application is written from scratch. For generating PDFs, processing payments, drawing charts or handling logins there are libraries: packages of code written, tested and maintained by others, which developers assemble like standard bricks. An ordinary business application uses, directly and indirectly, hundreds of them, most of them free and open source. For your company this has two faces. The good one: development costs a fraction of what building everything yourself would, and the critical components such as encryption and payment handling are scrutinised by entire communities rather than by one developer working against a deadline. The face that demands hygiene: every library is a dependency. It arrives with its own licence, and some licences carry conditions incompatible with commercial software, and it arrives with its own vulnerabilities. That is why your application needs periodic maintenance to keep those libraries current and safe rather than quietly rotting after handover.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Development an order of magnitude cheaper
Standard functionality — PDFs, email, payments, charts — is assembled from mature components instead of being reinvented at your expense.
Quality proven across thousands of projects
A widely used library has been exercised in production by thousands of companies, which means its major faults were found and fixed long before you arrived.
Standardisation that protects you
Code built on well-known libraries can be picked up by any competent team, so you never depend on the unique personal style of the first developer.
Frequently asked questions
What risks do the libraries in my application bring?
Two main ones: vulnerabilities discovered later, which is why an application is maintained rather than abandoned after delivery, and libraries abandoned by their authors, which have to be replaced in good time. Both are managed through periodic maintenance — a normal running cost of live software.
Do library licences matter for my company?
Yes. Most open-source licences such as MIT and Apache permit any commercial use, but some copyleft licences can require you to publish your own code. A professional supplier checks dependency licences, and on projects with real stakes it is worth asking explicitly whether they have.
What is the difference between a library and a framework?
You call a library when you need it — a tool in the developer's kit. A framework calls you: it is a skeleton that dictates the structure of the whole application. Choosing a framework is an architectural decision; choosing libraries is a daily one.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247