A fresh cloud server or VPS comes with every port wide open. Your provider doesn’t know what you’re running, so they let everything through. This is fine for about five minutes — until the first bot finds your IP and starts probing every exposed service. If you’re running
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
Honesty Pragmatism Excellence Speed
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 in
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 forks like gitlab.