Should we split git projects across multiple repositories?

Dickon Reed wrote “Recommendations Keep your project source code in a single repository for simplicity as long as you reasonably can while keeping your developers working efficiently. Invest in your build to keep your median automated build and test time as fast as possible – 15 minutes is good, 1 minute is better. Keep large binaries out and…”

Reasoning about GraphQL servers

Dickon Reed wrote “Lots of developers seem very excited about GraphQL, so it was useful to read Sacha Greif’s Five Common Problems in GraphQL Apps (And How to Fix Them). While learning GraphQL after working with gRPC recently a few more questions come to mind, discussed below. Being new to GraphQL I’m not trying to offer conclusions or recommendations…”

A year with Bitbucket Cloud

Dickon Reed wrote “For the whole of 2018 we used Bitbucket Cloud to host a few git repositories on a project with around 40 developers working full time, creating 20000 commits. The service worked pretty well, though: We did end up spending some time developing extra checks and automation. We have concerns around the lack of service availability…”

Enoch Lai at the English language Wikipedia [GFDL (http://www.gnu.org/copyleft/fdl.html) or CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0/)], via Wikimedia Commons

Recycling your continuous integration builds

Dickon Reed wrote “Background Having a stable integration branch and doing branch per feature is one way to run a project; we use it to ensure we do code review on every change, and (almost) never have to roll back bad merges (though there are other approaches). If you are doing feature per branch you can do extensive testing…”