Codebase

Uses your system voice; voice and rate in settings.

Snapshot

≈ 3 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

CodeBase is a tech ecosystem support organisation that has supported over 500 startups and scaleups, who have collectively raised over £4 billion. CodeBase is promotes collaboration in tech innovation, by working with startups, scaleups, corporates, governments, academia and the third sector. CodeBase provides the workspace environment for startups to grow, delivers expert educational programmes and industry accelerators, and fosters connections through events, meetups, mentorship matching, and corporate-startup collaboration programmes.

Launched in Edinburgh in 2014, CodeBase offers startup incubation space through hotdesking, coworking, and dedicated office space. Further hubs opened in Stirling, in 2017, followed by Aberdeen in 2019, along with popup hubs across the UK. CodeBase is for startup founders, would-be founders, and employees across the UK - particularly within the tech ecosystem - who want to join a community of like-minded people, learn from others, and access support to help grow their business.

CodeBase works with businesses looking to innovate through collaboration with startups and tech businesses in their sectors. Governments and enterprise organisations looking for support in delivering large scale programmes.

Evidence and sources

A codebase (or code base) is a collection of source code that is maintained as a unit. Typically, it is used to build one or more software components including applications and libraries. A codebase is often stored in a source control repository of a version control system. A repository can contain build-generated files (which are therefore not source code), but typically such files are excluded from a repository, and therefore the codebase.

A repository may contain data files (such as configuration) that are required for building or running the resulting software. But version control is not a required aspect of a codebase. Even the Linux kernel was maintained without version control for many years. When developing multiple components, a choice is made either to maintain a separate, distinct codebase for each, or to combine codebases, possibly in a single, . With a monolithic codebase, changes to (i.e. refactoring) multiple components can often be easier and robust.

But this requires a larger repository, and makes it easier to introduce wide-ranging technical debt. With separate codebases, each repository is smaller and more manageable. The structure enforces logical separation between components, but can require more build and runtime integration between codebases, and complicates changes that span multiple components.

Text derived from https://en.wikipedia.org/w/index.php?oldid=1372037778 under CC BY-SA 4.0; modifications have been made.

Sources cited in this revision

5 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.