Our core values
Read more
Make software development feel light.
New engineers open a blog and read a post that praises monoliths, then one that praises micro-services; one week GitHub Actions rules, the next it’s GitLab CI. Choice paralysis sets in, searching eclipses shipping, and months—or sleepless years—pass before the fog lifts. Code should be simple and
All-in one: Mono-repo repositories
We favor "mono-repo" repositories. That is everything that belongs to a customer's project goes into one single Git repository: All the different subprojects also-known-as "services" (backend, frontend, mobile app), any technical documentation and any infrastructure code. How we benefit We heavily benefit from mono-repos
No branches, just fork it!
Okay okay, you're right we still use branches, but just not on the master main repository. Every developer has their own forked project, which lives under the "forks" group. For example if we had a git project at gitlab.com/rocketrunner/rocketrunner we would then create
Coming soon
This is nlited.de, a brand new site by Lars that's just getting started. Things will be up and running here shortly, but you can subscribe in the meantime if you'd like to stay up to date and receive emails when new content is published!